deleteOne deleteMany for tables using OperationAttempt #1551
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
Changes the warnings associated commands to use the new ApiExcpetions, and `warnings` in the return status now returns a list of error object V2. To do that needed to improve the way CommandResult was built, so it always had a status map so the CommandProcessor could append a warning. To do that expanded the CommandResultBuilder added for the OperationAttempts, removed the many overloads used for CommandResult, and updated all creation of the CommandResult to use the builder. See also #1518 to continue this
…cResponses Missed adding errors to the CommandResult builder for per document responses in InsertOperationPage
- change CommandErrorV2 property to match bean style - change CreateKeyspaceIntegrationTest to get new response warning
and made both create and drop tests check the names of the commands in the message
- our schema cache was not invalidating when a table was changed, so we would always give out missing index errors rather than errors when index was there but did not support the operation - updated integration tests for the full error in the warning, and made them check the id for the warning - big fix, we were not turning on allow filtering when doing a comparison query for some data types on indexed columns
Waiting for the WhereCQLClauseAnalyzer to get strategy so it can check the where for a delete
4 tasks
…eration-attempt # Conflicts: # src/main/java/io/stargate/sgv2/jsonapi/service/operation/tables/WhereCQLClauseAnalyzer.java
|
Added Integration tests for DeleteOne, DeleteMany |
Yuqi-Du
approved these changes
Oct 21, 2024
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.
WIP waiting for WhereCQLClauseAnalyzer to get strategy for delete.
NOTE: no integration tests yet, and we need a where analysis strategy for deleteOne and deleteMany
For deleteOne, the full PK must be specified. For deleteMany a partial PK (with full partition keys) is acceptable.
What this PR does:
Which issue(s) this PR fixes:
Fixes #
Checklist