vertx / io.vertx.reactivex.kafka.client.consumer / KafkaConsumer / seekToBeginning

seekToBeginning

open fun seekToBeginning(topicPartition: TopicPartition): KafkaConsumer<K, V>

Seek to the first offset for each of the given partition.

Parameters

topicPartition - topic partition for which seek

Return
current KafkaConsumer instance

open fun seekToBeginning(topicPartitions: MutableSet<TopicPartition>): KafkaConsumer<K, V>

Seek to the first offset for each of the given partitions.

Parameters

topicPartitions - topic partition for which seek

Return
current KafkaConsumer instance

open fun seekToBeginning(topicPartition: TopicPartition, completionHandler: Handler<AsyncResult<Void>>): KafkaConsumer<K, V>

Seek to the first offset for each of the given partition.

Due to internal buffering of messages, the will continue to observe messages fetched with respect to the old offset until some time after the given completionHandler is called. In contrast, the once the given completionHandler is called the io.vertx.reactivex.kafka.client.consumer.KafkaConsumer#batchHandler will only see messages consistent with the new offset.

Parameters

topicPartition - topic partition for which seek

completionHandler - handler called on operation completed

Return
current KafkaConsumer instance

open fun seekToBeginning(topicPartitions: MutableSet<TopicPartition>, completionHandler: Handler<AsyncResult<Void>>): KafkaConsumer<K, V>

Seek to the first offset for each of the given partitions.

Due to internal buffering of messages, the will continue to observe messages fetched with respect to the old offset until some time after the given completionHandler is called. In contrast, the once the given completionHandler is called the io.vertx.reactivex.kafka.client.consumer.KafkaConsumer#batchHandler will only see messages consistent with the new offset.

Parameters

topicPartitions - topic partition for which seek

completionHandler - handler called on operation completed

Return
current KafkaConsumer instance