[
https://issues.apache.org/jira/browse/CASSANDRA-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-2622:
--------------------------------------
Attachment: 2622.txt
Right. But that implies that in the meantime * needs to include KEY or we break
semantics when we go from no-key to including-key.
Currently, the Python driver cheats and adds the row key at the beginning of
each column list whether it was asked for or not (obviously incorrect) and JDBC
forces you to unwrap the CassandraResultSet to get at it, which encourages
relying on implementation details that should really be private (and isn't very
user-friendly either:
http://twitter.com/#!/ampedandwired/status/66795646228762624).
It also means the two drivers we're shipping have different semantics which is
also broken.
As you can see from the patch (updated version attached) the actual changes to
QueryProcessor are small; the work of key-wrangling is done in
extractThriftColumns and the rest is just adjustments to pass the metadata
object there.
The patch is complete for QP and cql.py; I'm still working on the JDBC side.
Note that all the existing JDBC tests continue to pass (since there weren't
actually any wildcards tested there).
> Select * doesn't include row key
> --------------------------------
>
> Key: CASSANDRA-2622
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2622
> Project: Cassandra
> Issue Type: Bug
> Components: API
> Affects Versions: 0.8 beta 1
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Fix For: 0.8.0
>
> Attachments: 2622-in-progress.txt, 2622.txt
>
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
