-
Notifications
You must be signed in to change notification settings - Fork 15.8k
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
community: update VDMS vectorstore with latest VDMS release #28443
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for the update!
before fully reviewing, could you provide a bit more context? seems like there's some breaking changes, are these necessary for compatibility with the new vdms release? or are those two separate things
embedding: Optional[Embeddings] = None, | ||
collection_name: str = DEFAULT_COLLECTION_NAME, # DescriptorSet name | ||
distance_strategy: DISTANCE_METRICS = "L2", | ||
embedding: Embeddings, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
breaking change
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@baskaryan, this change wasn't necessary. I reverted it
Deployment failed with the following error:
|
@baskaryan could you please review this? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cwlacewe I'm going to close this for now with the recommendation that you / Intel implement the VDMS vector store in a new package (e.g., langchain-vdms
or langchain-intel
).
We've written a walkthrough on this process here and are happy to answer your questions as you go through it:
https://python.langchain.com/docs/contributing/how_to/integrations/
We are encouraging contributors of LangChain integrations to go this route. This way we don't have to be in the loop for reviews, you're able to properly integration test the code, and you have control over versioning.
I think this route is preferable to reviewing a large code change (thousands of lines), only to have the implementation deprecated if/when the standalone package is released.
Docs would continue to be maintained in the langchain
repo.
Let me know what you think!
"FindDescriptor", {"entities": list(), "returned": 0, "status": 0} | ||
) | ||
new_response = [ | ||
# {"FindDescriptor": {"returned": 0, "status": 0, "entities": []}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# {"FindDescriptor": {"returned": 0, "status": 0, "entities": []}} |
# else: | ||
# kwargs["normalize_distance"] = True |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we handle the else
condition here?
ids=ids, | ||
metadatas=metadatas, | ||
batch_size=batch_size, | ||
# Remove IDs if exist-TEST_REMOVAL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is meant by -TEST_REMOVAL
?
@ccurme is there a way to get this one integrated as we have customers waiting and we can work on the package for new year? |
Description:
Issue: N/A
Dependencies: N/A