Class MigrationPushStrategyZKAccessor
- java.lang.Object
-
- com.linkedin.venice.controller.migration.MigrationPushStrategyZKAccessor
-
public class MigrationPushStrategyZKAccessor extends java.lang.Object
-
-
Field Summary
Fields Modifier and Type Field Description static java.lang.String
MIGRATION_PUSH_STRATEGY_PATH
-
Constructor Summary
Constructors Constructor Description MigrationPushStrategyZKAccessor(org.apache.helix.zookeeper.impl.client.ZkClient zkClient, HelixAdapterSerializer adapter)
-
Method Summary
All Methods Instance Methods Concrete Methods Modifier and Type Method Description java.util.Map<java.lang.String,java.lang.String>
getAllPushStrategies()
The reason to return the push strategy for all the stores: 1.void
setPushStrategy(java.lang.String voldemortStoreName, java.lang.String pushStrategyStr)
-
-
-
Field Detail
-
MIGRATION_PUSH_STRATEGY_PATH
public static final java.lang.String MIGRATION_PUSH_STRATEGY_PATH
- See Also:
- Constant Field Values
-
-
Constructor Detail
-
MigrationPushStrategyZKAccessor
public MigrationPushStrategyZKAccessor(org.apache.helix.zookeeper.impl.client.ZkClient zkClient, HelixAdapterSerializer adapter)
-
-
Method Detail
-
getAllPushStrategies
public java.util.Map<java.lang.String,java.lang.String> getAllPushStrategies()
The reason to return the push strategy for all the stores: 1. It is necessary for admin tool to retrieve push strategy for all the stores; 2. Right now,ControllerClient
doesn't provide a good way to recognize "not-exist" status since the backend always throws an exception; 3. Combo plugin needs to know whether the push strategy exists or not to decide whether to use the default push strategy; It is definitely possible to support 'not-exist' case: such as updating ControllerClient to be aware of '404', but right now I choose to return the push strategy for all the stores, and let client decide.
-
setPushStrategy
public void setPushStrategy(java.lang.String voldemortStoreName, java.lang.String pushStrategyStr)
-
-