Details
-
Sub-task
-
Status: Resolved
-
Normal
-
Resolution: Fixed
-
None
-
None
Description
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.