-
I love llama_index and just scratching surface. I am fond of llama_index and primarily utilize it for structured data. The RecursiveRetriever concept demonstrated in the provided link resonates with me https://github.com/run-llama/llama_index/blob/dd3a25c8a2423d1f8f5077237e7b68e7065e6907/docs/docs/examples/query_engine/pdf_tables/recursive_retriever.ipynb. My query pertains to storing Vectors after converting my data - can I preserve them in Chromadb to bypass repeating the conversion process? I am inclined towards storing the initial data for future use, enabling quick retrieval through a query like: I mean I like to store first before I query. In the query, I call the vector database and query again... That is my goal. Could you assist me with this? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 5 replies
-
To store your vectors in ChromaDB for use with the RetrieverQuery Engine, follow these steps:
This approach allows you to convert data into vectors, store them in ChromaDB, and retrieve them using a query engine. For detailed steps on setting up the environment, loading data, and querying, refer to the respective package documentation and the example provided in the Remember, when working with ChromaDB and LlamaIndex, there are constraints such as the
|
Beta Was this translation helpful? Give feedback.
To store the
vector_index
in ChromaDB and retrieve it later, you'll need to adjust your approach slightly from the standard document storage and retrieval process. The key here is to understand that storing avector_index
involves not just the vectors themselves but also the structure and metadata that allow for efficient querying later on.Given the code snippet you've shared and your goal, here's a refined example that demonstrates how to store your
vector_index
in ChromaDB and retrieve it for future queries. This example assumes you've already created yourvector_index
as shown in your snippet and focuses on integrating with ChromaDB: