You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sandeep Tata (JIRA)" <ji...@apache.org> on 2009/06/16 07:51:07 UTC
[jira] Created: (CASSANDRA-232) Interface does not allow
specification of weak vs quorum reads
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.
[jira] Updated: (CASSANDRA-232) Interface does not allow
specification of weak vs quorum reads
Posted by "Gasol Wu (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (CASSANDRA-232) Interface does not allow
specification of weak vs quorum reads
Posted by "Sammy Yu (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (CASSANDRA-232) Interface does not allow
specification of weak vs quorum reads
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736055#action_12736055 ]
Jonathan Ellis commented on CASSANDRA-232:
------------------------------------------
committed, thanks!
> 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.
[jira] Commented: (CASSANDRA-232) Interface does not allow
specification of weak vs quorum reads
Posted by "Sammy Yu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736101#action_12736101 ]
Sammy Yu commented on CASSANDRA-232:
------------------------------------
oops thanks for catching this!
> 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.
[jira] Commented: (CASSANDRA-232) Interface does not allow
specification of weak vs quorum reads
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12721030#action_12721030 ]
Jonathan Ellis commented on CASSANDRA-232:
------------------------------------------
That's the design. It's adequate for many applications. Let's solidify that before getting more ambitious.
> 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.
[jira] Assigned: (CASSANDRA-232) Interface does not allow
specification of weak vs quorum reads
Posted by "Sammy Yu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sammy Yu reassigned CASSANDRA-232:
----------------------------------
Assignee: Sammy Yu
> 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
>
>
> 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.
[jira] Commented: (CASSANDRA-232) Interface does not allow
specification of weak vs quorum reads
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733610#action_12733610 ]
Jonathan Ellis commented on CASSANDRA-232:
------------------------------------------
see also CASSANDRA-300
> 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
> 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.
[jira] Commented: (CASSANDRA-232) Interface does not allow
specification of weak vs quorum reads
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720091#action_12720091 ]
Jonathan Ellis commented on CASSANDRA-232:
------------------------------------------
+1
for symmetry, adding block_for (minimum of 1) seems ok, unless someone has a better suggestion.
> 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.
[jira] Commented: (CASSANDRA-232) Interface does not allow
specification of weak vs quorum reads
Posted by "Eric Evans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720164#action_12720164 ]
Eric Evans commented on CASSANDRA-232:
--------------------------------------
+1 for adding a block_for to be consistent with inserts
> 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.
[jira] Commented: (CASSANDRA-232) Interface does not allow
specification of weak vs quorum reads
Posted by "Sandeep Tata (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (CASSANDRA-232) Interface does not allow
specification of weak vs quorum reads
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736063#action_12736063 ]
Hudson commented on CASSANDRA-232:
----------------------------------
Integrated in Cassandra #151 (See [http://hudson.zones.apache.org/hudson/job/Cassandra/151/])
pass consistency_level param from thrift to internals. patch by Gasol Wu; reviewed by jbellis for
add ConsistencyLevel parameter to read ops. patch by Sammy Yu; reviewed by jbellis for
> 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.