cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gasol Wu (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CASSANDRA-232) Interface does not allow specification of weak vs quorum reads
Date Tue, 28 Jul 2009 08:33:14 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gasol Wu updated CASSANDRA-232:
-------------------------------

    Attachment: change-correct-parameter-CASSANDRA-232.patch

old copy always pass ConsistencyLevel.ONE to StorageProxy.readProtocol.
this patch work for me.

> 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, change-correct-parameter-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.


Mime
View raw message