Return-Path: 
 <user-return-29663-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org>
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 74F86DB4F
	for <apmail-cassandra-user-archive@www.apache.org>;
 Mon, 22 Oct 2012 13:03:37 +0000 (UTC)
Received: (qmail 23200 invoked by uid 500); 22 Oct 2012 13:03:35 -0000
Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org
Received: (qmail 23069 invoked by uid 500); 22 Oct 2012 13:03:32 -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 23032 invoked by uid 99); 22 Oct 2012 13:03:31 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Oct 2012 13:03:31 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=5.0
	tests=RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of jbellis@gmail.com designates
 209.85.160.44 as permitted sender)
Received: from [209.85.160.44] (HELO mail-pb0-f44.google.com) (209.85.160.44)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Oct 2012 13:03:26 +0000
Received: by mail-pb0-f44.google.com with SMTP id ro8so1990375pbb.31
        for <multiple recipients>; Mon, 22 Oct 2012 06:03:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :cc:content-type;
        bh=390cijR702T0o8fpPtDlt45BhQTZZSHorJjtDKEXjlc=;
        b=FTP5o0r1Tvd3J0t1KqIlP+tde9veEOBA8X3BZm0mVuwq0ywKbGnMjbQNdJpBiO/GcT
         PCeHujjMuwaPrKlD6yR7eU4E7gzeVdGPFFoNXucB0GxQLoiiJzPymgDWDdxfPt32Up2/
         NxnFvak3UuzflZTTxlGW5/gmIJ2rX7gjwrJP8aZQvWAS+5nvVzP9RdMdFPA63Fv3juhN
         /2V5mctElWU2khJR/fxno5gkrarNYvPW3rO02CIa+lGmvQ66k/2ctlPkZc6vRbfo4tUf
         /yXagfgfXhF/fj2oPKnA4Z3Xq0TaUJZvv+KDEf3ytMf83hlrvuYh8It7EDWch1+o8jZm
         VVBg==
Received: by 10.68.143.162 with SMTP id sf2mr29476878pbb.137.1350910986131;
 Mon, 22 Oct 2012 06:03:06 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.66.40.147 with HTTP; Mon, 22 Oct 2012 06:02:45 -0700 (PDT)
In-Reply-To: <1350907069.47335.YahooMailNeo@web32508.mail.mud.yahoo.com>
References: 
 <CANJo1uC6gf2hOMfSTiJQL5Uy0WyJVn8gfmoAFPUcFSs+708jRw@mail.gmail.com>
 <007308B1-B49F-4206-871B-D220DDE7EDBB@thelastpickle.com>
 <CANJo1uDehdwnYzcBkq+xbOaoKYhVrFYy4Pu3cGmND6--=CLq8Q@mail.gmail.com>
 <3B25A86B-588D-4505-AB83-610615DA0ABE@thelastpickle.com>
 <CANJo1uD0aJVSyo4ojieUGookX8BxC48+Ztw681OTDJ8w6NTkvg@mail.gmail.com>
 <CANJo1uDa309U1A2NMVnXqwVBCrB7oD6U1+HXy6aaOEkm04WZug@mail.gmail.com>
 <1350907069.47335.YahooMailNeo@web32508.mail.mud.yahoo.com>
From: Jonathan Ellis <jbellis@gmail.com>
Date: Mon, 22 Oct 2012 08:02:45 -0500
Message-ID: 
 <CALdd-zi26JGZ5NgyCCw-rHZqsu6Q6zwa7E73NOXEEZ2bgx=MYg@mail.gmail.com>
Subject: Re: Fw: Fwd: Compound primary key: Insert after delete
To: dev@cassandra.apache.org, Vivek Mishra <vivek.mishra@yahoo.com>
Cc: user <user@cassandra.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Virus-Checked: Checked by ClamAV on apache.org

Mixing the two isn't really recommended because of just this kind of
difficulty, but if you must, I would develop against 1.2 since it will
actually validate that the CT encoding you've done manually is valid.
1.1 will just fail silently.

On Mon, Oct 22, 2012 at 6:57 AM, Vivek Mishra <vivek.mishra@yahoo.com> wrote:
> Hi,
>
> I am building support for Composite/Compund keys in Kundera and currently
> getting into number of problems for my POC to access it via Thrift.
>
> I am planning to use thrift API for insert/update/delete and for query i
> will go by CQL way.
>
>
> Issues:
> CompositeTypeRunner.java (see attached): Simple program to perform CRUD, it
> is not inserting against the deleted row key and also thrift API is
> returning column name as "Empty" string.
>
> OtherCompositeTypeRunner.java (see attached): Program to demonstrate issue
> with compound primary key as boolean. Column family creation via CQL is
> working fine, But insert via thrift is giving issue with "Unconfigured
> column family" though it is there!
>
> This is what i have tried with cassandra 1.1.6 as well.
>
> Please have a look and share, if i am doing anything wrong?   i did ask same
> on user group but no luck.
>
>
> -Vivek
>
>
>
>
> ----- Forwarded Message -----
> From: Vivek Mishra <mishra.vivs@gmail.com>
> To: vivek.mishra@yahoo.com
> Sent: Monday, October 22, 2012 5:17 PM
> Subject: Fwd: Compound primary key: Insert after delete
>
>
>
> ---------- Forwarded message ----------
> From: Vivek Mishra <mishra.vivs@gmail.com>
> Date: Mon, Oct 22, 2012 at 1:08 PM
> Subject: Re: Compound primary key: Insert after delete
> To: user@cassandra.apache.org
>
>
> Well. Last 2 lines of code are deleting 1 record and inserting 2 records,
> first one is "the deleted one" and  a new record. Output from command line:
>
> [default@unknown] use bigdata;
> Authenticated to keyspace: bigdata
> [default@bigdata] list test1;
> Using default limit of 100
> Using default column limit of 100
> -------------------
> RowKey: 2
> => (column=3:address, value=4, timestamp=1350884575938)
> -------------------
> RowKey: 1
>
> 2 Rows Returned.
>
>
> -Vivek
>
> On Mon, Oct 22, 2012 at 1:01 PM, aaron morton <aaron@thelastpickle.com>
> wrote:
>
> How is it not working ?
>
> Can you replicate the problem withe the CLI ?
> Cheers
>
> -----------------
> Aaron Morton
> Freelance Developer
> @aaronmorton
> http://www.thelastpickle.com
>
> On 22/10/2012, at 7:17 PM, Vivek Mishra <mishra.vivs@gmail.com> wrote:
>
> code attached. Somehow it is not working with 1.1.5.
>
> -Vivek
>
> On Mon, Oct 22, 2012 at 5:20 AM, aaron morton <aaron@thelastpickle.com>
> wrote:
>
> Yes AFAIK.
>
> Cheers
>
> -----------------
> Aaron Morton
> Freelance Developer
> @aaronmorton
> http://www.thelastpickle.com
>
> On 20/10/2012, at 12:15 AM, Vivek Mishra <mishra.vivs@gmail.com> wrote:
>
> Hi,
> Is it possible to reuse same compound primary key after delete? I guess it
> works fine for non composite keys.
>
> -Vivek
>
>
>
> <CompositeTypeRunner.java>
>
>
>
>
>
>



-- 
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com