[
https://issues.apache.org/jira/browse/CASSANDRA-21061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-21061:
--------------------------------------
Bug Category: Parent values: Correctness(12982)Level 1 values:
Unrecoverable Corruption / Loss(13161)
Complexity: Low Hanging Fruit
Discovered By: Fuzz Test
Fix Version/s: 6.x
Severity: Critical
Status: Open (was: Triage Needed)
> 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
>
>
> 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]
