Update to pinecone-plugin-inference=2.0.0 #397
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Updates
pinecone-plugin-inference
to new major version2.0.0
.From the 2.0.0 release notes:
Reusing top-level exceptions from
pinecone
clientExceptions in the Pinecone Inference SDK have been reworked to throw the top-level exceptions declared in the Pinecone Python SDK as opposed to plugin-specific duplications of those exceptions, which was confusing to users.
Old
Previously, exceptions in the Python Inference SDK were redeclared/duplicated in an obscure package, leading to a poor user experience when working with what should otherwise be standard Pinecone exceptions.
For example, a user who wanted to catch and handle
PineconeApiException
would have to know to enter:New
Now, the Inference SDK reuses exceptions from the top-level Pinecone SDK, allowing the user to simply enter:
Solution
Describe the approach you took. Link to any relevant bugs, issues, docs, or other resources.
Type of Change
Test Plan
Describe specific steps for validating this change.