vertx / io.vertx.rxjava.kafka.client.consumer / KafkaConsumer / pause

# pause

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

Suspend fetching from the requested partition.

### Parameters

`topicPartition` - topic partition from which suspend fetching

Return
current KafkaConsumer instance

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

Suspend fetching from the requested partitions.

### Parameters

`topicPartitions` - topic partition from which suspend fetching

Return
current KafkaConsumer instance

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

Suspend fetching from the requested partition.

Due to internal buffering of messages, the will continue to observe messages from the given `topicParation` until some time after the given `completionHandler` is called. In contrast, the once the given `completionHandler` is called the `io.vertx.rxjava.kafka.client.consumer.KafkaConsumer#batchHandler` will not see messages from the given `topicParation`.

### Parameters

`topicPartition` - topic partition from which suspend fetching

`completionHandler` - handler called on operation completed

Return
current KafkaConsumer instance

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

Suspend fetching from the requested partitions.

Due to internal buffering of messages, the will continue to observe messages from the given `topicParations` until some time after the given `completionHandler` is called. In contrast, the once the given `completionHandler` is called the `io.vertx.rxjava.kafka.client.consumer.KafkaConsumer#batchHandler` will not see messages from the given `topicParations`.

### Parameters

`topicPartitions` - topic partition from which suspend fetching

`completionHandler` - handler called on operation completed

Return
current KafkaConsumer instance