cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-767) Row keys should be byte[]s, not Strings
Date Thu, 04 Mar 2010 22:19:27 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841565#action_12841565
] 

Jonathan Ellis commented on CASSANDRA-767:
------------------------------------------

then you get back to needing partitioner+token per CF.  that's totally outside the scope for
0.7 and probably 0.8.

An alternative?  Instead of AT defining a comparator, have it define a collation id generator,
where it generates a byte[] that gives it "the right sort" when done lexicographically.  then
you could make that part of key decoration and it Just Works.

> 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.


Mime
View raw message