Database metadata through name, id, region #217
Closed
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
…ther classes as well (like collection) if needed
|
This is not meant for |
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.
Added dbops calls to the astraDB creation to gather name, id, and region. Exposed through attributes:
astradb.name
astradb.region
astradb.id
Additionally added "name, full_name" to collections as well as the database
col.name
col.fullname
col.database
Also added client_options at the DB level. It is set outside the class so we could expose it at the collection level or within the asyncs.
Also added collection.drop() and changed db.delete_collection() to db.drop_collection()
Tests for everything, everything is passing.
Document with needed items: https://docs.google.com/spreadsheets/d/1ykhgGAqgxdnGJfOWevGDCcD3K6cZPxlGtN99bZTt_S4/edit#gid=2080544998