[
https://issues.apache.org/jira/browse/CASSANDRA-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841559#action_12841559
]
Stu Hood commented on CASSANDRA-767:
------------------------------------
Based on the difficulties encountered here, and never wanting to run into them,
I think we should allow AbstractTypes per ColumnFamily. This would allow us to
do fun stuff like compound keys for our views without throwing away type
information and needing to do nasty padding.
> 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.
