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 key" and "clustering
key" for composite Key. Wondering even if it is a partition key, shouldn't
it be returned in form of "key" rather than as part of returned columns?
Bit confusing, as definition of column in cassandra is {column_name,
column_value, timestamp}. Is it true for partition key as well?
-Vivek
On Mon, Jan 14, 2013 at 7:43 PM, Sylvain Lebresne <sylv...@datastax.com>wrote:
> 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 return columns.
>
> --
> Sylvain
>
>
>>
>> -Vivek
>>
>>
>> On Mon, Jan 14, 2013 at 7:18 PM, Sylvain Lebresne
>> <sylv...@datastax.com>wrote:
>>
>>> On Mon, Jan 14, 2013 at 12:48 PM, Vivek Mishra <mishra.v...@gmail.com>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 as they don't make any sense anymore either (they still
>>> exist in the thrift struct for compatibility sake, CQL2 still uses them,
>>> and we figured it was not worth duplicating thing by creating a specific
>>> Cql3Result struct).
>>>
>>> --
>>> Sylvain
>>>
>>>
>>>> Though same is working with 1.1.6
>>>>
>>>> -Vivek
>>>>
>>>>
>>>>
>>>> On Mon, Jan 14, 2013 at 4:34 PM, Sylvain Lebresne <sylv...@datastax.com
>>>> > wrote:
>>>>
>>>>> methods
>>>>
>>>>
>>>>
>>>>
>>>
>>
>
