[
https://issues.apache.org/jira/browse/CASSANDRA-16996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17421287#comment-17421287
]
Berenguer Blasi commented on CASSANDRA-16996:
---------------------------------------------
The latest push seems ok test wise
[j11|https://app.circleci.com/pipelines/github/bereng/cassandra/443/workflows/0f2e1f0b-4a48-41b2-8fb1-8b8c9ed5b840]
[j8|https://app.circleci.com/pipelines/github/bereng/cassandra/443/workflows/b55a6248-4197-4246-88dd-a8cafc879288]
besides the related junit failure fix I just pushed. I still want to give this
one more thought before moving into review...
> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
