[
https://issues.apache.org/jira/browse/CASSANDRA-953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12853407#action_12853407
]
Jonathan Ellis commented on CASSANDRA-953:
------------------------------------------
We've been telling people for a long time that 0.7 is going to break clients
for exactly this reason. So, go ahead and break them. :)
> Expose byte[] row keys in client APIs
> -------------------------------------
>
> Key: CASSANDRA-953
> URL: https://issues.apache.org/jira/browse/CASSANDRA-953
> Project: Cassandra
> Issue Type: Sub-task
> Reporter: Stu Hood
> Fix For: 0.7
>
>
> Once 767 lands, row keys will be stored as bytes internally, and the
> partitioner will decide whether to interpret the bytes. We can then expose
> the byte[] keys to client APIs.
> One key issue to settle is whether we should support both keys and bytes for
> the 0.7 release, or if we should make 0.7 a fully breaking release. The main
> problem with supporting both key types is that I don't think Thrift supports
> method overloading, so all of the methods would need to change names.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
