Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <CAOBz8JYpk5LFM_iiSYjdP6A76aUnXLmJT5DY_SvS0RJVtHzZFQ@mail.gmail.com>
References: <1615137824361324314.124242oleg.dulin-gmail.com@news.gmane.org>
	<CAJ=yfkNU+mHXddOVHJhVbj+qKXuSF74-GR60zYv=ozC2e_BbCQ@mail.gmail.com>
	<4FD94BD1.1060807@mebigfatguy.com>
	<CAP=kKf-Um1hqXOJRWfHRnVzo=aD6_5Sno9sUh9LxFC1Zkdu=DA@mail.gmail.com>
	<CAJ=yfkNZWM0H-eteE5fNtwuEWSPfLUg3eU3HHGE7NoTq_rMtTQ@mail.gmail.com>
	<CAOBz8JYpk5LFM_iiSYjdP6A76aUnXLmJT5DY_SvS0RJVtHzZFQ@mail.gmail.com>
Date: Thu, 14 Jun 2012 10:36:32 -0500
Message-ID: 
 <CAJ=yfkPjVFtANHOAwHsOQ-hoqiPGV0c8g14RfmP8DZb7eDNaVg@mail.gmail.com>
Subject: Re: Supercolumn behavior on writes
From: Greg Fausak <greg@named.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Derek,

Thanks for that!

Yes, I am aware of that technique.  I am currently using something
very similar on an sql database.  I think one of the great benefits with
Cassandra is that you can invent these on the fly.  I also think there
is great benefit to keep all of the columns in the same row.

Anyway, I didn't mean to hijack Oleg's thread.  I am interested
in the original question about the serialization/deserialization on write.
Does anybody know?

-g


On Wed, Jun 13, 2012 at 11:45 PM, Derek Williams <derek@fyrie.net> wrote:
> On Wed, Jun 13, 2012 at 9:08 PM, Greg Fausak <greg@named.com> wrote:
>>
>> Interesting.
>>
>> How do you do it?
>>
>> I have a version 2 CF, that works fine.
>> A version 3 table won't let me invent columns that
>> don't exist yet. (for composite tables). =A0What's the trick?
>
>
> You are able to get the same behaviour as non cql by doing something like
> this:
>
> CREATE TABLE mytable (
> =A0 id bigint,
> =A0 name text,
> =A0 value text,
> =A0 PRIMARY KEY (id, name)
> ) WITH COMPACT STORAGE;
>
> This table will work exactly like a standard column family with no define=
d
> columns. For example:
>
> cqlsh:testing>=A0INSERT INTO mytable (id, name, value) VALUES (1, 'firstn=
ame',
> 'Alice');
> cqlsh:testing>=A0INSERT INTO=A0mytable (id, name, value)=A0VALUES=A0(1, '=
email',
> 'alice@example.org');
> cqlsh:testing>=A0INSERT INTO=A0mytable (id, name, value)=A0VALUES=A0(2, '=
firstname',
> 'Bob');
> cqlsh:testing>=A0INSERT INTO=A0mytable (id, name, value)=A0VALUES=A0(2, '=
webpage',
> 'http://bob.example.org');
> cqlsh:testing>=A0INSERT INTO=A0mytable (id, name, value)=A0VALUES=A0(2, '=
email',
> 'bob@example.org');
>
> cqlsh:testing>=A0SELECT name, value FROM mytable WHERE id =3D 2;
> =A0name =A0 =A0 =A0| value
> -----------+------------------------
> =A0 =A0 =A0email | =A0 =A0 =A0 =A0bob@example.org
> =A0firstname | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Bob
> =A0 =A0webpage | http://bob.example.org
>
> Not very exciting, but when you take a look with cassandra-cli:
>
> [default@testing] get mytable[2];
> =3D> (column=3Demail, value=3Dbob@example.org, timestamp=3D13396482702840=
00)
> =3D> (column=3Dfirstname, value=3DBob, timestamp=3D1339648270275000)
> =3D> (column=3Dwebpage, value=3Dhttp://bob.example.org,
> timestamp=3D1339648270280000)
> Returned 3 results.
> Elapsed time: 11 msec(s).
>
> which is exactly what you would expect from a normal cassandra column
> family.
>
> So the trick is to separate your static columns and your dynamic columns
> into separate column families.=A0Column names and types can of course be
> something different then my example, and inserts can be done within a
> 'BATCH' to avoid multiple round trips.
>
> Also, I'm not trying to advocate this as being a better solution then jus=
t
> using the old thrift interface, I'm just showing an example of how to do =
it.
> I personally do prefer this way as it is more predictable, but of course
> others will have a different opinion.
>
> --
> Derek Williams
>