You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using the DynamicLLMPathExtractor with allowed_entity_props=[]. It will generate some properties for iPad like: {'generation': '10th', 'storage': '64GB', 'price': '$349',
'features': ['Liquid Retina display', 'A14 Bionic chip', 'USB-C
charging'],
In the _insert_nodes_to_vector_index function, the self.vector_store.add(llama_nodes) will raise error as it requires "Value for metadata features must be one of (str, int, float, None)"
Version
0.12.2
Steps to Reproduce
DynamicLLMPathExtractor with allowed_entity_props=[]
Relevant Logs/Tracbacks
No response
The text was updated successfully, but these errors were encountered:
Hey @haoyuhan1! I'm here to help you with any bugs, questions, or contributions you have. If you need assistance, feel free to ask!
The error you're encountering is due to the self.vector_store.add(llama_nodes) method, which requires metadata feature values to be of type str, int, float, or None. The list data type in your metadata (e.g., features: ['Liquid Retina display', 'A14 Bionic chip', 'USB-C charging']) is causing the issue.
To resolve this, you can convert list data types in your metadata to a string format before inserting them into the vector store. For example, you can join the list items into a single string:
Bug Description
I am using the DynamicLLMPathExtractor with allowed_entity_props=[]. It will generate some properties for iPad like: {'generation': '10th', 'storage': '64GB', 'price': '$349',
'features': ['Liquid Retina display', 'A14 Bionic chip', 'USB-C
charging'],
In the _insert_nodes_to_vector_index function, the self.vector_store.add(llama_nodes) will raise error as it requires "Value for metadata features must be one of (str, int, float, None)"
Version
0.12.2
Steps to Reproduce
DynamicLLMPathExtractor with allowed_entity_props=[]
Relevant Logs/Tracbacks
No response
The text was updated successfully, but these errors were encountered: