[
https://issues.apache.org/jira/browse/CASSANDRA-19489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17833340#comment-17833340
]
Caleb Rackliffe edited comment on CASSANDRA-19489 at 4/2/24 11:34 PM:
----------------------------------------------------------------------
trunk CI looks clean (attaching shortly)
({{TestUpgrade_indev_4_0_x_To_indev_trunk}} looks like it also failed while
running tests for CASSANDRA-19284, so it's not new.)
I looked at 4.1, and the problem is we don't even have {{EnableFlag}} there.
I'm going to move forward w/ 5.0 and trunk for now, rather than back-porting
CASSANDRA-17544, CASSANDRA-19018, and who knows what else.
was (Author: maedhroz):
trunk CI looks clean (attaching shortly)
({{TestUpgrade_indev_4_0_x_To_indev_trun}} looks like it also failed while
runnings tests for CASSANDRA-19284, so it's not new.)
I looked at 4.1, and the problem is we don't even have {{EnableFlag}} there.
I'm going to move forward w/ 5.0 and trunk for now, rather than back-porting
CASSANDRA-17544, CASSANDRA-19018, and who knows what else.
> Guardrail to warn clients about possible transient incorrect responses for
> filtering queries against multiple mutable columns
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-19489
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19489
> Project: Cassandra
> Issue Type: Improvement
> Components: Consistency/Coordination, CQL/Semantics, Messaging/Client
> Reporter: Caleb Rackliffe
> Assignee: Caleb Rackliffe
> Priority: Normal
> Fix For: 5.0.x, 5.1
>
> Attachments: ci_summary.html
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Given we may not have time to fully resolve CASSANDRA-19007 before we release
> 5.0, it would still be helpful to have, at the very minimum, a client warning
> for cases where a user filters on two or more mutable (static or regular)
> columns at consistency levels that require coordinator reconciliation. We may
> also want the option to fail these queries outright, although that need not
> be the default.
> The only art involved in this is deciding what we want to say in the
> warning/error message. It's probably reasonable to mention there that this
> only happens when we have unrepaired data. It's also worth noting that SAI
> queries are no longer vulnerable to this after the resolution of
> CASSANDRA-19018.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
