[
https://issues.apache.org/jira/browse/CASSANDRA-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848082#action_12848082
]
Sylvain Lebresne commented on CASSANDRA-767:
--------------------------------------------
That may well be a question a bit ahead of time, and that may not be the right
place to ask that, so sorry in advance.
But do you have any idea of how the upgrade path will work when this come out.
Do you believe such upgrade will be doable on a live cluster ? Cause I'm not
sure
I see how that can pulled off.
Typically, I have to store UUID as row key. Right now I have to encode that in
a string somehow. Ideally, I would like for them to be stored as 16 bytes when
this patch come out. Not sure how that can be done without a full cluster
restart tough (which may not be possible at the time).
Any idea if I can plan something right now (while I'm still in development)
to make it easier then ?
> 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.
