Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 92536 invoked from network); 23 Feb 2011 01:13:38 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 23 Feb 2011 01:13:38 -0000 Received: (qmail 78081 invoked by uid 500); 23 Feb 2011 01:13:37 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 78027 invoked by uid 500); 23 Feb 2011 01:13:36 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 78019 invoked by uid 500); 23 Feb 2011 01:13:36 -0000 Delivered-To: apmail-incubator-cassandra-user@incubator.apache.org Received: (qmail 78016 invoked by uid 99); 23 Feb 2011 01:13:36 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Feb 2011 01:13:36 +0000 X-ASF-Spam-Status: No, hits=2.0 required=5.0 tests=FREEMAIL_FROM,SPF_NEUTRAL,T_TO_NO_BRKTS_FREEMAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: 216.139.236.26 is neither permitted nor denied by domain of tijoriwala.ritesh@gmail.com) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Feb 2011 01:13:29 +0000 Received: from jim.nabble.com ([192.168.236.80]) by sam.nabble.com with esmtp (Exim 4.69) (envelope-from ) id 1Ps3Hw-0000ND-MW for cassandra-user@incubator.apache.org; Tue, 22 Feb 2011 17:13:08 -0800 Date: Tue, 22 Feb 2011 17:13:08 -0800 (PST) From: "tijoriwala.ritesh" To: cassandra-user@incubator.apache.org Message-ID: <1298423588691-6054806.post@n2.nabble.com> In-Reply-To: <415F86341B2D7B4480FAE34D76D00DB2010D87DC87@NYKPCMMGMB07.INTRANET.BARCAPINT.COM> References: <1298422796915-6054778.post@n2.nabble.com> <415F86341B2D7B4480FAE34D76D00DB2010D87DC87@NYKPCMMGMB07.INTRANET.BARCAPINT.COM> Subject: Re: Does Cassandra use vector clocks MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Thanks for the quick reply. I found this ticket https://issues.apache.org/jira/browse/CASSANDRA-580 which talks about vector clock support in Cassandra but it was marked as "won't fix". It would be insightful to know why it was rejected. If Cassandra relies on timestamps, does it mean that clients have to be clock synchronized? This is very difficult in distributed systems. -- View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Does-Cassandra-use-vector-clocks-tp6054778p6054806.html Sent from the cassandra-user@incubator.apache.org mailing list archive at Nabble.com.