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 9766CDC6D for ; Mon, 27 Aug 2012 04:29:00 +0000 (UTC) Received: (qmail 70141 invoked by uid 500); 27 Aug 2012 04:28:58 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 69469 invoked by uid 500); 27 Aug 2012 04:28:50 -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 69425 invoked by uid 99); 27 Aug 2012 04:28:48 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Aug 2012 04:28:48 +0000 X-ASF-Spam-Status: No, hits=1.8 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,FSL_RCVD_USER,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of amithanda01@gmail.com designates 209.85.212.44 as permitted sender) Received: from [209.85.212.44] (HELO mail-vb0-f44.google.com) (209.85.212.44) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Aug 2012 04:28:42 +0000 Received: by vbbez10 with SMTP id ez10so4386705vbb.31 for ; Sun, 26 Aug 2012 21:28:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=sWmyX+f5Y21YvdPzfILeVBv/I2mEpJgENqy6db/bw70=; b=azLGRBFlqMRYjpOPawT5u4a/5jMDDmINJc/9nxU1I9UMs3ukI/etqD/z9NS2C0BSuZ Gpv/ZtEDN7t8TYvx0UeJMM6M9Ygerd8jxVT8HpSClWVMnDezQYORBo3OQr5EyY1MMcwo sgmPdrxBnPqHgGOrY+hkj+xz16HAb4yJfIp+03Wc2Wz5HMf//EctQlYPee2BZ6ev5KWR P3bKssUUE200CgjuK0JsHFkOxfz8LCgapV4he0afwF3WrWzMwDv/NwyLMXhsE/ca9e70 oCkDmW5eqZdLXJD6txyl7R0NLTZsXAY3M8GTnuknObu6+E79q25yRdE+0s/U4rzdcFIA pLiQ== MIME-Version: 1.0 Received: by 10.52.69.174 with SMTP id f14mr3856362vdu.17.1346041701210; Sun, 26 Aug 2012 21:28:21 -0700 (PDT) Received: by 10.58.68.106 with HTTP; Sun, 26 Aug 2012 21:28:21 -0700 (PDT) In-Reply-To: References: Date: Mon, 27 Aug 2012 09:58:21 +0530 Message-ID: Subject: Re: help required to resolve super column family problems From: Amit Handa To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=20cf307f31fc741b1d04c837c194 --20cf307f31fc741b1d04c837c194 Content-Type: text/plain; charset=ISO-8859-1 Hi, i basically want to do hands-on on Super Column family concept, making some examples using hector api, and manually adding the data. I explored hector-example project, but only got very starting level of super column family example. i am in search of more super column family examples using hector api. can i get some link and references related to it? Regards, Amit On Sat, Aug 25, 2012 at 3:20 AM, Mohit Anchlia wrote: > If you are starting out new use composite column names/values or you could > also use JSON style doc as a column value. > > > On Fri, Aug 24, 2012 at 2:31 PM, Rob Coli wrote: > >> On Fri, Aug 24, 2012 at 4:33 AM, Amit Handa >> wrote: >> > kindly help in resolving the following problem with respect to super >> column >> > family. >> > i am using cassandra version 1.1.3 >> >> Well, THERE's your problem... ;D >> >> But seriously.. as I understand project intent, super columns will >> ultimately be a weird API wrapper around composite keys. Also, super >> column families have not been well supported for years. You probably >> just want to use composite keys if you are just starting out in 1.1.x. >> >> https://issues.apache.org/jira/browse/CASSANDRA-3237 >> >> =Rob >> >> -- >> =Robert Coli >> AIM>ALK - rcoli@palominodb.com >> YAHOO - rcoli.palominob >> SKYPE - rcoli_palominodb >> > > --20cf307f31fc741b1d04c837c194 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

i basically want to do hands-on on Super Column fami= ly concept, making some examples using hector api, and manually adding the = data.=A0
I explored hector-example project, but only got very sta= rting level of super column family example.
i am in search of more super column family examples using hector api. = can i get some link and references related to it?

=
Regards,
Amit


On Sat, Aug 25, 2012 at 3:20 AM, Mohit Anchlia <mohitanchlia@gmail.co= m> wrote:
If you are starting out new use composite column names/values or you could = also use JSON style doc as a column value.


On Fri, Aug 24, 2012 at 2:31 PM, Rob Coli <r= coli@palominodb.com> wrote:
On Fri, Aug 24, 2012 at 4:33 AM, Amit= Handa <amith= anda01@gmail.com> wrote:
> kindly help in resolving the following problem with respect to super c= olumn
> family.
> i am using cassandra version 1.1.3

Wel= l, THERE's your problem... ;D

But seriously.. as I understand pr= oject intent, super columns will
ultimately be a weird API wrapper around composite keys. Also, =A0super
= column families have not been well supported for years. You probably
jus= t want to use composite keys if you are just starting out in 1.1.x.

https://issues.apache.org/jira/browse/CASSANDRA-3237
<= font color=3D"#888888">
=3DRob

--
=3DRobert Coli
AIM&GT= ALK - rcoli@palom= inodb.com
YAHOO - rcoli.palominob
SKYPE - rcoli_palominodb


--20cf307f31fc741b1d04c837c194--