zhoulii opened a new issue, #10849: URL: https://github.com/apache/paimon/issues/10849
### Search before asking - [x] I searched in the [issues](https://github.com/apache/paimon/issues) and found nothing similar. ### Motivation Stricter validation after an upgrade can make existing table options invalid. [#10830](https://github.com/apache/paimon/pull/10830) decoupled catalog alter and drop operations from runtime table loading, but Flink and Spark still load tables before executing SQL metadata commands. Consequently, `SHOW CREATE TABLE`, `ALTER TABLE`, and `DROP TABLE` can still fail on runtime-invalid options, preventing users from inspecting, repairing, or deleting affected tables. ### Solution - Load file-store table definitions without initializing the runtime store, using the existing table-loading API - Defer runtime validation and store creation until the first scan, read, write, or commit operation. - Keep CREATE and ALTER validation before committing the resulting schema. ### Anything else? Follow-up to [#10829](https://github.com/apache/paimon/issues/10829) and #10830. ### 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]
