[
https://issues.apache.org/jira/browse/CASSANDRA-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sammy Yu updated CASSANDRA-232:
-------------------------------
Attachment: 0001-Work-for-cassandra-232.patch
Added consistency_level parameter for the following thrift calls:
get_column, get_column_count, get_slice_super_by_names, get_slice_super,
get_super_column, get_slice, get_slice_by_names
> Interface does not allow specification of weak vs quorum reads
> --------------------------------------------------------------
>
> Key: CASSANDRA-232
> URL: https://issues.apache.org/jira/browse/CASSANDRA-232
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Affects Versions: 0.3, 0.4
> Environment: all
> Reporter: Sandeep Tata
> Assignee: Sammy Yu
> Fix For: 0.4
>
> Attachments: 0001-Work-for-cassandra-232.patch
>
>
> Today. read calls in the API, eg. get_column don't let you specify if you
> want a weak read or a quorum read.
> Reads seem to default always to weak reads. A way for apps to request quorum
> reads would be nice.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
