[
https://issues.apache.org/jira/browse/CASSANDRA-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841592#action_12841592
]
Stu Hood edited comment on CASSANDRA-767 at 3/4/10 11:11 PM:
-------------------------------------------------------------
> An alternative? Instead of AT defining a comparator, have it define a
> collation id generator
Works for me... it's similar to what we already do with BytesToken in COPP.
EDIT: Hmm, except we would still need to solve the padding problems within the
collation id.
EDIT2: Unless the collation id supports the compound key concept somehow by
having sections.
was (Author: stuhood):
> An alternative? Instead of AT defining a comparator, have it define a
collation id generator
Works for me... it's similar to what we already do with BytesToken in COPP.
EDIT: Hmm, except we would still need to solve the padding problems within the
collation id.
> 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
> Priority: Critical
> Fix For: 0.7
>
>
> 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.
