You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "David Capwell (Jira)" <ji...@apache.org> on 2025/07/16 18:15:00 UTC
[jira] [Updated] (CASSANDRA-20772) Accord Route Index does not filter based off txn_id range which causes segments which can't contain the data to be queried
[ https://issues.apache.org/jira/browse/CASSANDRA-20772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Capwell updated CASSANDRA-20772:
--------------------------------------
Change Category: Performance
Complexity: Low Hanging Fruit
Fix Version/s: NA
Status: Open (was: Triage Needed)
> Accord Route Index does not filter based off txn_id range which causes segments which can't contain the data to be queried
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-20772
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20772
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Accord
> Reporter: David Capwell
> Assignee: David Capwell
> Priority: Normal
> Fix For: NA
>
>
> When the accord route index searches for range transactions we pass in a min/max timestamp range to search for, but this gets ignored. The issue with ignoring it is that we will do unneeded disk searches as we will include segments that don’t have data for the range and must get filtered out after the read.
> We should respect the txn_id passed in to limit the segments to only the ones that “could” match.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org