Update feature matrix for Astra DB vector store integration #1159
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.
Overview
This PR updates the feature matrix for the Astra DB vector store integration.
Type of change
Type: Update existing documentation
Checklist
docs devsrc/docs.jsonif neededAdditional notes
This PR marks these two attributes as "yes" for the Astra DB Vector Store component: passes standard tests and multi tenancy.
For the first item, the component uses the entire vectorstore suite from the
langchain-testsin its CI/CD and passes it.For the multi-tenancy, Astra DB is a cloud database: as such, is it my understanding that it is inherently multitenant, as each user comes with their own auth token and accesses their own databases there through DB-specific endpoints (see e.g. here). In that respect, it is not different than e.g. the Mongo DB Atlas vector store, likewise marked as multitenant in the feature matrix.