chenxinwei opened a new issue, #5080: URL: https://github.com/apache/paimon/issues/5080
### Search before asking - [x] I searched in the [issues](https://github.com/apache/paimon/issues) and found nothing similar. ### Motivation In the data backtracking scenario of Flink tasks, sometimes we don't want to use the latest partition during the lookup join. Instead, we expect to restore the original state of the data as much as possible by specifying a fixed partition. We introduce a fixed partition mechanism here to look up the given partition. Refer to the following example： CREATE TABLE customers ( id INT, name STRING, country STRING, zip STRING, dt STRING, PRIMARY KEY (id, dt) NOT ENFORCED ) PARTITIONED BY (dt); SELECT o.order_id, o.total, c.country, c.zip FROM orders AS o JOIN customers /*+ OPTIONS('lookup.fixed-partition'='2025-02-13') */ FOR SYSTEM_TIME AS OF o.proc_time AS c ON o.customer_id = c.id; ### Solution _No response_ ### Anything else? _No response_ ### Are you willing to submit a PR? - [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]
