-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update on tables using OperationAttempt #1552
Conversation
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
Waiting for the WhereCQLClauseAnalyzer to get strategy so it can check the where for a update
…eration-attempt # Conflicts: # src/main/java/io/stargate/sgv2/jsonapi/service/operation/tables/WhereCQLClauseAnalyzer.java
…empt' into ajm/update-command-operation-attempt
…r table updateOne
Table UpdateOne (UpdateMany is not supported)
Currently, I added these rule checks in ColumnAssignment constructor. here |
There is one thing weird, that is the status map for table updateOne. We always construct this status map in UpdateAttemptPage.
I know we can't know the update is successful or not, but is this response body needed? |
…eration-attempt # Conflicts: # src/main/java/io/stargate/sgv2/jsonapi/api/model/command/CommandResultBuilder.java # src/main/java/io/stargate/sgv2/jsonapi/service/operation/collections/DeleteOperationPage.java # src/main/java/io/stargate/sgv2/jsonapi/service/operation/tables/CreateTableAttempt.java # src/main/java/io/stargate/sgv2/jsonapi/service/operation/tables/DeleteTableOperation.java # src/main/java/io/stargate/sgv2/jsonapi/service/operation/tables/UpdateTableOperation.java # src/main/java/io/stargate/sgv2/jsonapi/service/operation/tables/WhereCQLClauseAnalyzer.java # src/test/java/io/stargate/sgv2/jsonapi/api/v1/tables/TableFilterIntegrationTest.java # src/test/java/io/stargate/sgv2/jsonapi/api/v1/util/DataApiResponseValidator.java # src/test/java/io/stargate/sgv2/jsonapi/api/v1/util/DataApiTableCommandSender.java
…eration-attempt # Conflicts: # src/main/java/io/stargate/sgv2/jsonapi/service/operation/DeleteAttemptPage.java # src/main/java/io/stargate/sgv2/jsonapi/service/operation/tables/DeleteAttemptBuilder.java
pair up with unit tests and IT tests
pair up with unit tests and IT tests
…rgate/jsonapi into ajm/update-command-operation-attempt
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
perms broken, reviewed in person some changes
src/main/java/io/stargate/sgv2/jsonapi/exception/UpdateException.java
Outdated
Show resolved
Hide resolved
src/main/java/io/stargate/sgv2/jsonapi/service/resolver/update/TableUpdateAnalyzer.java
Outdated
Show resolved
Hide resolved
src/main/java/io/stargate/sgv2/jsonapi/service/resolver/update/TableUpdateAnalyzer.java
Show resolved
Hide resolved
src/main/java/io/stargate/sgv2/jsonapi/service/resolver/update/TableUpdateAnalyzer.java
Show resolved
Hide resolved
src/main/java/io/stargate/sgv2/jsonapi/service/resolver/update/TableUpdateAnalyzer.java
Outdated
Show resolved
Hide resolved
src/main/java/io/stargate/sgv2/jsonapi/service/resolver/update/TableUpdateAnalyzer.java
Show resolved
Hide resolved
src/main/java/io/stargate/sgv2/jsonapi/service/resolver/update/TableUpdateResolver.java
Show resolved
Hide resolved
src/main/java/io/stargate/sgv2/jsonapi/service/resolver/UpdateOneCommandResolver.java
Outdated
Show resolved
Hide resolved
src/main/java/io/stargate/sgv2/jsonapi/service/resolver/update/TableUpdateResolver.java
Show resolved
Hide resolved
…eration-attempt # Conflicts: # src/test/java/io/stargate/sgv2/jsonapi/fixtures/testdata/TestData.java
Waiting for the WhereCQLClauseAnalyzer to get strategy so it can check the where for a update
NOTE: builds on #1551
NOTE: no integration tests yet, and we need a where analysis strategy for updateOne - user must specify the full PK
What this PR does:
Which issue(s) this PR fixes:
Fixes #
Checklist