[
https://issues.apache.org/jira/browse/CASSANDRA-21631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francisco Guerrero updated CASSANDRA-21631:
-------------------------------------------
Description:
{{SSTableImporter.importNewSSTables()}} does not consult
{{KeyspaceMigrationInfo.shouldUseTrackedTransfers()}} to make a decision on
whether the SSTables are still pending or have completed migration for specific
ranges. Currently, the decision is purely based on
{{cfs.metadata().replicationType().isTracked()}} without accounting for the
migration state.
This is a follow-up to CASSANDRA-21626
was:
{{SSTableImporter.importNewSSTables()}} does not consult
{{KeyspaceMigrationInfo.shouldUseTrackedTransfers()}} to make a decision on
whether the SSTables are still pending or have completed migration for specific
ranges. Currently, the decision is purely based on
{{cfs.metadata().replicationType().isTracked()}} without accounting for the
migration state.
This is a follow-up to https://issues.apache.org/jira/browse/CASSANDRA-21626
> CEP-45: nodetool import is not migration-aware
> ----------------------------------------------
>
> Key: CASSANDRA-21631
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21631
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Tool/nodetool
> Reporter: Francisco Guerrero
> Assignee: Francisco Guerrero
> Priority: Normal
>
> {{SSTableImporter.importNewSSTables()}} does not consult
> {{KeyspaceMigrationInfo.shouldUseTrackedTransfers()}} to make a decision on
> whether the SSTables are still pending or have completed migration for
> specific ranges. Currently, the decision is purely based on
> {{cfs.metadata().replicationType().isTracked()}} without accounting for the
> migration state.
> This is a follow-up to CASSANDRA-21626
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
