[ https://issues.apache.org/jira/browse/CASSANDRA-16996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17429375#comment-17429375 ]
Caleb Rackliffe commented on CASSANDRA-16996: --------------------------------------------- With the discussion over how to test this in a better place, I've thrown my +1 (and one more non-controversial nit) on the PR. I'm still in favor of removing {{testSchemaPullSynchoricity()}}, but I'm fine leaving a second reviewer ([~jlewandowski]?), which we should probably grab, given there is concurrency involved here, to break that tie ;) > 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