[Bug]: [SQL] BeamKafkaTable doesn't set commitOffsetsInFinalize to KafkaIO reader
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 196
Description
### What happened?
BeamKafkaTable creates a KafkaIO reader without `commitOffsetsInFinalize = true`, is it a bug? if the flink job restarted, than the KafkaIO will read messages decided by `auto.offset.reset` ? why BeamKafkaTable doesn't set commitOffsetsInFinalize to true implicitly?
### Issue Priority
Priority: 0 (outage / urgent vulnerability)
### Issue Components
- [ ] Component: Python SDK
- [ ] Component: Java SDK
- [ ] Component: Go SDK
- [ ] Component: Typescript SDK
- [ ] Component: IO connector
- [ ] Component: Beam examples
- [ ] Component: Beam playground
- [ ] Component: Beam katas
- [ ] Component: Website
- [ ] Component: Spark Runner
- [X] Component: Flink Runner
- [ ] Component: Samza Runner
- [ ] Component: Twister2 Runner
- [ ] Component: Hazelcast Jet Runner
- [ ] Component: Google Cloud Dataflow Runner
Contributor guide
Assessment
This issue has not been assessed yet.