LiebingYu opened a new issue, #2182: URL: https://github.com/apache/fluss/issues/2182
### Search before asking - [x] I searched in the [issues](https://github.com/apache/fluss/issues) and found nothing similar. ### Motivation Currently, Fluss tiering service won't do snapshot expiration for Paimon lake table, even though `'write-only' = 'false'` is set. When a Paimon table is set with `'write-only' = 'false'`, it indicates that the engine is expected to perform snapshot expiration. In my opinion, Fluss's tiering service should be consistent with this behavior—if users do not want snapshot expiration, they can set `'write-only' = 'true'`. ### Solution _No response_ ### Anything else? _No response_ ### Willingness to contribute - [x] I'm willing to submit a PR! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
