[jira] [Updated] (CASSANDRA-19503) (Accord) Cassandra bootstrap no longer using the range txn and instead uses the sync point empty txn for reads
[ https://issues.apache.org/jira/browse/CASSANDRA-19503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-19503: -- Fix Version/s: 5.1 (was: 5.x) Since Version: NA Source Control Link: https://github.com/apache/cassandra/commit/63f39562ec2f1da182034c24eeb1e7bef29749ec Resolution: Fixed Status: Resolved (was: Ready to Commit) > (Accord) Cassandra bootstrap no longer using the range txn and instead uses > the sync point empty txn for reads > -- > > Key: CASSANDRA-19503 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19503 > Project: Cassandra > Issue Type: Bug > Components: Accord >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Fix For: 5.1 > > > Ephemeral reads made a change to ReadData which caused Bootstrap to no longer > use the range txn it generates and instead uses the empty txn from the sync > point. This was not detected in Accord due to ListRead supporting ranges, > and failed in Cassandra as we don’t support range reads. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19503) (Accord) Cassandra bootstrap no longer using the range txn and instead uses the sync point empty txn for reads
[ https://issues.apache.org/jira/browse/CASSANDRA-19503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Eggleston updated CASSANDRA-19503: Status: Ready to Commit (was: Review In Progress) +1 > (Accord) Cassandra bootstrap no longer using the range txn and instead uses > the sync point empty txn for reads > -- > > Key: CASSANDRA-19503 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19503 > Project: Cassandra > Issue Type: Bug > Components: Accord >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Fix For: 5.x > > > Ephemeral reads made a change to ReadData which caused Bootstrap to no longer > use the range txn it generates and instead uses the empty txn from the sync > point. This was not detected in Accord due to ListRead supporting ranges, > and failed in Cassandra as we don’t support range reads. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19503) (Accord) Cassandra bootstrap no longer using the range txn and instead uses the sync point empty txn for reads
[ https://issues.apache.org/jira/browse/CASSANDRA-19503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Eggleston updated CASSANDRA-19503: Reviewers: Blake Eggleston, Blake Eggleston (was: Blake Eggleston) Blake Eggleston, Blake Eggleston (was: Blake Eggleston) Status: Review In Progress (was: Patch Available) > (Accord) Cassandra bootstrap no longer using the range txn and instead uses > the sync point empty txn for reads > -- > > Key: CASSANDRA-19503 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19503 > Project: Cassandra > Issue Type: Bug > Components: Accord >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Fix For: 5.x > > > Ephemeral reads made a change to ReadData which caused Bootstrap to no longer > use the range txn it generates and instead uses the empty txn from the sync > point. This was not detected in Accord due to ListRead supporting ranges, > and failed in Cassandra as we don’t support range reads. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19503) (Accord) Cassandra bootstrap no longer using the range txn and instead uses the sync point empty txn for reads
[ https://issues.apache.org/jira/browse/CASSANDRA-19503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Blake Eggleston updated CASSANDRA-19503: Reviewers: Blake Eggleston > (Accord) Cassandra bootstrap no longer using the range txn and instead uses > the sync point empty txn for reads > -- > > Key: CASSANDRA-19503 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19503 > Project: Cassandra > Issue Type: Bug > Components: Accord >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Fix For: 5.x > > > Ephemeral reads made a change to ReadData which caused Bootstrap to no longer > use the range txn it generates and instead uses the empty txn from the sync > point. This was not detected in Accord due to ListRead supporting ranges, > and failed in Cassandra as we don’t support range reads. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19503) (Accord) Cassandra bootstrap no longer using the range txn and instead uses the sync point empty txn for reads
[ https://issues.apache.org/jira/browse/CASSANDRA-19503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-19503: -- Test and Documentation Plan: existing tests Status: Patch Available (was: Open) > (Accord) Cassandra bootstrap no longer using the range txn and instead uses > the sync point empty txn for reads > -- > > Key: CASSANDRA-19503 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19503 > Project: Cassandra > Issue Type: Bug > Components: Accord >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Fix For: 5.x > > > Ephemeral reads made a change to ReadData which caused Bootstrap to no longer > use the range txn it generates and instead uses the empty txn from the sync > point. This was not detected in Accord due to ListRead supporting ranges, > and failed in Cassandra as we don’t support range reads. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19503) (Accord) Cassandra bootstrap no longer using the range txn and instead uses the sync point empty txn for reads
[ https://issues.apache.org/jira/browse/CASSANDRA-19503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Capwell updated CASSANDRA-19503: -- Bug Category: Parent values: Correctness(12982)Level 1 values: Unrecoverable Corruption / Loss(13161) Complexity: Normal Discovered By: Unit Test Fix Version/s: 5.x Severity: Critical Status: Open (was: Triage Needed) > (Accord) Cassandra bootstrap no longer using the range txn and instead uses > the sync point empty txn for reads > -- > > Key: CASSANDRA-19503 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19503 > Project: Cassandra > Issue Type: Bug > Components: Accord >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Fix For: 5.x > > > Ephemeral reads made a change to ReadData which caused Bootstrap to no longer > use the range txn it generates and instead uses the empty txn from the sync > point. This was not detected in Accord due to ListRead supporting ranges, > and failed in Cassandra as we don’t support range reads. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org