THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Operation | Resource Type | Resource Name |
|
| Offsets topic used by the connector, which is either the value of the |
Note that there is currently no use case for Connect that requires a consumer principal to be configured for source connectors. As a result, this proposed change technically introduces "new" configuration properties for source connectors: consumer-level overrides prefixed with consumer.override. , as described in KIP-458: Connector Client Config Override Policy.
Admin
If the offsets topic for a connector does not exist yet, the connector’s admin principal must be given the following permissions on the Kafka cluster it reads offsets from:
...
Additional configuration properties
The two user-facing configuration worker-level exactly.once.source.enabled and connector-level offsets.storage.topic configuration properties introduced here should not violate backwards compatibility, as they both come with default values that preserve existing behavior. Technically, an existing connector may expose a offsets.storage.topic configuration property that will now conflict with this newly-introduced framework property, but the risk is low enough to be acceptable.
The newly-introduced source connector consumer.override. -prefixed properties will also technically be backwards incompatible, but for the same reason that these properties were introduced in the first place for sink connectors, and the similar producer.override. - and admin.override. -prefixed properties were introduced for source connectors, this should be acceptable. The risk is low enough.
New Admin API
The new Admin methods for fencing producers will be implemented using existing protocols (specifically, FindCoordinator and InitProducerId), so no changes to the Kafka binary protocol will be required. As a result, these new methods should work on any broker that supports those protocols.
...