[
https://issues.apache.org/jira/browse/CASSANDRA-20188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17911569#comment-17911569
]
Paul Chandler commented on CASSANDRA-20188:
-------------------------------------------
I have tested 4.1 -> 5.0 now, and I am pleased to confirm that the hint files
are processed correctly now. Thank you.
> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
