[jira] [Commented] (CASSANDRA-10699) Make schema alterations strongly consistent

["Aleksey Yeschenko (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-10699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15187068#comment-15187068 ] 

Aleksey Yeschenko commented on CASSANDRA-10699:
-----------------------------------------------

bq. Will resolution of this ticket enable concurrent clients to successfully perform CREATE TABLE IF NOT EXISTS? Or will that still be problematic? I just want to know if this is the ticket to point people to for concurrent CREATE TABLE IF NOT EXISTS issues.

Yes. But I'm not sure why you are singling out the {{IF NOT EXISTS}} case. Both plain {{CREATE TABLE}} and {{CREATE TABLE IF NOT EXISTS}} require strongly consistent schema to work 100% correctly.

> Make schema alterations strongly consistent
> -------------------------------------------
>
>                 Key: CASSANDRA-10699
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10699
>             Project: Cassandra
>          Issue Type: Sub-task
>            Reporter: Aleksey Yeschenko
>             Fix For: 3.x
>
>
> Schema changes do not necessarily commute. This has been the case before CASSANDRA-5202, but now is particularly problematic.
> We should employ a strongly consistent protocol instead of relying on marshalling {{Mutation}} objects with schema changes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)