pub struct ListOffsetsRequest {
pub replica_id: Int32,
pub isolation_level: Option<IsolationLevel>,
pub topics: Vec<ListOffsetsRequestTopic>,
}Fields§
§replica_id: Int32The broker ID of the requestor, or -1 if this request is being made by a normal consumer.
isolation_level: Option<IsolationLevel>This 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.
As per KIP-98 the default is READ_UNCOMMITTED.
Added in version 2.
topics: Vec<ListOffsetsRequestTopic>Each topic in the request.
Note: A topic may only appear once within the request.
Trait Implementations§
Source§impl Debug for ListOffsetsRequest
impl Debug for ListOffsetsRequest
Source§impl RequestBody for ListOffsetsRequest
impl RequestBody for ListOffsetsRequest
Source§const API_VERSION_RANGE: ApiVersionRange
const API_VERSION_RANGE: ApiVersionRange
At the time of writing this is the same subset supported by rdkafka
Source§const FIRST_TAGGED_FIELD_IN_REQUEST_VERSION: ApiVersion
const FIRST_TAGGED_FIELD_IN_REQUEST_VERSION: ApiVersion
Source§type ResponseBody = ListOffsetsResponse
type ResponseBody = ListOffsetsResponse
Source§const FIRST_TAGGED_FIELD_IN_RESPONSE_VERSION: ApiVersion = Self::FIRST_TAGGED_FIELD_IN_REQUEST_VERSION
const FIRST_TAGGED_FIELD_IN_RESPONSE_VERSION: ApiVersion = Self::FIRST_TAGGED_FIELD_IN_REQUEST_VERSION
FIRST_TAGGED_FIELD_IN_REQUEST_VERSION but
there are some special snowflakes.