Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: ValueError: Vector search index does not exist for the Neptune Analytics graph. #17527

Open
fengmen-amz opened this issue Jan 16, 2025 · 3 comments
Labels
bug Something isn't working triage Issue needs to be triaged/prioritized

Comments

@fengmen-amz
Copy link

Bug Description

Received the error when following the tutorial at https://docs.llamaindex.ai/en/stable/examples/vector_stores/AmazonNeptuneVectorDemo/

I made sure to start from a clean python environment. See logs for package versions.

Version

0.12.11

Steps to Reproduce

pip install --upgrade llama_index
pip install --upgrade llama-index-vector-stores-neptune
from llama_index.vector_stores.neptune import NeptuneAnalyticsVectorStore

graph_identifier = ""
embed_dim = 1536

neptune_vector_store = NeptuneAnalyticsVectorStore(
    graph_identifier=graph_identifier, embedding_dimension=1536
)

Relevant Logs/Tracbacks

ValueError                                Traceback (most recent call last)
Cell In[1], line 6
      3 graph_identifier = ""
      4 embed_dim = 1536
----> 6 neptune_vector_store = NeptuneAnalyticsVectorStore(
      7     graph_identifier=graph_identifier, embedding_dimension=1536
      8 )

File ~/.conda/envs/llamaindex/lib/python3.9/site-packages/llama_index/vector_stores/neptune/base.py:115, in NeptuneAnalyticsVectorStore.__init__(self, graph_identifier, embedding_dimension, client, credentials_profile_name, region_name, hybrid_search, node_label, text_node_property, retrieval_query, **kwargs)
    108         raise ValueError(
    109             "Could not load credentials to authenticate with AWS client. "
    110             "Please check that credentials in the specified "
    111             "profile name are valid."
    112         ) from e
    114 # Verify that the analytics graph has a vector search index and that the dimensions match
--> 115 self._verify_vectorIndex()

File ~/.conda/envs/llamaindex/lib/python3.9/site-packages/llama_index/vector_stores/neptune/base.py:132, in NeptuneAnalyticsVectorStore._verify_vectorIndex(self)
    128         raise ValueError(
    129             f"Vector search index dimension for Neptune Analytics graph does not match the provided value."
    130         )
    131 else:
--> 132     raise ValueError(
    133         f"Vector search index does not exist for the Neptune Analytics graph."
    134     )

ValueError: Vector search index does not exist for the Neptune Analytics graph.

llama-cloud                             0.1.8
llama-index                             0.12.11
llama-index-agent-openai                0.4.1
llama-index-cli                         0.4.0
llama-index-core                        0.12.11
llama-index-embeddings-openai           0.3.1
llama-index-indices-managed-llama-cloud 0.6.3
llama-index-llms-openai                 0.3.13
llama-index-multi-modal-llms-openai     0.4.2
llama-index-program-openai              0.3.1
llama-index-question-gen-openai         0.3.0
llama-index-readers-file                0.4.2
llama-index-readers-llama-parse         0.4.0
llama-index-vector-stores-neptune       0.3.1
llama-parse                             0.5.19
@fengmen-amz fengmen-amz added bug Something isn't working triage Issue needs to be triaged/prioritized labels Jan 16, 2025
Copy link

dosubot bot commented Jan 16, 2025

To resolve the "ValueError: Vector search index does not exist for the Neptune Analytics graph" error, ensure that your Amazon Neptune Analytics graph has a vector search index configured. This error occurs when the vectorSearchConfiguration is missing in the response from the get_graph call in the NeptuneAnalyticsVectorStore class.

Here are the steps you should follow:

  1. Verify Vector Search Index Configuration: Check that your Neptune Analytics graph has a vector search index set up. This can typically be done through the AWS Management Console or using AWS CLI commands.

  2. Match Embedding Dimension: Ensure that the vector search index's dimension matches the embedding_dimension you specified (1536 in your case).

  3. Correct Graph Identifier: Double-check that the graph_identifier you are using is correct and corresponds to the graph with the vector search index.

If the vector search index is not configured, you will need to set it up in your Neptune Analytics graph. Additionally, make sure you have the correct version of the boto3 library (1.34.40 or greater) installed, as it is required for the NeptuneAnalyticsVectorStore to function properly [1].

To continue talking to Dosu, mention @dosu.


Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other

@logan-markewich
Copy link
Collaborator

I would appreciate any help making a fix for this. I'm not sure when I'll get time to setup Neptune (you might be the second person I've ever seen use this since it was contributed)

@fengmen-amz
Copy link
Author

Yeah, I am looking into it. In fact, the other bug on Neptune also came from me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage Issue needs to be triaged/prioritized
Projects
None yet
Development

No branches or pull requests

2 participants