[
https://issues.apache.org/jira/browse/CASSANDRA-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12728191#action_12728191
]
Evan Weaver edited comment on CASSANDRA-139 at 7/7/09 9:54 AM:
---------------------------------------------------------------
Looks reasonable!
Once we get multiget we will have the same situation for keys, so i like the
struct solution. Internal layer is agnostic but consistent, and clients can go
nuts. A standard may eventually emerge.
Is a struct the same as named parameters in Thrift or are there other benefits
to reifying the param list?
was (Author: eweaver):
Looks reasonable.
Once we get multiget we will have the same situation for keys, so i like the
struct solution. Internal layer is agnostic but consistent, and clients can go
nuts. A standard may eventually emerge.
> 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.
