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

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

Just to make sure I don't mis-interpret again. The impression I got from 
Jonathan's response is that CqlRow.key is always null and was a "special case" 
in the past. In other words it is deprecated going forward.

The change with CQL3 is that KEY is just another column, so thrift does get the 
column. I can live with that and will give it a try. Reading the source code, 
it wasn't at all obvious, which is why I asked. I will add a comment and 
javadoc to ResultSet and submit a patch. Atleast that way, if anyone else 
writing drivers looks they can see the explanation and ask the same question 
again.

thanks for taking time to clarify.

> 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