[ 
https://issues.apache.org/jira/browse/CASSANDRA-6807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13922777#comment-13922777
 ] 

Peter commented on CASSANDRA-6807:
----------------------------------

In the interest of helping other people that work on drivers. I will add 
javadocs and comments to ResultSet class and submit a patch over the weekend. 
Once I have the patch, I will close the issue.

To get the KEY over thrift, driver implementors need to find the KEY column to 
extract the value. In the case of hector, I find the index for the KEY column 
once and reuse it for all subsequent rows to avoid iterating over the columns 
again. Every query will find the index for the Key column once, since users 
might not always put the KEY column at the front of the select statement.

> Thrift with CQL3 doesn't return key
> -----------------------------------
>
>                 Key: CASSANDRA-6807
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6807
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>         Environment: windows 7 64bit, jdk 1.7, cassandra 2.0.5
>            Reporter: Peter
>         Attachments: thrift-missing-key.png
>
>
> I'm working on adding support for CQL3 to Hector and came across an odd 
> issue. I explicitly include the key in the statement, but the key isn't 
> returned. I've attached a screenshot. Hector's CqlQuery class is doing the 
> following to issue the cql3 call. I'm hoping it's a simple configuration 
> detail I'm missing or parameter I need to set.
> result = cassandra.execute_cql3_query(query, useCompression ? 
> Compression.GZIP : Compression.NONE, getConsistency());
> Looking at org.apache.cassandra.thrift.Cassandra.Client, I don't see anything 
> obvious that would tell me how to tell Cassandra to return the key in the 
> CqlResult or CqlRow. The queries I tried look like this
> select key from myColFamily;



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to