Uses of Class
io.confluent.parallelconsumer.state.WorkContainer
Packages that use WorkContainer
Package
Description
-
Uses of WorkContainer in io.confluent.parallelconsumer
Fields in io.confluent.parallelconsumer declared as WorkContainerMethods in io.confluent.parallelconsumer that return WorkContainerModifier and TypeMethodDescriptionprotected WorkContainer<K,V> RecordContext.getWorkContainer()RecordContextInternal.getWorkContainer()Methods in io.confluent.parallelconsumer that return types with arguments of type WorkContainerModifier and TypeMethodDescriptionList<WorkContainer<K,V>> PollContextInternal.getWorkContainers()PollContextInternal.streamWorkContainers()Methods in io.confluent.parallelconsumer with parameters of type WorkContainerModifier and TypeMethodDescriptionRecordContext.RecordContextBuilder.workContainer(WorkContainer<K, V> workContainer) Constructors in io.confluent.parallelconsumer with parameters of type WorkContainerModifierConstructorDescriptionRecordContext(WorkContainer<K, V> wc) RecordContext(WorkContainer<K, V> workContainer, org.apache.kafka.clients.consumer.ConsumerRecord<K, V> consumerRecord) Constructor parameters in io.confluent.parallelconsumer with type arguments of type WorkContainer -
Uses of WorkContainer in io.confluent.parallelconsumer.internal
Methods in io.confluent.parallelconsumer.internal with parameters of type WorkContainerModifier and TypeMethodDescriptionprotected voidAbstractParallelEoSStreamProcessor.addToMailbox(WorkContainer<K, V> wc) protected voidAbstractParallelEoSStreamProcessor.addToMailBoxOnUserFunctionSuccess(WorkContainer<K, V> wc, List<?> resultsFromUserFunction) protected voidExternalEngine.addToMailBoxOnUserFunctionSuccess(WorkContainer<K, V> wc, List<?> resultsFromUserFunction) With Vertx and Reactor, a function hasn't succeeded until the inner vertx function has also succeeded no opprotected voidAbstractParallelEoSStreamProcessor.onUserFunctionSuccess(WorkContainer<K, V> wc, List<?> resultsFromUserFunction) protected voidExternalEngine.onUserFunctionSuccess(WorkContainer<K, V> wc, List<?> resultsFromUserFunction) With Vertx and Reactor, a function hasn't succeeded until the inner vertx function has also succeeded loggingMethod parameters in io.confluent.parallelconsumer.internal with type arguments of type WorkContainerModifier and TypeMethodDescriptionprotected <R> List<ParallelConsumer.Tuple<org.apache.kafka.clients.consumer.ConsumerRecord<K,V>, R>> AbstractParallelEoSStreamProcessor.runUserFunction(Function<PollContextInternal<K, V>, List<R>> usersFunction, Consumer<R> callback, List<WorkContainer<K, V>> workContainerBatch) Run the supplied function.protected <R> voidAbstractParallelEoSStreamProcessor.submitWorkToPool(Function<PollContextInternal<K, V>, List<R>> usersFunction, Consumer<R> callback, List<WorkContainer<K, V>> workToProcess) Submit a piece of work to the processing pool. -
Uses of WorkContainer in io.confluent.parallelconsumer.state
Methods in io.confluent.parallelconsumer.state that return WorkContainerMethods in io.confluent.parallelconsumer.state that return types with arguments of type WorkContainerModifier and TypeMethodDescriptionProcessingShard.getEntries()Map of offset to WorkUnits.List<Consumer<WorkContainer<K,V>>> WorkManager.getSuccessfulWorkListeners()Useful for testingList<WorkContainer<K,V>> ShardManager.getWorkIfAvailable(int requestedMaxWorkToRetrieve) List<WorkContainer<K,V>> WorkManager.getWorkIfAvailable()Get work with no limit on quantity, useful for testing.List<WorkContainer<K,V>> WorkManager.getWorkIfAvailable(int requestedMaxWorkToRetrieve) Depth first work retrieval.Methods in io.confluent.parallelconsumer.state with parameters of type WorkContainerModifier and TypeMethodDescriptionvoidPartitionState.addWorkContainer(WorkContainer<K, V> wc) voidPartitionStateManager.addWorkContainer(WorkContainer<K, V> wc) voidProcessingShard.addWorkContainer(WorkContainer<K, V> wc) voidRemovedPartitionState.addWorkContainer(WorkContainer<K, V> wc) voidShardManager.addWorkContainer(WorkContainer<K, V> wc) booleanWorkManager.checkIfWorkIsStale(WorkContainer<K, V> workContainer) Have our partitions been revoked?intWorkContainer.compareTo(WorkContainer o) booleanPartitionStateManager.couldBeTakenAsWork(WorkContainer<?, ?> workContainer) voidWorkManager.handleFutureResult(WorkContainer<K, V> wc) booleanPartitionStateManager.isAllowedMoreRecords(WorkContainer<?, ?> wc) static ShardKeyShardKey.of(WorkContainer<?, ?> wc, ParallelConsumerOptions.ProcessingOrder ordering) voidPartitionState.onFailure(WorkContainer<K, V> work) voidPartitionStateManager.onFailure(WorkContainer<K, V> wc) voidShardManager.onFailure(WorkContainer<?, ?> wc) Idempotent - work may have not been removed, either way it's put backvoidWorkManager.onFailureResult(WorkContainer<K, V> wc) voidPartitionState.onSuccess(WorkContainer<K, V> work) voidPartitionStateManager.onSuccess(WorkContainer<K, V> wc) voidProcessingShard.onSuccess(WorkContainer<?, ?> wc) voidRemovedPartitionState.onSuccess(WorkContainer<K, V> work) voidShardManager.onSuccess(WorkContainer<?, ?> wc) voidWorkManager.onSuccessResult(WorkContainer<K, V> wc) Method parameters in io.confluent.parallelconsumer.state with type arguments of type WorkContainerModifier and TypeMethodDescriptionbooleanWorkManager.checkIfWorkIsStale(List<WorkContainer<K, V>> workContainers) Have our partitions been revoked? Can a batch contain messages of different epochs?