[
https://issues.apache.org/jira/browse/CASSANDRA-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12729708#action_12729708
]
Evan Weaver edited comment on CASSANDRA-139 at 7/10/09 9:40 AM:
----------------------------------------------------------------
No multiget from multiple column families for a single key?
For what it's worth I thought the previous way was more flexible, but I suppose
your point is that that may be bad at this point. I liked having the full path
excluding table as its own self-contained object though; I can see storing that
full predicate (?) as the id in a hydrated row, rather than storing the
predicate and key separately.
was (Author: eweaver):
No multiget from multiple column families for a single key?
For what it's worth I thought the previous way was more flexible (if we're
worried about forward compatibility). Not a big deal.
> 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
> Assignee: Jonathan Ellis
> Priority: Minor
> Attachments: 0001-thrift-changes.patch, 0001-thrift-changes.patch
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
