[
https://issues.apache.org/jira/browse/KAFKA-13709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17642115#comment-17642115
]
Chris Egerton commented on KAFKA-13709:
---------------------------------------
I've decided to keep the rollback instructions out for now. The only potential
impact that they have is the extreme loss of source offsets in some extremely
niche scenarios, and loss of source offsets becomes a condition that must be
accounted for as soon as exactly-once support is disabled anyways.
> Document exactly-once support for source connectors
> ---------------------------------------------------
>
> Key: KAFKA-13709
> URL: https://issues.apache.org/jira/browse/KAFKA-13709
> Project: Kafka
> Issue Type: Task
> Components: KafkaConnect
> Reporter: Chris Egerton
> Assignee: Chris Egerton
> Priority: Major
>
> Add documentation for the support for exactly-once source connectors
> introduced in
> [KIP-618|https://cwiki.apache.org/confluence/display/KAFKA/KIP-618%3A+Exactly-Once+Support+for+Source+Connectors].
> This includes but is not limited to:
> * How to safely perform a rolling upgrade to enable exactly-once source
> support for an existing cluster
> * Any new APIs that connector authors can/should leverage for their source
> connectors that need clarification beyond what can be included in a Javadoc
> (for example, how to know what to return from
> {{{}SourceConnector::exactlyOnceSupport{}}}, and an example on how to define
> custom transaction boundaries for a connector)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
