cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-767) Row keys should be byte[]s, not Strings
Date Mon, 22 Mar 2010 14:01:27 GMT


Sylvain Lebresne commented on CASSANDRA-767:

> In version 0.7, all row keys (which are currently strings encoded as UTF-8, will be returned
as raw 
> UTF-8 bytes: Cassandra does not have any idea what you might have encoded in the string.

Yep, I think I was hoping for some upgrade path that you could customize to repack the keys
bytes correctly (by means of a custom java class for instance). But I realized that there
is no way 
that could be done without converting all the data of the cluster at once, which is unrealistic.
I was 
just stupid. Sorry.

> Row keys should be byte[]s, not Strings
> ---------------------------------------
>                 Key: CASSANDRA-767
>                 URL:
>             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.

View raw message