[CASSANDRA-11369] Re-use IndexedEntry / IndexInfo after 11206

• Type: Improvement
• Status: Open
• Priority: Low
• Resolution: Unresolved
• Fix Version/s: 5.x
• Component/s: Legacy/Local Write-Read Paths
• Assignee: Unassigned Assign to me
• Reporter: Robert Stupp
• Created: 17/Mar/16 09:33
• Updated: 07/Mar/23 10:54

Description

CASSANDRA-8180 introduced UnfilteredRowIteratorWithLowerBound#getPartitionIndexLowerBound which relies on IndexInfo being present in the key-cache. But CASSANDRA-11206 will remove the presence of IndexInfo objects in-memory.

This ticket is about to re-add that functionality if feasible.

Currently tagged with fix-version 3.x, if it is possible to to that without changing summary or index disk structures - but maybe it's necessary to change the on-disk structure, which means we can do this in 4.x.

Issue Links

• is blocked by: CASSANDRA-11206 Support large partitions on the 3.0 sstable format
• is related to: CASSANDRA-8180 Optimize disk seek using min/max column name meta data when the LIMIT clause is used