How to Retrieve Top K Unique Base Nodes Using RecursiveRetriever in LlamaIndex?
I’m encountering an issue when trying to retrieve the top K base nodes using the RecursiveRetriever
from LlamaIndex. Instead of retrieving only the top K base nodes, it retrieves from all top K nodes (including base and reference nodes) and then selects unique base nodes from this list.
Llamaindex load from storage optimization
I am trying to load index like this
load_index_from_storage(retrieved_sentence)
ModuleNotFoundError: No module named ‘llama_index.readers.database’
from llama_index.readers.database import DatabaseReader ModuleNotFoundError: No module named ‘llama_index.readers.database’ llama-index Use the below command to install pip install llama-index-readers-database
Llama Index stack “Cannot build index from nodes with no content. “
I am using Llama Index for the first time and I started with the tutorial here
How to prevent LlamaIndex queryengine from reloading LLM on each query?
I’m trying to experiment with LlamaIndex and build up a chatbot answering on provided documents and doing some research I ended up with a code like the following (I’ve purged out irrelevant parts):
Customizing ReAct agent’s system_prompt in LlamaIndex
i want to customize the system prompt for the ReAct agent in LlamaIndex and ,i cant seem to access any predefined prompt, nor be able to change
why do i get this ValueError: No API key found for OpenAI
I’m using llama-index with the following code:
Is there a way to use llama-index only on the indexing side?
When I create VectorStoreIndex object, why does it require ChatGPT or some other LLM that will be used at the query time?
Llamaindex SQLTableRetrieverQueryEngine not generating the correct SQL
I am using LLamaindex SQLTableRetrieverQueryEngine for natural language to SQL interface. My schema has one of the table called ‘Suppliers’ which has the columns ‘Name’ and ‘ContactInfo’. One of the row values are ‘FitLife Sports Gear’ for Name, ‘[email protected]’ for ContactInfo.
llama-index RelevancyEvaluator passes every source node
I’m using RelevancyEvaluator when looping through the source_nodes of a query_engine response, and the .evaluate() says that every source node is passing (result.passing returns True). This is of course not correct, and is preventing me from obtaining the correct source node that was used by the llm to answer my query.