[Bug] Partition expiration stuck in infinite failure loop when HMS drop succeeds but Paimon drop fails due to unhandled MetaException
- Dominant language
- Java
- Stars
- 3.4k
- Forks
- 1.4k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 396
Description
### Search before asking
- [x] I searched in the [issues](https://github.com/apache/paimon/issues) and found nothing similar.
### Paimon version
Paimon-1.1.1
### Compute Engine
Spark-3.5.0
### Minimal reproduce step
Executing the "CALL sys.expire_partitions" operation via the Spark engine:
1. Executing `partition expire` throws an exception after the HMS Drop Partition is completed, preventing subsequent Paimon partition metadata deletion processing.
2. Executing `partition expire` again will throw an exception.
### What doesn't meet your expectations?
Failed to correctly identify the partition not found exception
### Anything else?
_No response_
### Are you willing to submit a PR?
- [x] I'm willing to submit a PR!
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the Spark entry point for the `CALL sys.expire_partitions` operation and reproduce it on Paimon 1.1.1 with Spark 3.5.0. Trace how a successful HMS drop followed by an unhandled `MetaException` affects Paimon metadata deletion; done means the partition-expiration retry no longer fails in an infinite loop.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spark
- Domain
- data-engineering, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100