nicochen opened a new issue, #3517: URL: https://github.com/apache/amoro/issues/3517
### What happened? Consider a scenario that a mixed table is initialized by a Spark batch job to fill history data and then is ingested with streaming data by Flink. The MixedTableMaintainer would never expire any snapshots of base table as it takes 'last-non-optimized snapshot time' into consideration to choose lower bound of snapshot to keep. The last-non-optimized snapshot in base table is generated by data initialisation and would not been updated any longer. Thus, in my scenario, the snapshots of base table would not been expired eventually. ### Affects Versions 0.7 ### What table formats are you seeing the problem on? Mixed-Iceberg, Mixed-Hive ### What engines are you seeing the problem on? AMS ### How to reproduce Refer to what happend ### Relevant log output ```shell ``` ### Anything else _No response_ ### Are you willing to submit a PR? - [x] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's Code of Conduct -- 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]
