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

Francisco Guerrero updated CASSANDRA-19351:
-------------------------------------------
    Test and Documentation Plan: Removed synchronization blocks only, since we 
already rely on correct synchronization on the {{Schema.instance}}.
                         Status: Patch Available  (was: In Progress)

PR: https://github.com/apache/cassandra-analytics/pull/37
CI: https://app.circleci.com/pipelines/github/frankgh/cassandra-analytics/107

> [Analytics] No longer need to synchronize on Schema.instance after Cassandra 
> 4.0.12
> -----------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-19351
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-19351
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Analytics Library
>            Reporter: Francisco Guerrero
>            Assignee: Francisco Guerrero
>            Priority: Normal
>             Fix For: NA
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> We no longer need to synchronize on the {{Schema.instance}} in Analytics 
> after the release of Cassandra 4.0.12, that includes a synchronization fix in 
> https://issues.apache.org/jira/browse/CASSANDRA-18317. We need to clean up 
> the TODOs pending on that code being released



--
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

Reply via email to