Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 90343200C88 for ; Fri, 2 Jun 2017 19:54:09 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 8D699160BDD; Fri, 2 Jun 2017 17:54:09 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id D5233160BBA for ; Fri, 2 Jun 2017 19:54:08 +0200 (CEST) Received: (qmail 94435 invoked by uid 500); 2 Jun 2017 17:54:08 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 94424 invoked by uid 99); 2 Jun 2017 17:54:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Jun 2017 17:54:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 935041858C8 for ; Fri, 2 Jun 2017 17:54:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id b3P0LQo1_UUK for ; Fri, 2 Jun 2017 17:54:06 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 3C69560D6D for ; Fri, 2 Jun 2017 17:54:06 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 43B52E0BDF for ; Fri, 2 Jun 2017 17:54:05 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 706E92400B for ; Fri, 2 Jun 2017 17:54:04 +0000 (UTC) Date: Fri, 2 Jun 2017 17:54:04 +0000 (UTC) From: "Matt Byrd (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-10699) Make schema alterations strongly consistent MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 02 Jun 2017 17:54:09 -0000 [ https://issues.apache.org/jira/browse/CASSANDRA-10699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035130#comment-16035130 ] Matt Byrd commented on CASSANDRA-10699: --------------------------------------- In particular I'm interested in how to avoid concurrent schema changes causing problems. [~iamaleksey] Is the plan to use Paxos to linearise the schema changes? > 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 > Assignee: Matt Byrd > Fix For: 4.0 > > > 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.15#6346) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org For additional commands, e-mail: commits-help@cassandra.apache.org