< Back
 

# Packages

-  package root
  Definition Classes
    root
-  package kafka
  Definition Classes
    root
-  package manager

  Definition Classes
    kafka
-  package utils

  Definition Classes
    manager
-  package logkafka81
  Definition Classes
    utils
-  package logkafka82
  Definition Classes
    utils
-  package one10
  Definition Classes
    utils
- BaseKey
- CommitRecordMetadataAndOffset
- Defaults
- GroupMetadata
- GroupMetadataKey
- GroupMetadataManager
- GroupOverview
- GroupTopicPartition
- LogConfig
- MemberMetadata
- OffsetKey
-  package two00
  Definition Classes
    utils
-  package zero10
  Definition Classes
    utils
-  package zero11
  Definition Classes
    utils
-  package zero81
  Definition Classes
    utils
-  package zero82
  Definition Classes
    utils
-  package zero90
  Definition Classes
    utils

p

kafka.manager.utils

# one10 

#### package one10

 
Ordering

1. Alphabetic

Visibility

1. Public
2. All

### Type Members

1.  trait BaseKey extends AnyRef
2.  case class CommitRecordMetadataAndOffset(appendedBatchOffset: Option[Long], offsetAndMetadata: OffsetAndMetadata) extends Product with Serializable

   We cache offset commits along with their commit record offset.

   We cache offset commits along with their commit record offset. This enables us to ensure that the latest offset commit is always materialized when we have a mix of transactional and regular offset commits. Without preserving information of the commit record offset, compaction of the offsets topic it self may result in the wrong offset commit being materialized.

3.  class GroupMetadata extends Logging

   Group contains the following metadata:

   Group contains the following metadata:

   Membership metadata:

   1. Members registered in this group 2. Current protocol assigned to the group (e.g. partition assignment strategy for consumers) 3. Protocol metadata associated with group members

   State metadata:

   1. group state 2. generation id 3. leader id
   Annotations
     @nonthreadsafe()
4.  case class GroupMetadataKey(version: Short, key: String) extends BaseKey with Product with Serializable
5.  case class GroupOverview(groupId: String, protocolType: String) extends Product with Serializable

   Case class used to represent group metadata for the ListGroups API

6.  case class GroupTopicPartition(group: String, topicPartition: TopicPartition) extends Product with Serializable
7.  case class LogConfig(props: Map[_, _], overriddenConfigs: Set[String] = Set.empty) extends AbstractConfig with Product with Serializable
8.  case class MemberMetadata(memberId: String, groupId: String, clientId: String, clientHost: String, protocolType: String, supportedProtocols: List[(String, Set[String])], assignment: Set[(String, Int)]) extends Product with Serializable

   Member metadata contains the following metadata:

   Member metadata contains the following metadata:

   Heartbeat metadata: 1. negotiated heartbeat session timeout 2. timestamp of the latest heartbeat

   Protocol metadata: 1. the list of supported protocols (ordered by preference) 2. the metadata associated with each protocol

   In addition, it also contains the following state information:

   1. Awaiting rebalance callback: when the group is in the prepare-rebalance state, its rebalance callback will be kept in the metadata if the member has sent the join group request 2. Awaiting sync callback: when the group is in the awaiting-sync state, its sync callback is kept in metadata until the leader provides the group assignment and the group transitions to stable

9.  case class OffsetKey(version: Short, key: GroupTopicPartition) extends BaseKey with Product with Serializable

### Value Members

1.  object Defaults
2.  object GroupMetadata
3.  object GroupMetadataManager

   Messages stored for the group topic has versions for both the key and value fields.

   Messages stored for the group topic has versions for both the key and value fields. Key version is used to indicate the type of the message (also to differentiate different types of messages from being compacted together if they have the same field values); and value version is used to evolve the messages within their data types:

   key version 0: group consumption offset -> value version 0: [offset, metadata, timestamp]

   key version 1: group consumption offset -> value version 1: [offset, metadata, commit_timestamp, expire_timestamp]

   key version 2: group metadata -> value version 0: [protocol_type, generation, protocol, leader, members]

4.  object LogConfig extends TopicConfigs with Serializable
5.  object MemberMetadata extends Serializable

### Ungrouped