[
https://issues.apache.org/jira/browse/CASSANDRA-20188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17911244#comment-17911244
]
Brandon Williams commented on CASSANDRA-20188:
----------------------------------------------
That is turning out to be more difficult than I anticipated. I made a [jvm
dtest|https://github.com/driftx/cassandra/commit/0a871c1214e9da029d67428aa169a659db739b6e#diff-84323bafb5928aeeedd50f634b051260d02b546ec4e6dbb70eabecd9ebbd8ae9R172]
which works, but needs to suppress an IRE from an undeliverable hint and I
haven't gotten the uncaught exception filter to work, so it fails after
actually passing. Unfortunately we don't expose enough hint information for a
python dtest to handle this with JMX polling.
> Allow hint delivery during schema mismatch
> ------------------------------------------
>
> Key: CASSANDRA-20188
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20188
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Consistency/Hints
> Reporter: Brandon Williams
> Assignee: Brandon Williams
> Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x
>
>
> In CASSANDRA-2083 we made hints require schema agreement to avoid a flood of
> errors in case the table the hints were destined for did not yet exist.
> This, however, has other undesirable effects, such as making keeping upgrades
> in a mixed mode over a longer period of time less tenable. We should still
> try to deliver hints and back off if the destination table doesn't exist.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
