[
https://issues.apache.org/jira/browse/CASSANDRA-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720993#action_12720993
]
Sandeep Tata commented on CASSANDRA-232:
----------------------------------------
Since we're not using vector clocks like Dynamo, a quorum read is essentially a
"read latest". Right?
I'm concerned that the *only* resolution policy here when things are not
consistent is "latest timestamp wins". This is fine if the only use case is for
an inverted index like the FB guys. You can't build a shopping cart application.
> 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
> Affects Versions: 0.3, 0.4
> Environment: all
> Reporter: Sandeep Tata
> Fix For: 0.4
>
>
> 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.
