[
https://issues.apache.org/jira/browse/CASSANDRA-10699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15006857#comment-15006857
]
Jim Witschey commented on CASSANDRA-10699:
------------------------------------------
Just so developers working on this know: until we build a system for viewing
test results and filtering out known failures, we are skipping the dtests in
{{concurrent_schema_changes_test.py}} with {{@require(10699)}}.
> 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)
