[ https://issues.apache.org/jira/browse/CASSANDRA-15833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17135833#comment-17135833 ]
Jacek Lewandowski commented on CASSANDRA-15833: ----------------------------------------------- [~jwest] thank you for having a look. I know about those inconsistencies depending on which node is coordinator, I discovered them later after creating this patch though. The test you created looks great. I'll add more queries that may be affected by this problem, IIRC I also saw some inconsistencies when executing conditional delete but I need to re-check that. Feel free to move the ticket back in "in-progress"-like state > Unresolvable false digest mismatch during upgrade due to CASSANDRA-10657 > ------------------------------------------------------------------------ > > Key: CASSANDRA-15833 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15833 > Project: Cassandra > Issue Type: Bug > Components: Consistency/Repair > Reporter: Jacek Lewandowski > Assignee: Jacek Lewandowski > Priority: Normal > Fix For: 3.11.x, 4.0-alpha > > Attachments: CASSANDRA-15833-3.11.patch, CASSANDRA-15833-4.0.patch > > > CASSANDRA-10657 introduced changes in how the ColumnFilter is interpreted. > This results in digest mismatch when querying incomplete set of columns from > a table with consistency that requires reaching instances running pre > CASSANDRA-10657 from nodes that include CASSANDRA-10657 (it was introduced in > Cassandra 3.4). > The fix is to bring back the previous behaviour until there are no instances > running pre CASSANDRA-10657 version. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org