[
https://issues.apache.org/jira/browse/KAFKA-14829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Grant updated KAFKA-14829:
---------------------------------
Description: Currently, we have various bits of reassignment logic spread
across different classes. For example, `ReplicationControlManager` contains
logic for when a reassignment is in progress, which is duplication in
`PartitionChangeBuilder`. Another example is `PartitionReassignmentRevert`
which contains logic for how to undo/revert a reassignment. The idea here is to
move the logic to `PartitionReassignmentReplicas` so its more testable and
easier to reason about. (was: Currently, we have various bits of reassignment
logic spread across different classes. For example, `ReplicationControlManager`
contains logic for when a reassignment is in progress, which is duplication in
`PartitionChangeBuilder`. Another example is `PartitionReassignmentRevert`
which contains logic for how to undo/revert a reassignment. The idea here is to
move the logic to )
> Consolidate reassignment logic in PartitionReassignmentReplicas
> ---------------------------------------------------------------
>
> Key: KAFKA-14829
> URL: https://issues.apache.org/jira/browse/KAFKA-14829
> Project: Kafka
> Issue Type: Improvement
> Reporter: Andrew Grant
> Assignee: Andrew Grant
> Priority: Minor
>
> Currently, we have various bits of reassignment logic spread across different
> classes. For example, `ReplicationControlManager` contains logic for when a
> reassignment is in progress, which is duplication in
> `PartitionChangeBuilder`. Another example is `PartitionReassignmentRevert`
> which contains logic for how to undo/revert a reassignment. The idea here is
> to move the logic to `PartitionReassignmentReplicas` so its more testable and
> easier to reason about.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)