Fw: Fwd: Compound primary key: Insert after delete
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
To: vivek.mis...@yahoo.com
Sent: Monday, October 22, 2012 5:17 PM
Subject: Fwd: Compound primary key: Insert after delete
-- Forwarded message --
From: Vivek Mishra
Date: Mon, Oct 22, 2012 at 1:08 PM
Subject: Re: Compound primary key: Insert after delete
To: u...@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 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 wrote:
>
>code attached. Somehow it is not working with 1.1.5.
>>
>>
>>-Vivek
>>
>>
>>On Mon, Oct 22, 2012 at 5:20 AM, aaron morton wrote:
>>
>>Yes AFAIK.
>>>
>>>
>>>Cheers
>>>
>>>
>>>-
>>>Aaron Morton
>>>Freelance Developer
>>>@aaronmorton
>>>http://www.thelastpickle.com
>>>
>>>
>>>On 20/10/2012, at 12:15 AM, Vivek Mishra wrote:
>>>
>>>Hi,
Is it possible to reuse same compound primary key after delete? I guess it
works fine for non composite keys.
-Vivek
>>>
>>
>/***
* * Copyright 2012 Impetus Infotech.
* *
* * Licensed under the Apache License, Version 2.0 (the "License");
* * you may not use this file except in compliance with the License.
* * You may obtain a copy of the License at
* *
* * http://www.apache.org/licenses/LICENSE-2.0
* *
* * Unless required by applicable law or agreed to in writing, software
* * distributed under the License is distributed on an "AS IS" BASIS,
* * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* * See the License for the specific language governing permissions and
* * limitations under the License.
**/
package com.impetus.client.cassandra.thrift;
import java.nio.ByteBuffer;
import java.util.ArrayList;
import java.util.Iterator;
import java.util.LinkedHashMap;
import java.util.List;
import org.apache.cassandra.db.marshal.AbstractType;
import org.apache.cassandra.db.marshal.CompositeType;
import org.apache.cassandra.db.marshal.CompositeType.Builder;
import org.apache.cassandra.db.marshal.UTF8Type;
import org.apache.cassandra.locator.SimpleStrategy;
import org.apache.cassandra.thrift.Cassandra;
import org.apache.cassandra.thrift.CfDef;
import org.apache.cassandra.thrift.Column;
import org.apache.cassandra.thrift.ColumnOrSuperColumn;
import org.apache.cassandra.thrift.ColumnParent;
import org.apache.cassandra.thrift.ColumnPath;
import org.apache.cassandra.thrift.Compression;
import org.apache.cassandra.thrift.ConsistencyLevel;
import org.apache.cassandra.thrift.CqlResult;
import org.apache.cassandra.thrift.CqlRow;
import org.apache.cassandra.thrift.KsDef;
import org.apache.cassandra.thrift.SlicePredicate;
import org.apache.cassandra.thrift.SliceRange;
import org.apache.cassandra.thrift.TBinaryProtocol;
import org.apache.thrift.transport.TFramedTransport;
import org.apache.thrift.transport.TSocket;
import org.scale7.cassandra.pelops.Bytes;
/**
* @author vivek.mishra
*
*/
public class CompositeTypeRunner
{
public static void main(String[] args) throws Exception {
TSocket socket = new TSocket("localhost", 9160);
TFramedTransport transport = new TFramedTransport(socket);
Cassandra.Client client = new Cassandra.Client(new
TBinaryProtocol(transport));
transport.open();
client.set_cql_version("3.0.0");
List cfDefs = new Ar
Re: Fw: Fwd: Compound primary key: Insert after delete
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 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 > To: vivek.mis...@yahoo.com > Sent: Monday, October 22, 2012 5:17 PM > Subject: Fwd: Compound primary key: Insert after delete > > > > -- Forwarded message -- > From: Vivek Mishra > Date: Mon, Oct 22, 2012 at 1:08 PM > Subject: Re: Compound primary key: Insert after delete > To: u...@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 > 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 wrote: > > code attached. Somehow it is not working with 1.1.5. > > -Vivek > > On Mon, Oct 22, 2012 at 5:20 AM, aaron morton > wrote: > > Yes AFAIK. > > Cheers > > - > Aaron Morton > Freelance Developer > @aaronmorton > http://www.thelastpickle.com > > On 20/10/2012, at 12:15 AM, Vivek Mishra wrote: > > Hi, > Is it possible to reuse same compound primary key after delete? I guess it > works fine for non composite keys. > > -Vivek > > > > > > > > > > -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of DataStax, the source for professional Cassandra support http://www.datastax.com
Re: Fw: Fwd: Compound primary key: Insert after delete
Thanks. But it means i may have re-write all the stuff in CQL way. Considering CQL as a future interface for cassandra interface,AFN i will implement it without mixing them. -Vivek On Mon, Oct 22, 2012 at 6:32 PM, Jonathan Ellis wrote: > 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 > 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 > > To: vivek.mis...@yahoo.com > > Sent: Monday, October 22, 2012 5:17 PM > > Subject: Fwd: Compound primary key: Insert after delete > > > > > > > > -- Forwarded message -- > > From: Vivek Mishra > > Date: Mon, Oct 22, 2012 at 1:08 PM > > Subject: Re: Compound primary key: Insert after delete > > To: u...@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 > > 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 wrote: > > > > code attached. Somehow it is not working with 1.1.5. > > > > -Vivek > > > > On Mon, Oct 22, 2012 at 5:20 AM, aaron morton > > wrote: > > > > Yes AFAIK. > > > > Cheers > > > > - > > Aaron Morton > > Freelance Developer > > @aaronmorton > > http://www.thelastpickle.com > > > > On 20/10/2012, at 12:15 AM, Vivek Mishra wrote: > > > > Hi, > > Is it possible to reuse same compound primary key after delete? I guess > it > > works fine for non composite keys. > > > > -Vivek > > > > > > > > > > > > > > > > > > > > > > > > -- > Jonathan Ellis > Project Chair, Apache Cassandra > co-founder of DataStax, the source for professional Cassandra support > http://www.datastax.com >
