[
https://issues.apache.org/jira/browse/CASSANDRA-9642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joshua McKenzie updated CASSANDRA-9642:
---------------------------------------
Fix Version/s: (was: 3.0.0 rc2)
3.0.x
2.2.x
2.1.x
> getSplits should not depend on selectAndReference()
> ---------------------------------------------------
>
> Key: CASSANDRA-9642
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9642
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Benedict
> Priority: Minor
> Fix For: 2.1.x, 2.2.x, 3.0.x
>
>
> It turns out this method that nobody thinks too much about is on the critical
> path for some pretty important functionality. It uses {{keySamples}} and
> (repeatedly) {{estimatedKeysForRange}}, both of which take references to all
> intersecting sstables.
> Both could quite easily and safely be switched to guarding by the {{OpOrder
> readOrdering}}, which is both less burden and guarantees the operation cannot
> be blocked by issues like CASSANDRA-9637.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
