Astra DB: explicit projection when reading from Astra DB #3013
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.
In view of upcoming changes in the Astra DB Data API, this PR explicitly sets a projection every time a
find
command (or equivalent) is executed, in order to ensure all necessary fields of the document are returned by the API.This occurs in the two method calls
find_one
andvector_find
in the testtest-ingest-astra-output.py
.With this change, future versions of the Data API, which may implement an exclude-vector-by-default policy, will not cause any disruption in these tests.