Struct RdKafkaPropertiesConsumer

pub struct RdKafkaPropertiesConsumer {
    pub queued_min_messages: Option<usize>,
    pub queued_max_messages_kbytes: Option<usize>,
    pub fetch_wait_max_ms: Option<usize>,
    pub fetch_queue_backoff_ms: Option<usize>,
    pub fetch_max_bytes: Option<usize>,
    pub enable_auto_commit: Option<bool>,
}

Properties for the rdkafka library. Leave a field as None to use the default value. These properties are not intended to be exposed to users in the majority of cases.

See also https://github.com/confluentinc/librdkafka/blob/master/CONFIGURATION.md

Fields

queued_min_messages: Option<usize>

Minimum number of messages per topic+partition librdkafka tries to maintain in the local consumer queue.

queued_max_messages_kbytes: Option<usize>

fetch_wait_max_ms: Option<usize>

Maximum time the broker may wait to fill the Fetch response with fetch.min.bytes of messages.

fetch_queue_backoff_ms: Option<usize>

How long to postpone the next fetch request for a topic+partition in case the current fetch queue thresholds (queued.min.messages or queued.max.messages.kbytes) have been exceeded. This property may need to be decreased if the queue thresholds are set low and the application is experiencing long (~1s) delays between messages. Low values may increase CPU utilization.

fetch_max_bytes: Option<usize>

Maximum amount of data the broker shall return for a Fetch request. Messages are fetched in batches by the consumer and if the first message batch in the first non-empty partition of the Fetch request is larger than this value, then the message batch will still be returned to ensure the consumer can make progress. The maximum message batch size accepted by the broker is defined via message.max.bytes (broker config) or max.message.bytes (broker topic config). fetch.max.bytes is automatically adjusted upwards to be at least message.max.bytes (consumer config).

enable_auto_commit: Option<bool>

Whether to automatically and periodically commit offsets in the background.

Note that RisingWave does NOT rely on committed offsets. Committing offset is only for exposing the progress for monitoring. Setting this to false can avoid creating consumer groups.

default: true

Implementations

impl RdKafkaPropertiesConsumer

pub fn set_client(&self, c: &mut ClientConfig)

Trait Implementations

impl Clone for RdKafkaPropertiesConsumer

fn clone(&self) -> RdKafkaPropertiesConsumer

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for RdKafkaPropertiesConsumer

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for RdKafkaPropertiesConsumer

fn default() -> RdKafkaPropertiesConsumer

Returns the “default value” for a type.

impl<'de> Deserialize<'de> for RdKafkaPropertiesConsumer

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl WithOptions for RdKafkaPropertiesConsumer