[
https://issues.apache.org/jira/browse/CASSANDRA-14082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paulo Motta updated CASSANDRA-14082:
------------------------------------
Status: Patch Available (was: Open)
Rebased on top of latest now that CASSANDRA-13948, setting this to PA, tests
look good:
||3.11||trunk||
|[branch|https://github.com/apache/cassandra/compare/cassandra-3.11...pauloricardomg:3.11-14082]|[branch|https://github.com/apache/cassandra/compare/trunk...pauloricardomg:trunk-14082]|
|[testall|https://issues.apache.org/jira/secure/attachment/12902160/3.11-14082-testall.png]|[testall|https://issues.apache.org/jira/secure/attachment/12902158/trunk-14082-testall.png]|
|[dtest|https://issues.apache.org/jira/secure/attachment/12902161/3.11-14082-dtest.png]|[dtest|https://issues.apache.org/jira/secure/attachment/12902159/trunk-14082-dtest.png]|
> Do not expose compaction strategy index publicly
> ------------------------------------------------
>
> Key: CASSANDRA-14082
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14082
> Project: Cassandra
> Issue Type: Bug
> Reporter: Paulo Motta
> Assignee: Paulo Motta
> Attachments: 3.11-14082-dtest.png, 3.11-14082-testall.png,
> trunk-14082-dtest.png, trunk-14082-testall.png
>
>
> Before CASSANDRA-13215 we used the compaction strategy index to decide which
> disk to place a given sstable, but now we can get this directly from the disk
> boundary manager and keep the compaction strategy index internal only.
> This will ensure external consumers will use a consistent {{DiskBoundaries}}
> object to perform operations on multiple disks, rather than risking getting
> inconsistent indexes if the compaction strategy indexes change between
> successive calls to {{CSM.getCompactionStrategyIndex}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
