All Classes and Interfaces
Class
Description
Configuration for a schema association (key or value).
Parser for Odyssey association configurations
Jackson-deserialisable representation of the JSON value supplied by the user for
confluent.key.association / confluent.value.association config keys.Which side of a record an association applies to: key or value.
Result of topic classification before token acquisition.
Clusterlink API client using the RM Java client with protobuf-based models.
Callback that applies stripped config changes via the Kafka controller.
Per-topic outcome of an Odyssey delete request.
Combined result of the DescribeConfigs Odyssey flow: the standard Kafka config response
enriched with per-topic association fetch results.
Disassociation request for a single topic.
Sets the external-schema type to MAYBE for the named topics, before their Schema Registry associations
are created.
Utility for building Kafka Logical Cluster CRNs.
Base exception for LSRC lookup failures.
Invalid LKC ID provided (null or empty).
RRI client error (network, timeout, service unavailable).
No LKCāLSRC mapping found in Resource Manager or missing endpoint in mapping.
Result of a Schema Registry endpoint lookup for a Logical Kafka Cluster.
Service for looking up Schema Registry endpoints from Resource Manager's RRI (Resource Relation Index).
Constants used throughout the Odyssey integration module.
Configuration keys for topic association configs.
Default values for Odyssey configurations.
Odyssey-owned error codes surfaced as the
schemaErrorCode on results; OdysseyConstants.ErrorCodes.code()
is the integer value.Error messages for common scenarios.
Metrics constants for Schema Management JMX surfaces.
Manages the integration between Kafka topic creation and Odyssey (Schema Registry) associations for K1.
Builder for OdysseyIntegrationManager.
Full Odyssey integration interface used by the controller server.
A resource's association payloads that the request carried as tagged bytes rather than as
inline config values, because they exceed the limit the protocol can encode in a string
field.
Read-only Odyssey integration operations used by the broker server.
Interface for managing asynchronous requests to Odyssey (Schema Registry).
Result of token acquisition from Token Platform.
Result of any Odyssey operation (validation, association creation, fetch, etc.).
Holds parsed association configurations for key and value.
Simple shim interface to make unit testing easier
Client interface for managing group dynamic configurations in the resource manager.
Implementation of RmGroupConfigClient using RmClient.
Client interface for managing HealthProbe resources in the resource manager.
Implementation of
RmHealthProbeClient using RmClient.Status reporter for managing InternalSwitchoverPair resource lifecycle.
Implementation of
RmMaterializedTableClient using RmClient.Factory for building raw Resource Manager
Client instances without
the RmClient wrapper.Helper for managing RM resource status, finalizers, and observed generation.
Client interface for managing StreamsTopology resources in the resource manager.
Implementation of RmStreamsTopologyClient using RmClient.
Simple shim interface for
Watcher.SubscriptionClient interface for managing topics and deleted topics in the resource manager.
Convenience wrapper around a
Client.Shim interface for
Watcher.Start a watch stream at its tail.
Continue a watch stream from a token.
Strategy for how the watch stream is initialized
Start a watch stream with a full snapshot.
Per-dependency drill-down metrics:
CallsPerSec (Meter), LatencyMs (Histogram),
ErrorsPerSec (Meter).Bounded classification of a dependency-call error, used as the
error_class tag.Per-request-type SLO metrics for Schema Management.
Client interface for obtaining Logical Access Tokens (LAT) from the Token Platform service.
Immutable configuration for
TokenPlatformClient.SPIRE authentication mode for the gRPC channel to Token Platform.
Exception thrown when Token Platform operations fail.
Categorizes the type of error for appropriate handling.
Context required to issue a Logical Access Token from Token Platform.
Association information for a single topic.
Functional interface for looking up topic IDs.
Context for the validation phase, containing classified topics and SR client.