From user-return-31031-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org Thu Jan 10 19:43:11 2013 Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E6A95EC3F for ; Thu, 10 Jan 2013 19:43:11 +0000 (UTC) Received: (qmail 22883 invoked by uid 500); 10 Jan 2013 19:43:09 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 22856 invoked by uid 500); 10 Jan 2013 19:43:09 -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 22847 invoked by uid 99); 10 Jan 2013 19:43:09 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Jan 2013 19:43:09 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [208.113.200.5] (HELO homiemail-a56.g.dreamhost.com) (208.113.200.5) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Jan 2013 19:43:03 +0000 Received: from homiemail-a56.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a56.g.dreamhost.com (Postfix) with ESMTP id 9A365FE065 for ; Thu, 10 Jan 2013 11:42:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=thelastpickle.com; h=from :content-type:message-id:mime-version:subject:date:references:to :in-reply-to; s=thelastpickle.com; bh=J1sTuQ2jJ3qWUn1K/pUn5Hkw7T k=; b=JwAE9niiVXrLUYtzwGVxv2GGKQW1ELCrCNVob7yIEr26oE1lANvfrLNBE2 znH6a8W6ANzfLvlSH37BzC7XO8Z2fjfosZjE0zxUoPEabtndFolfVtqFDOa9jxJS 6rworGq0uOH1IEJo+VnLSFwyJgu4EfU8rlsL869gSMMhi+gas= Received: from [172.16.1.8] (unknown [203.86.207.101]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: aaron@thelastpickle.com) by homiemail-a56.g.dreamhost.com (Postfix) with ESMTPSA id 1733CFE064 for ; Thu, 10 Jan 2013 11:42:41 -0800 (PST) From: aaron morton Content-Type: multipart/alternative; boundary="Apple-Mail=_50CDD0CE-1405-4E68-AEBA-0985AC98A6FE" Message-Id: <214A3575-ECDD-48D5-920F-3251EA9E9C5E@thelastpickle.com> Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: How long does it take for a write to actually happen? Date: Fri, 11 Jan 2013 08:42:40 +1300 References: To: user@cassandra.apache.org In-Reply-To: X-Mailer: Apple Mail (2.1499) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail=_50CDD0CE-1405-4E68-AEBA-0985AC98A6FE Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 > But Cassandra 1.1.7 is not fully CQL3, yet. Is it? By default 1.1 is CQL 2 1.1 is CQL 3 beta and it not compatible with CQL 3 in 1.2.=20 I do not think there are plans to bring CQL in 1.1 up to the CQL 1.2 = spec. Though I may be wrong there.=20 If you are using a higher level client it will be using thrift, and if = you are not setting the timestamp the client will be doing it for you.=20= In either case it's always good to have the clocks as syncronised as = possible.=20 Cheers ----------------- Aaron Morton Freelance Cassandra Developer New Zealand @aaronmorton http://www.thelastpickle.com On 11/01/2013, at 12:12 AM, Vitaly Sourikov = wrote: > But Cassandra 1.1.7 is not fully CQL3, yet. Is it? I did not have any = timestamps explicitly, as columns, in that CF, but synchronizing clocks = on Cassandra and its clients actually seems to solve the latency problem = I had. So, I just want to make sure that it makes sense. =20 >=20 > And thanks for your responses, Aaron and Vegard. >=20 > Best, > Vitaly Sourikov >=20 > On Thu, Jan 10, 2013 at 1:01 AM, aaron morton = wrote: > And by default in CQL 3 the timestamp is generated server side. >=20 >=20 --Apple-Mail=_50CDD0CE-1405-4E68-AEBA-0985AC98A6FE Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1
But Cassandra 1.1.7 is not = fully CQL3, yet. Is it?
By default 1.1 is CQL 2
1.1 = is CQL 3 beta and it not compatible with CQL 3 in 1.2. 
I do = not think there are plans to bring CQL in 1.1 up to the CQL 1.2 spec. = Though I may be wrong there. 

If you are = using a higher level client it will be using thrift, and if you are not = setting the timestamp the client will be doing it for = you. 

In either case it's always good to = have the clocks as syncronised as = possible. 

Cheers

<= div apple-content-edited=3D"true">
http://www.thelastpickle.com

On 11/01/2013, at 12:12 AM, Vitaly Sourikov <vitaly.sourikov@gmail.com>= ; wrote:

But Cassandra 1.1.7 is not fully CQL3, = yet. Is it? I did not have any timestamps explicitly, as columns, in = that CF, but synchronizing clocks on Cassandra and its clients actually = seems to solve the latency problem I had. So, I just want to make sure = that it makes sense. 

And thanks for your responses, Aaron and = Vegard.

Best,
Vitaly Sourikov

On Thu, Jan 10, 2013 at 1:01 AM, aaron morton = <aaron@thelastpickle.com> wrote:
And by default in CQL = 3 the timestamp is generated server = side.



= --Apple-Mail=_50CDD0CE-1405-4E68-AEBA-0985AC98A6FE--