Caused by: org.apache.iceberg.exceptions.ValidationException
- Dominant language
- Java
- Stars
- 1.2k
- Forks
- 395
- Avg merge
- 4d 10h
- Merged PRs (30d)
- 33
Description
Currently the iceberg is updated by kafka connect.
Optimizing job failed due to below error
Caused by: org.apache.iceberg.exceptions.ValidationException: Cannot commit, found new position delete for replaced data file:
Is there any way to fix it?
I also have already added below table properties:
self-optimizing.filte = created_at < '2025-01-01T00:00:00Z'
self-optimizing.allow-partial-commit =true
'self-optimizing.allow-partial-commit' = 'true',
'self-optimizing.max-file-count' = '3000',
'self-optimizing.max-task-size-bytes' = '67108864',
'self-optimizing.minor.trigger.file-count' = '8',
'self-optimizing.minor.trigger.interval' = '900000',
'self-optimizing.major.trigger.duplicate-ratio' = '0.2',
'self-optimizing.target-size' = '134217728',
'self-optimizing.fragment-ratio' = '8',
'self-optimizing.min-target-size-ratio' = '0.75',
'self-optimizing.min-plan-interval' = '60000'
Contributor guide
Research direction
No source file, test, or code entry point is identified in the issue. Start by reproducing the optimizing job while Kafka Connect updates the Iceberg table, then trace the conflicting position delete and verify that the chosen configuration or coordination change allows the optimization commit to complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, kafka
- Domain
- data-engineering, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100