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

fix chatvectordbchain to use pinecone namespace #1139

Merged
merged 2 commits into from
Feb 18, 2023

Conversation

kekayan
Copy link
Contributor

@kekayan kekayan commented Feb 18, 2023

In the similarity search, the pinecone namespace is not used, which makes the bot return I don't know where the embeddings are stored in the pinecone namespace. Now we can query by passing the namespace optionally.
result = qa({"question": query, "chat_history": chat_history, "namespace":"01gshyhjcfgkq1q5wxjtm17gjh"})

@hwchase17
Copy link
Contributor

lets try to make this a bit more general - can we change it to something like vectordbkwargs = inputs.get(vectordbkwargs, {}) and then pass those as **vectordbkwargs? that way its extensible to other params as well!

@kekayan
Copy link
Contributor Author

kekayan commented Feb 18, 2023

sure, I will do the changes now

@kekayan
Copy link
Contributor Author

kekayan commented Feb 18, 2023

pushed the change as you suggested @hwchase17

@hwchase17 hwchase17 merged commit 9111f4c into langchain-ai:master Feb 18, 2023
@blob42 blob42 mentioned this pull request Feb 21, 2023
zachschillaci27 pushed a commit to zachschillaci27/langchain that referenced this pull request Mar 8, 2023
In the similarity search, the pinecone namespace is not used, which
makes the bot return _I don't know_ where the embeddings are stored in
the pinecone namespace. Now we can query by passing the namespace
optionally.
```result = qa({"question": query, "chat_history": chat_history, "namespace":"01gshyhjcfgkq1q5wxjtm17gjh"})```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants