hudi
hudi copied to clipboard
[HUDI-6297] Fixed issue in consuming transactional topic
Change Logs
Fixed issue in consuming Transactional Kafka Topic.
Impact
none
Risk level (write none, low medium or high below)
none
Documentation Update
none
Contributor's checklist
- [ ] Read through contributor's guide
- [ ] Change Logs and Impact were stated clearly
- [ ] Adequate tests were added if applicable
- [ ] CI passed
CI report:
- 9395a5cf8b4309e028959d0da471cbb66239e80b Azure: FAILURE
Bot commands
@hudi-bot supports the following commands:@hudi-bot run azurere-run the last Azure build
@ad1happy2go : Can you introduce the change in KafkaSource (with a config) which can wrap the RDD and handle the behavior instead of making the change in DeltaSync ?
hey @bvaradar : can you help with this issue. Do you have pointers on exactly once from kafka. looks like reading it OOB might result in data consistency issues as reported above.
Hey @nsivabalan , @bvaradar , @ad1happy2go - is this absolutely not going to happen anytime soon? It's preventing us from directly ingesting a large majority of our Kafka topics in our organisation and i'm very surprised it's not a more widely experienced issue, given its a common feature of topics produced through kafka-streams applications