[
https://issues.apache.org/jira/browse/CASSANDRA-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12727410#action_12727410
]
Evan Weaver edited comment on CASSANDRA-139 at 7/6/09 12:16 AM:
----------------------------------------------------------------
OK, the old style API came from the BigTable paper. HBase uses it too:
Cell cell = table.get("myRow", "myColumnFamily:columnQualifier1");
This is bad for three reasons:
1. Concatenating strings; are you serious?
2. It is targeted for a specific use case where your table contains just one
kind of business object.
3. It doesn't represent actual storage order, so it's super confusing.
I think all APIs should take parameters in storage order in all cases. That is:
keyspace.get(column_family, key, [supercolumn], column)
was (Author: eweaver):
The old style API came from the BigTable pape. HBase uses it too:
Cell cell = table.get("myRow", "myColumnFamily:columnQualifier1");
This is bad for three reasons:
1. Concatenating strings; are you serious?
2. It is targeted for a specific use case where your table contains just one
kind of business object.
3. It doesn't represent actual storage order, so it's super confusing.
I think all APIs should take parameters in storage order in all cases. That is:
keyspace.get(column_family, key, [supercolumn], column)
> 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.
