[
https://issues.apache.org/jira/browse/KAFKA-4107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16160414#comment-16160414
]
Randall Hauch commented on KAFKA-4107:
--------------------------------------
I wonder if it's better to handle any of the offset stores rather than only
handle offsets are stored in Kafka topics. The tool can read the worker
configuration file instead:
{code}
bin/kafka-connect-source-offset-reset.sh --config=my-worker-config.properties
--export --to-file=my-offsets.json
{code}
and
{code}
bin/kafka-connect-source-offset-reset.sh --config=my-worker-config.properties
--update --from-file=my-offsets.json
{code}
> Support offset reset capability in Kafka Connect
> ------------------------------------------------
>
> Key: KAFKA-4107
> URL: https://issues.apache.org/jira/browse/KAFKA-4107
> Project: Kafka
> Issue Type: Improvement
> Components: KafkaConnect
> Reporter: Jason Gustafson
>
> It would be useful in some cases to be able to reset connector offsets. For
> example, if a topic in Kafka corresponding to a source database is
> accidentally deleted (or deleted because of corrupt data), an administrator
> may want to reset offsets and reproduce the log from the beginning. It may
> also be useful to have support for overriding offsets, but that seems like a
> less likely use case.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
