[Astra DB, vector store] Upgrade to astrapy 1.0 usage #1218
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hemidactylus
changed the title
|
@simonpfish Hello, may I ask you to take a look please? Thank you :) |
|
@anoop-openai sorry for asking again, but could please anyone take a look at this? It should be quick, a matter of upgrading a few calls in the notebook to the latest AstraPy API. Thanks! |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
This PR upgrades the AstraPy version of the notebook to use the stable AstraPy 1.0 (0.x had a different, now obsolete API in some respects).
Motivation
The cookbook before this PR was showing what is now an obsolete (although still functional) way of interacting with the database using the client.
Incidentally, this PR also amends a missing entry in the registry yaml.