[
https://issues.apache.org/jira/browse/CASSANDRA-20772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-20772:
--------------------------------------
Attachment: ci_summary-trunk-7f05bd6e1403238c2260c6b7645e12dee17a534b.html
result_details-trunk-7f05bd6e1403238c2260c6b7645e12dee17a534b.tar.gz
> 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
>
> Attachments:
> ci_summary-trunk-7f05bd6e1403238c2260c6b7645e12dee17a534b.html,
> result_details-trunk-7f05bd6e1403238c2260c6b7645e12dee17a534b.tar.gz
>
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
