[ https://issues.apache.org/jira/browse/CASSANDRA-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stu Hood updated CASSANDRA-767: ------------------------------- Attachment: 0003-Store-bytes-in-DecoratedKey-and-cleanup-dead-code.patch 0002-Implement-a-legacy-sstable-test.patch 0001-Implement-compaction-benchmark.patch > Row keys should be byte[]s, not Strings > --------------------------------------- > > Key: CASSANDRA-767 > URL: https://issues.apache.org/jira/browse/CASSANDRA-767 > Project: Cassandra > Issue Type: Improvement > Reporter: Stu Hood > Assignee: Stu Hood > Priority: Critical > Fix For: 0.7 > > Attachments: 0001-Implement-compaction-benchmark.patch, > 0002-Implement-a-legacy-sstable-test.patch, > 0003-Store-bytes-in-DecoratedKey-and-cleanup-dead-code.patch > > > This issue has come up numerous times, and we've dealt with a lot of pain > because of it: let's get it knocked out. > Keys being Java Strings can make it painful to use Cassandra from other > languages, encoding binary data like integers as Strings is very inefficient, > and there is a disconnect between our column data types and the plain String > treatment we give row keys. > The key design decision that needs discussion is: Should we apply the column > AbstractTypes to row keys? If so, how do Partitioners change? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.