Skip to content

Commit

Permalink
Extract ClusterTopicManipulationService out of SingleClusterMonitor s…
Browse files Browse the repository at this point in the history
…uch that it can be instantiated as a separate service

Extract ClusterTopicManipulationService out of SingleClusterMonitor such that it can be instantiated as a separate service rather than part of the SingleClusterMonitor App

Signed-off-by: Andrew Choi <[email protected]>
  • Loading branch information
Andrew Choi authored Sep 15, 2020
1 parent 41d2012 commit f91c04e
Showing 1 changed file with 0 additions and 3 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,6 @@

package com.linkedin.xinfra.monitor.apps;

import com.linkedin.xinfra.monitor.services.ClusterTopicManipulationServiceFactory;
import com.linkedin.xinfra.monitor.services.ConsumeService;
import com.linkedin.xinfra.monitor.services.ConsumerFactory;
import com.linkedin.xinfra.monitor.services.ConsumerFactoryImpl;
Expand Down Expand Up @@ -68,13 +67,11 @@ public SingleClusterMonitor(Map<String, Object> props, String name) throws Excep

ProduceService produceService = new ProduceService(props, name);
ConsumeService consumeService = new ConsumeService(name, topicPartitionResult, consumerFactory);
Service clusterTopicManipulationService = new ClusterTopicManipulationServiceFactory(props, name).createService();

_allServices = new ArrayList<>(SERVICES_INITIAL_CAPACITY);
_allServices.add(_topicManagementService);
_allServices.add(produceService);
_allServices.add(consumeService);
_allServices.add(clusterTopicManipulationService);
}

@Override
Expand Down

0 comments on commit f91c04e

Please sign in to comment.