You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Chris Burroughs (JIRA)" <ji...@apache.org> on 2011/02/09 19:29:57 UTC
[jira] Created: (CASSANDRA-2146) cli read_repair_chance input not
validated
cli read_repair_chance input not validated
------------------------------------------
Key: CASSANDRA-2146
URL: https://issues.apache.org/jira/browse/CASSANDRA-2146
Project: Cassandra
Issue Type: Bug
Components: Core
Affects Versions: 0.7.1
Reporter: Chris Burroughs
Priority: Minor
{noformat}
put(ColumnFamilyArgument.READ_REPAIR_CHANCE, "Probability (0.0-1.0) with which to perform read repairs on CL.ONE reads");
{noformat}
The input range is not enforced so
{noformat}
create column family ... with ... read_repair_chance = 25;
{noformat}
Will result in
{noformat}
Keyspace: ks1:
Replication Strategy: org.apache.cassandra.locator.SimpleStrategy
Replication Factor: 3
Column Families:
ColumnFamily: cf1
Columns sorted by: org.apache.cassandra.db.marshal.UTF8Type
...
Read repair chance: 25.0
{noformat}
I am unsure if in practice this means RR chance 100%, or something surprising. (I ran into this because read_repair_chance requires a leading 0 and ommiting it results in an unhelpful "Command not found:" message).
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CASSANDRA-2146) cli read_repair_chance input not
validated
Posted by "Pavel Yaskevich (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Yaskevich updated CASSANDRA-2146:
---------------------------------------
Attachment: CASSANDRA-2146.patch
> cli read_repair_chance input not validated
> ------------------------------------------
>
> Key: CASSANDRA-2146
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2146
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7.0
> Reporter: Chris Burroughs
> Assignee: Pavel Yaskevich
> Priority: Minor
> Fix For: 0.7.2
>
> Attachments: CASSANDRA-2146.patch
>
>
> {noformat}
> put(ColumnFamilyArgument.READ_REPAIR_CHANCE, "Probability (0.0-1.0) with which to perform read repairs on CL.ONE reads");
> {noformat}
> The input range is not enforced so
> {noformat}
> create column family ... with ... read_repair_chance = 25;
> {noformat}
> Will result in
> {noformat}
> Keyspace: ks1:
> Replication Strategy: org.apache.cassandra.locator.SimpleStrategy
> Replication Factor: 3
> Column Families:
> ColumnFamily: cf1
> Columns sorted by: org.apache.cassandra.db.marshal.UTF8Type
> ...
> Read repair chance: 25.0
> {noformat}
> I am unsure if in practice this means RR chance 100%, or something surprising. (I ran into this because read_repair_chance requires a leading 0 and ommiting it results in an unhelpful "Command not found:" message).
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CASSANDRA-2146) cli read_repair_chance input not
validated
Posted by "Pavel Yaskevich (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Yaskevich updated CASSANDRA-2146:
---------------------------------------
Remaining Estimate: 0.5h
Original Estimate: 0.5h
> cli read_repair_chance input not validated
> ------------------------------------------
>
> Key: CASSANDRA-2146
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2146
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7.0
> Reporter: Chris Burroughs
> Assignee: Pavel Yaskevich
> Priority: Minor
> Fix For: 0.7.2
>
> Attachments: CASSANDRA-2146.patch
>
> Original Estimate: 0.5h
> Remaining Estimate: 0.5h
>
> {noformat}
> put(ColumnFamilyArgument.READ_REPAIR_CHANCE, "Probability (0.0-1.0) with which to perform read repairs on CL.ONE reads");
> {noformat}
> The input range is not enforced so
> {noformat}
> create column family ... with ... read_repair_chance = 25;
> {noformat}
> Will result in
> {noformat}
> Keyspace: ks1:
> Replication Strategy: org.apache.cassandra.locator.SimpleStrategy
> Replication Factor: 3
> Column Families:
> ColumnFamily: cf1
> Columns sorted by: org.apache.cassandra.db.marshal.UTF8Type
> ...
> Read repair chance: 25.0
> {noformat}
> I am unsure if in practice this means RR chance 100%, or something surprising. (I ran into this because read_repair_chance requires a leading 0 and ommiting it results in an unhelpful "Command not found:" message).
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CASSANDRA-2146) cli read_repair_chance input not
validated
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993240#comment-12993240 ]
Hudson commented on CASSANDRA-2146:
-----------------------------------
Integrated in Cassandra-0.7 #276 (See [https://hudson.apache.org/hudson/job/Cassandra-0.7/276/])
validate read_repair_chance
patch by xedin; reviewed by jbellis for CASSANDRA-2146
> cli read_repair_chance input not validated
> ------------------------------------------
>
> Key: CASSANDRA-2146
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2146
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7.0
> Reporter: Chris Burroughs
> Assignee: Pavel Yaskevich
> Priority: Minor
> Fix For: 0.7.2
>
> Attachments: CASSANDRA-2146.patch
>
> Original Estimate: 0.5h
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {noformat}
> put(ColumnFamilyArgument.READ_REPAIR_CHANCE, "Probability (0.0-1.0) with which to perform read repairs on CL.ONE reads");
> {noformat}
> The input range is not enforced so
> {noformat}
> create column family ... with ... read_repair_chance = 25;
> {noformat}
> Will result in
> {noformat}
> Keyspace: ks1:
> Replication Strategy: org.apache.cassandra.locator.SimpleStrategy
> Replication Factor: 3
> Column Families:
> ColumnFamily: cf1
> Columns sorted by: org.apache.cassandra.db.marshal.UTF8Type
> ...
> Read repair chance: 25.0
> {noformat}
> I am unsure if in practice this means RR chance 100%, or something surprising. (I ran into this because read_repair_chance requires a leading 0 and ommiting it results in an unhelpful "Command not found:" message).
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CASSANDRA-2146) cli read_repair_chance input not
validated
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-2146:
--------------------------------------
Affects Version/s: (was: 0.7.1)
0.7.0
Fix Version/s: 0.7.2
Assignee: Pavel Yaskevich
> cli read_repair_chance input not validated
> ------------------------------------------
>
> Key: CASSANDRA-2146
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2146
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7.0
> Reporter: Chris Burroughs
> Assignee: Pavel Yaskevich
> Priority: Minor
> Fix For: 0.7.2
>
>
> {noformat}
> put(ColumnFamilyArgument.READ_REPAIR_CHANCE, "Probability (0.0-1.0) with which to perform read repairs on CL.ONE reads");
> {noformat}
> The input range is not enforced so
> {noformat}
> create column family ... with ... read_repair_chance = 25;
> {noformat}
> Will result in
> {noformat}
> Keyspace: ks1:
> Replication Strategy: org.apache.cassandra.locator.SimpleStrategy
> Replication Factor: 3
> Column Families:
> ColumnFamily: cf1
> Columns sorted by: org.apache.cassandra.db.marshal.UTF8Type
> ...
> Read repair chance: 25.0
> {noformat}
> I am unsure if in practice this means RR chance 100%, or something surprising. (I ran into this because read_repair_chance requires a leading 0 and ommiting it results in an unhelpful "Command not found:" message).
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira