[ 
https://issues.apache.org/jira/browse/CASSANDRA-20188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brandon Williams updated CASSANDRA-20188:
-----------------------------------------
          Fix Version/s: 4.0.16
                         4.1.8
                         5.0.3
                         5.1
                             (was: 5.x)
                             (was: 4.0.x)
                             (was: 4.1.x)
                             (was: 5.0.x)
          Since Version: 0.7.1
    Source Control Link: 
https://github.com/apache/cassandra/commit/64b8d6b9add607b80752cd1a8fbce51839af9ec4
             Resolution: Fixed
                 Status: Resolved  (was: Ready to Commit)

Thanks, committed.

And with that I have undone a restriction I added 14 years ago.

> 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.16, 4.1.8, 5.0.3, 5.1
>
>
> 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]

Reply via email to