[
https://issues.apache.org/jira/browse/CASSANDRA-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12728196#action_12728196
]
Jonathan Ellis commented on CASSANDRA-139:
------------------------------------------
you can't have optional parameters in thrift except in a struct. so we're
forced to use struct for some; for the rest it seems best to be consistent in
struct usage even though it's not necessary.
for multiget I would take the approach of the batch_ methods and have table +
key + list<cf> or list<cf, column>, etc.
(as I may have noted on the multiget issue, multiget is a superset of ordinary
get so it probably doesn't make sense to keep both around ultimately.)
> 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
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
