zhoulii opened a new issue, #10829: URL: https://github.com/apache/paimon/issues/10829
### Search before asking - [x] I searched in the [issues](https://github.com/apache/paimon/issues) and found nothing similar. ### Motivation Stricter option validation after an upgrade can make existing tables fail to load. Since catalog alter and drop operations depend on runtime table loading, users may be unable to correct invalid options or delete the affected table. Metadata management should remain available when persisted options fail runtime validation. ### Solution - For `alterTable`, load the existing schema directly, apply all requested changes, and validate the resulting schema before committing. - For `dropTable`, collect cleanup paths from schema and branch metadata without constructing a runtime table. - Preserve existing schema evolution restrictions, deletion semantics, and runtime validation. ### 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]
