[Feature] Automatically detect changes to the expiration policy.
- 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.
### Motivation
After modifying the snapshot expiration policy, a restart of the writer or compactor job is required for the new configuration to take effect. This process is inconvenient, and it would be better if the system could automatically detect configuration changes.
### Solution
detect configuration changes when expire snapshot.
### 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 at the snapshot-expiration path described as "expire snapshot" and inspect how the expiration policy is loaded and reused after configuration changes. Done means a running writer or compactor applies a modified policy without requiring a restart; add or update tests for that behavior if the repository provides them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100