[ https://issues.apache.org/jira/browse/CASSANDRA-953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856039#action_12856039 ]
Gary Dusbabek commented on CASSANDRA-953: ----------------------------------------- I can't get this to apply on top of CASSANDRA-767. The last non-767 commit I have in my branch is: commit 8909b1722bec4ef4624a98f57bdd0b67b2e1c203 Author: jbellis <jbel...@13f79535-47bb-0310-9956-ffa450edef68> Date: Tue Apr 6 21:48:37 2010 +0000 add CFMetaData.hashCode. patch by Matthew Dennis; reviewed by Stu Hood for CASSANDRA-945 Do you or I need to rebase? :) > 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 > Assignee: Stu Hood > Fix For: 0.7 > > Attachments: > 0001-byte-for-decorateKey-and-getToken-in-IPartitioner.patch, > 0002-Convert-Thrift-to-byte-keys.patch, > 0003-Add-ByteOrderedPartitioner.patch, > 0004-Convert-to-hex-encoded-keys-in-sstable-import-export.patch > > > 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. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira