[
https://issues.apache.org/jira/browse/CASSANDRA-16996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17433013#comment-17433013
]
Caleb Rackliffe commented on CASSANDRA-16996:
---------------------------------------------
Except for the [one remaining
issue|https://github.com/apache/cassandra/pull/1278/files?authenticity_token=mRk1HCiqlaBpW%2BQQMMaRRuV4n68Frlnv1PNIOF18a5nAZYUHAZrX8pHh2DQ1pg4EjptTTct%2FyZbhCDRLSg3xhg%3D%3D&file-filters%5B%5D=.java#r734593004]
we need to fix, I'm +1 on all 3 PRs at this point, assuming clean tests.
> Prevent broken concurrent schema read/writes
> --------------------------------------------
>
> Key: CASSANDRA-16996
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16996
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Schema
> Reporter: Berenguer Blasi
> Assignee: Berenguer Blasi
> Priority: Normal
> Fix For: 3.11.x, 4.0, 4.x
>
>
> See CASSANDRA-16856 where the concurrent read/write path was left out
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
