Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This KIP is considering adding these options:

Scenarios

One Only one scenario should be defined for `input-topics` to proceed with the execution. If not,`to-earliest` will be used by default.

...

2. Use `kafka-consumer-groups` `reset-offsets` tool in the background to reset offset of input topics (including all partitions) on  (it will support the same format to specify partitions, e.g. `topic2:0,1,2`) on `kafka-streams-application-reset` execution.

23. Change `kafka-streams-application-reset` `dry-run` option for Execution Options described above. This is proposed to align execution options between both tools.

3. Remove `kafka-streams-application-reset` `zookeeper` option, removing Zookeeper dependency. With less arguments, tools will be easier to use, as `KafkaAdminClient` can replace `ZKUtils` functionality. This will include fixing 

Jira
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyKAFKA-4327

4. Keep execution parameters uniform between both tools: It will execute by default, and have a `dry-run` parameter just show the results. This will involve change current `ConsumerGroupCommand` to change execution options.

...

We will keep both tools `kafka-streams-application-reset` and `reset-offsets`, reusing `reset-offsets` on the background when `kafka-streams-application-reset` is executed.

Zookeeper dependency will be handled by KIP-198.


[1] KIP-122: Add Reset Consumer Group Offsets tooling

...