Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of sylvain@datastax.com designates
 209.85.220.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <A663AF0EC22BAB47966CA61D63C01B385606D23C@mcm-exch-mb.MoonCapital.Corp>
References: 
 <CAEfD-ZASrReozjpQ7uQ6aUB_-bNfQiBE+cJVzaw20DOP6+WnQg@mail.gmail.com>
	<CAEfD-ZBKAExmCnbw20Ji1bmC6gX-O_Jkr8HhZ298n6750nX1-A@mail.gmail.com>
	<A663AF0EC22BAB47966CA61D63C01B385606D22F@mcm-exch-mb.MoonCapital.Corp>
	<A663AF0EC22BAB47966CA61D63C01B385606D231@mcm-exch-mb.MoonCapital.Corp>
	<41A0E175-CC7F-49CE-8D1C-5B6624777D19@thelastpickle.com>
	<A663AF0EC22BAB47966CA61D63C01B385606D232@mcm-exch-mb.MoonCapital.Corp>
	<A663AF0EC22BAB47966CA61D63C01B385606D233@mcm-exch-mb.MoonCapital.Corp>
	<68406753-8A12-4F7F-875D-1CB767F1C8CA@thelastpickle.com>
	<A663AF0EC22BAB47966CA61D63C01B385606D234@mcm-exch-mb.MoonCapital.Corp>
	<08AB4D4C-0569-4B51-A319-377D2280825C@gmail.com>
	<A663AF0EC22BAB47966CA61D63C01B385606D235@mcm-exch-mb.MoonCapital.Corp>
	<A663AF0EC22BAB47966CA61D63C01B385606D236@mcm-exch-mb.MoonCapital.Corp>
	<CAKkz8Q3RyW5HBLeRgE7HbaJhRGBgBZP9R04kja6zo6YrV6yEyA@mail.gmail.com>
	<A663AF0EC22BAB47966CA61D63C01B385606D23C@mcm-exch-mb.MoonCapital.Corp>
Date: Tue, 10 Jul 2012 16:37:19 +0200
Message-ID: 
 <CAKkz8Q23U=4n+PTxXf4O95D26nr6EVd2HYK3siLwSFRTaxOzcA@mail.gmail.com>
Subject: Re: Dynamic CF
From: Sylvain Lebresne <sylvain@datastax.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, Jul 10, 2012 at 4:17 PM, Leonid Ilyevsky
<lilyevsky@mooncapital.com> wrote:
> So I guess, in the batch_mutate call, in the map that I pass to it, only =
the first element of the composite key should be used as a key (because it =
is the real key), and the other parts of the key should be passed as regula=
r columns? Is this correct? While I am waiting for your confirmation, I am =
going to try it.

I would really advise you to use the BATCH statement of CQL3 rather
than the thrift batch_mutate call. If only because until
https://issues.apache.org/jira/browse/CASSANDRA-4377 is resolved it
won't work at all, but also because the whole point of CQL3 is to hide
that kind of complexity.

--
Sylvain

>
> -----Original Message-----
> From: Sylvain Lebresne [mailto:sylvain@datastax.com]
> Sent: Tuesday, July 10, 2012 8:24 AM
> To: user@cassandra.apache.org
> Subject: Re: Dynamic CF
>
> On Fri, Jul 6, 2012 at 10:49 PM, Leonid Ilyevsky
> <lilyevsky@mooncapital.com> wrote:
>> At this point I am really confused about what direction Cassandra is goi=
ng. CQL 3 has the benefit of composite keys, but no dynamic columns.
>> I thought, the whole point of Cassandra was to provide dynamic tables.
>
> CQL3 absolutely provide "dynamic tables"/wide rows, the syntax is just
> different. The typical example for wide rows is a time serie, for
> instance keeping all the events for a given event_kind in the same C*
> row ordered by time. You declare that in CQL3 using:
>   CREATE TABLE events (
>     event_kind text,
>     time timestamp,
>     event_name text,
>     event_details text,
>     PRIMARY KEY (event_kind, time)
>   )
>
> The important part in such definition is that one CQL row (i.e a given
> event_kind, time, event_name, even_details) does not map to an internal
> Cassandra row. More precisely, all events sharing the same event_kind wil=
l be
> in the same internal row. This is a wide row/dynamic table in the sense o=
f
> thrift.
>
>
>> I need to have a huge table to store market quotes, and be able to query=
 it by name and timestamp (t1 <=3D t <=3D t2), therefore I wanted the compo=
site key.
>> Loading data to such table using prepared statements (CQL 3-based) was v=
ery slow, because it makes a server call for each row.
>
> You should use a BATCH statement which is the equivalent to batch_mutate.
>
> --
> Sylvain
>
> This email, along with any attachments, is confidential and may be legall=
y privileged or otherwise protected from disclosure. Any unauthorized disse=
mination, copying or use of the contents of this email is strictly prohibit=
ed and may be in violation of law. If you are not the intended recipient, a=
ny disclosure, copying, forwarding or distribution of this email is strictl=
y prohibited and this email and any attachments should be deleted immediate=
ly.  This email and any attachments do not constitute an offer to sell or a=
 solicitation of an offer to purchase any interest in any investment vehicl=
e sponsored by Moon Capital Management LP ("Moon Capital"). Moon Capital do=
es not provide legal, accounting or tax advice. Any statement regarding leg=
al, accounting or tax matters was not intended or written to be relied upon=
 by any person as advice. Moon Capital does not waive confidentiality or pr=
ivilege as a result of this email.