JimmyWang6 commented on PR #19820: URL: https://github.com/apache/kafka/pull/19820#issuecomment-3000025791
Hi @AndrewJSchofield @chia7712 I have updated the PR and resolved several bugs. Here are some of my test scenarios： 1. When a single shareConsumer subscribes to a single topic, consumes some messages, and then exits and , it can subsequently consume all previously consumed messages again after resetting the offset to ealiest. 2. When a single shareConsumer subscribes to mutiple topics, then excute `bin/kafka-share-groups.sh --reset-offsets --execute --to-earliest --all-topics --group test-group --bootstrap-server localhost:9092 `, the offset of all the topics were reset. 3. When a single shareConsumer subscribes to mutiple topics, consumes some messages, and then exits, it can subsequently consume all previously consumed messages again after resetting the consumption offset. 4. If no topic argument is provided when running `bin/kafka-share-groups.sh --bootstrap-server localhost:9092 --group test-group --reset-offsets --dry-run`, the following exception occurs: Option [reset-offsets] requires one of these options: [all-topics] or [topic]. 5. When none of `to-datetime`, `to-earliest` or `to-latest` are specified, the execution failed with an error `Option '[reset-offsets]' requires one of the following scenarios: [[to-datetime], [to-earliest], [to-latest]]` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: jira-unsubscr...@kafka.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
