[
https://issues.apache.org/jira/browse/CASSANDRA-21061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-21061:
--------------------------------------
Since Version: NA
Source Control Link:
https://github.com/apache/cassandra/commit/9c8ab8809d618f6d34316d131accef9ecd4b29a9
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> Accord: write rejections would be returned to users as server errors rather
> than INVALID and TxnReferenceOperation didn't handle all collections prperly
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-21061
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21061
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Accord
> Reporter: David Capwell
> Assignee: David Capwell
> Priority: Normal
> Fix For: 6.x
>
> Attachments:
> ci_summary-trunk-cd22831012ef5d0236b076e1d638a4c031c04dff.html,
> result_details-trunk-cd22831012ef5d0236b076e1d638a4c031c04dff.tar.gz
>
> Time Spent: 4h 50m
> Remaining Estimate: 0h
>
> This was forked from CASSANDRA-20828
> TxnReferenceOperation has not been correctly handling all the different
> collection operations, which would lead to runtime errors.
> Also, when accord generates a write that gets rejected (constraints, specific
> List type operators, etc.) the user would see a server error rather than the
> INVALID error code expected.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
