If you want the "row key", just query it (we prefer the term "partition
key" in CQL3 and that's the term you'll find in documents like
http://cassandra.apache.org/doc/cql3/CQL.html but it's the same thing) and
it'll be part of the return columns.
I understand that, as i am able to fetch "partition
>
> How to fetch and populate "row key" from CqlRow api then?
If you want the "row key", just query it (we prefer the term "partition
key" in CQL3 and that's the term you'll find in documents like
http://cassandra.apache.org/doc/cql3/CQL.html but it's the same thing) and
it'll be part of the re
Is it documented somewhere? How to fetch and populate "row key" from
CqlRow api then?
-Vivek
On Mon, Jan 14, 2013 at 7:18 PM, Sylvain Lebresne wrote:
> On Mon, Jan 14, 2013 at 12:48 PM, Vivek Mishra wrote:
>
>> I am getting an issue, where "key" attribute's in byte[] is returned as
>> empty va
On Mon, Jan 14, 2013 at 12:48 PM, Vivek Mishra wrote:
> I am getting an issue, where "key" attribute's in byte[] is returned as
> empty value.
>
We don't return this anymore as this doesn't make much sense for CQL3. Same
as in CqlMetadata we don't return a default_name_type and
default_value_type
Hi,
I am trying to migrate Kundera Thrift API from 1.1.6 from 1.2 and changing *
execute_cql_query* to* execute_cql3_query*(with consistenceLevel). I am
getting an issue, where "key" attribute's in byte[] is returned as empty
value.
Though same is working with 1.1.6
-Vivek
On Mon, Jan 14, 2013
On Sun, Jan 13, 2013 at 5:59 PM, Shahryar Sedghi wrote:
> Since new cql3 methods require ConsistencyLevel.xxx, is consistency level
> at the query has precedence over this level at the api or not.
>
There is no "consistency level at the query level" anymore. That's one of
the breaking change (no
I finally realized that Thrift API has changed from 1.1 to 1.2 and my code
and modified JDBC driver works well except I get an exception on the system
log when I close the connection. Looks like it is an old issue reappearing.
I have evaluated new Java driver, it is easier and more practical than
Thanks Brian
it is not the same issue, and stack trace is different. It is a simple test
case and I have 3 columns and I populate all of them with:
cqlsh:somedb> CREATE TABLE test(interval int,id text, body text, primary
key (interval, id));
cqlsh:somedb> insert into test (interval, id, body) val
I reported the issue here. You may be missing a component in your column name.
https://issues.apache.org/jira/browse/CASSANDRA-5138
-brian
On Jan 12, 2013, at 12:48 PM, Shahryar Sedghi wrote:
> Hi
>
> I am trying to test my application that runs with JDBC, CQL 3 with Cassandra
> 1.2. After
Hi
I am trying to test my application that runs with JDBC, CQL 3 with
Cassandra 1.2. After getting many weird errors and downgrading from JDBC to
thrift, I realized the thrift on Cassandra 1.2 has issues with wide rows.
If I define the table as:
CREATE TABLE test(interval int,id text, body text,
10 matches
Mail list logo
