Return-Path: 
 <user-return-13090-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org>
Delivered-To: apmail-cassandra-user-archive@www.apache.org
Received: (qmail 8039 invoked from network); 8 Feb 2011 17:12:29 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 8 Feb 2011 17:12:29 -0000
Received: (qmail 75576 invoked by uid 500); 8 Feb 2011 17:12:27 -0000
Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org
Received: (qmail 75490 invoked by uid 500); 8 Feb 2011 17:12:24 -0000
Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@cassandra.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@cassandra.apache.org>
List-Post: <mailto:user@cassandra.apache.org>
List-Id: <user.cassandra.apache.org>
Reply-To: user@cassandra.apache.org
Delivered-To: mailing list user@cassandra.apache.org
Received: (qmail 75482 invoked by uid 99); 8 Feb 2011 17:12:23 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Feb 2011 17:12:23 +0000
X-ASF-Spam-Status: No, hits=1.2 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS,URI_HEX
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of dave@meebo-inc.com designates
 74.125.149.209 as permitted sender)
Received: from [74.125.149.209] (HELO na3sys009aog113.obsmtp.com)
 (74.125.149.209)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Feb 2011 17:12:16 +0000
Received: from source ([209.85.220.179]) (using TLSv1) by
 na3sys009aob113.postini.com ([74.125.148.12]) with SMTP
	ID DSNKTVF5Wj+Tj41iFHGkTRXoZCmlEXdKwRq1@postini.com;
 Tue, 08 Feb 2011 09:11:56 PST
Received: by mail-vx0-f179.google.com with SMTP id 40so2618821vxb.10
        for <user@cassandra.apache.org>; Tue, 08 Feb 2011 09:11:54 -0800 (PST)
MIME-Version: 1.0
Received: by 10.220.185.197 with SMTP id cp5mr123322vcb.56.1297185113838; Tue,
 08 Feb 2011 09:11:53 -0800 (PST)
Received: by 10.220.64.201 with HTTP; Tue, 8 Feb 2011 09:11:53 -0800 (PST)
Received: by 10.220.64.201 with HTTP; Tue, 8 Feb 2011 09:11:53 -0800 (PST)
In-Reply-To: <1297168365203-6003775.post@n2.nabble.com>
References: <1297168365203-6003775.post@n2.nabble.com>
Date: Tue, 8 Feb 2011 09:11:53 -0800
Message-ID: <AANLkTik0qkcWRaHHriZY01oT16jpcy-+WbVW2qLg1Ua8@mail.gmail.com>
Subject: Re: Can serialized objects in columns serve as ersatz superCFs?
From: Dave Revell <dave@meebo-inc.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=90e6ba53ad74eb1447049bc871c6
X-Virus-Checked: Checked by ClamAV on apache.org

--90e6ba53ad74eb1447049bc871c6
Content-Type: text/plain; charset=ISO-8859-1

Yes, this works well for me. I have no SCFs but many columns contain JSON.

Depending on your time/space/compatibility tradeoffs you can obviously pick
you own serialization method.

Best,
Dave
On Feb 8, 2011 4:33 AM, "buddhasystem" <potekhin@bnl.gov> wrote:
>
> Seeing that discussion here about indexes not supported in superCFs, and
less
> than clear future of superCFs altogether, I was thinking about getting a
> modicum of same functionality with serialized objects inside columns. This
> way the column key becomes sort of analog of supercolumn key, and I handle
> the dictionaries I receive in the client.
>
> Does this sound OK?
>
> --
> View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Can-serialized-objects-in-columns-serve-as-ersatz-superCFs-tp6003775p6003775.html
> Sent from the cassandra-user@incubator.apache.org mailing list archive at
Nabble.com.

--90e6ba53ad74eb1447049bc871c6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<p>Yes, this works well for me. I have no SCFs but many columns contain JSO=
N.</p>
<p>Depending on your time/space/compatibility tradeoffs you can obviously p=
ick you own serialization method.</p>
<p>Best,<br>
Dave</p>
<div class=3D"gmail_quote">On Feb 8, 2011 4:33 AM, &quot;buddhasystem&quot;=
 &lt;<a href=3D"mailto:potekhin@bnl.gov">potekhin@bnl.gov</a>&gt; wrote:<br=
 type=3D"attribution">&gt; <br>&gt; Seeing that discussion here about index=
es not supported in superCFs, and less<br>
&gt; than clear future of superCFs altogether, I was thinking about getting=
 a<br>&gt; modicum of same functionality with serialized objects inside col=
umns. This<br>&gt; way the column key becomes sort of analog of supercolumn=
 key, and I handle<br>
&gt; the dictionaries I receive in the client.<br>&gt; <br>&gt; Does this s=
ound OK?<br>&gt; <br>&gt; -- <br>&gt; View this message in context: <a href=
=3D"http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Can-se=
rialized-objects-in-columns-serve-as-ersatz-superCFs-tp6003775p6003775.html=
">http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Can-seri=
alized-objects-in-columns-serve-as-ersatz-superCFs-tp6003775p6003775.html</=
a><br>
&gt; Sent from the <a href=3D"mailto:cassandra-user@incubator.apache.org">c=
assandra-user@incubator.apache.org</a> mailing list archive at Nabble.com.<=
br></div>

--90e6ba53ad74eb1447049bc871c6--