[
https://issues.apache.org/jira/browse/CASSANDRA-18317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17751155#comment-17751155
]
Francisco Guerrero commented on CASSANDRA-18317:
------------------------------------------------
[~ifesdjeen] thanks for looking into this and thanks for your ideas. I have
reviewed carefully the ideas, and it makes a lot of sense. I am okay to go with
either approach, however I feel like bringing this change into 4.0 might be
more than what we want to do for a branch that is not actively being developed.
Especially considering this is no longer an issue in 4.1 and 5.0. I'm +0 on the
CAS approaches you propose, but if you feel it's worth making this change in
4.0, I can go ahead and apply your suggestions to the PR. Let me know what your
thoughts are on this.
> Properly synchronize CQLSSTableWriter#build on the Schema.instance
> ------------------------------------------------------------------
>
> Key: CASSANDRA-18317
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18317
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/bulk load
> Reporter: Francisco Guerrero
> Assignee: Francisco Guerrero
> Priority: Normal
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The {{CQLSSTableWriter#build}} method should properly synchronize on the
> {{Schema.instance}} class to prevent concurrent Schema operations fail, [when
> the offline tool also updates schema].
> For example, a table creation operation, which modifies the keyspaces tables
> metadata, might end up missing the update when a concurrent call to the
> {{CQLSSTableWriter#build}} method is accessing the {{Schema}} instance.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
