cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Evan Weaver (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-139) thrift API should use lists instead of colon-delimited strings to specify column path
Date Mon, 06 Jul 2009 18:05:14 GMT

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

Evan Weaver commented on CASSANDRA-139:
---------------------------------------

The switch won't be silent, because we will drop the magic colons at the same time. Anyway,
now is the time to break things.

Re. routing order:

What we care about here is what knowledge the client can act on. 
 * It's important to know that a CF is a single a file with keys inside it, because that's
what lets you control column-major vs. row-major storage order. 
 * It is not important to know that a single key has all its column families on the same host.

Hbase and Hypertable use routing order, but they also use the colons, so I don't they are
trustworthy API design models.

In the interests of not needlessly confusing the majority of developers who are familiar with
SQL but not BigTable, I think we should switch it.

> thrift API should use lists instead of colon-delimited strings to specify column path
> -------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-139
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-139
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jonathan Ellis
>            Priority: Minor
>


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