Class CoordinatorStrategy
java.lang.Object
org.apache.kafka.clients.admin.internals.CoordinatorStrategy
- All Implemented Interfaces:
AdminApiLookupStrategy<CoordinatorKey>
-
Nested Class Summary
Nested classes/interfaces inherited from interface org.apache.kafka.clients.admin.internals.AdminApiLookupStrategy
AdminApiLookupStrategy.LookupResult<K> -
Constructor Summary
ConstructorsConstructorDescriptionCoordinatorStrategy(org.apache.kafka.common.requests.FindCoordinatorRequest.CoordinatorType type, org.apache.kafka.common.utils.LogContext logContext) -
Method Summary
Modifier and TypeMethodDescriptionbooleanbatch()org.apache.kafka.common.requests.FindCoordinatorRequest.BuilderbuildRequest(Set<CoordinatorKey> keys) Build the lookup request for a set of keys.voidhandleResponse(Set<CoordinatorKey> keys, org.apache.kafka.common.requests.AbstractResponse abstractResponse) Callback that is invoked when a lookup request returns successfully.Define the scope of a given key for lookup.Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, waitMethods inherited from interface org.apache.kafka.clients.admin.internals.AdminApiLookupStrategy
handleUnsupportedVersionException
-
Constructor Details
-
CoordinatorStrategy
public CoordinatorStrategy(org.apache.kafka.common.requests.FindCoordinatorRequest.CoordinatorType type, org.apache.kafka.common.utils.LogContext logContext)
-
-
Method Details
-
lookupScope
Description copied from interface:AdminApiLookupStrategyDefine the scope of a given key for lookup. Key lookups are complicated by the need to accommodate different batching mechanics. For example, a `Metadata` request supports arbitrary batching of topic partitions in order to discover partitions leaders. This can be supported by returning a single scope object for all keys. On the other hand, `FindCoordinator` requests only support lookup of a single key. This can be supported by returning a different scope object for each lookup key. Note that if theApiRequestScope.destinationBrokerId()maps to a specific brokerId, then lookup will be skipped. See the use ofStaticBrokerStrategyinDescribeProducersHandlerfor an example of this usage.- Specified by:
lookupScopein interfaceAdminApiLookupStrategy<CoordinatorKey>- Parameters:
key- the lookup key- Returns:
- request scope indicating how lookup requests can be batched together
-
buildRequest
public org.apache.kafka.common.requests.FindCoordinatorRequest.Builder buildRequest(Set<CoordinatorKey> keys) Description copied from interface:AdminApiLookupStrategyBuild the lookup request for a set of keys. The grouping of the keys is controlled throughAdminApiLookupStrategy.lookupScope(Object). In other words, each set of keys that map to the same request scope object will be sent to this method.- Specified by:
buildRequestin interfaceAdminApiLookupStrategy<CoordinatorKey>- Parameters:
keys- the set of keys that require lookup- Returns:
- a builder for the lookup request
-
handleResponse
public AdminApiLookupStrategy.LookupResult<CoordinatorKey> handleResponse(Set<CoordinatorKey> keys, org.apache.kafka.common.requests.AbstractResponse abstractResponse) Description copied from interface:AdminApiLookupStrategyCallback that is invoked when a lookup request returns successfully. The handler should parse the response, check for errors, and return a result indicating which keys were mapped to a brokerId successfully and which keys received a fatal error (e.g. a topic authorization failure). Note that keys which receive a retriable error should be left out of the result. They will be retried automatically. For example, if the response of `FindCoordinator` request indicates an unavailable coordinator, then the key should be left out of the result so that the request will be retried.- Specified by:
handleResponsein interfaceAdminApiLookupStrategy<CoordinatorKey>- Parameters:
keys- the set of keys from the associated requestabstractResponse- the response received from the broker- Returns:
- a result indicating which keys mapped successfully to a brokerId and which encountered a fatal error
-
disableBatch
public void disableBatch() -
batch
public boolean batch()
-