plaofchina opened a new issue, #8900: URL: https://github.com/apache/seatunnel/issues/8900
### Search before asking - [x] I had searched in the [feature](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22Feature%22) and found no similar feature requirement. ### Description Firstly, Kafka manages offsets on its own, so the `group_offsets` option is meaningless. The configurations `earliest` and `latest` only take effect when consuming for the first time. There is no need to automatically force the consumed offset to be set to `earliest` or` latest` every time. Using `timestamp` and `specific_offsets` can meet certain scenarios, but there is a potential risk of human accidents in engineering use. Here, it is recommended to keep the configuration consistent with Kafka's default behavior without setting offsets,but should not be required. Only in cases where `timestamps` and `specific_offsets` are used should the settings be adjusted as needed. Pay attention to configuration changes when `restarting` the pipeline. ### Usage Scenario It should be an common usage scenario. we usually except that the configurations of offset only take effect when comsuming for the first time and shoul not take any effect when we restart out pipeline. ### Related issues _No response_ ### Are you willing to submit a PR? - [x] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
