pub struct KfFetchRequest<R>{
pub replica_id: i32,
pub max_wait: i32,
pub min_bytes: i32,
pub max_bytes: i32,
pub isolation_level: Isolation,
pub session_id: i32,
pub epoch: i32,
pub topics: Vec<FetchableTopic>,
pub forgotten: Vec<ForgottenTopic>,
pub data: PhantomData<R>,
}Fields§
§replica_id: i32The broker ID of the follower, of -1 if this request is from a consumer.
max_wait: i32The maximum time in milliseconds to wait for the response.
min_bytes: i32The minimum bytes to accumulate in the response.
max_bytes: i32The maximum bytes to fetch. See KIP-74 for cases where this limit may not be honored.
isolation_level: IsolationThis setting controls the visibility of transactional records. Using READ_UNCOMMITTED (isolation_level = 0) makes all records visible. With READ_COMMITTED (isolation_level = 1), non-transactional and COMMITTED transactional records are visible. To be more concrete, READ_COMMITTED returns all data from offsets smaller than the current LSO (last stable offset), and enables the inclusion of the list of aborted transactions in the result, which allows consumers to discard ABORTED transactional records
session_id: i32The fetch session ID.
epoch: i32The fetch session ID.
topics: Vec<FetchableTopic>The topics to fetch.
forgotten: Vec<ForgottenTopic>In an incremental fetch request, the partitions to remove.
data: PhantomData<R>