zhoulii commented on PR #10850: URL: https://github.com/apache/paimon/pull/10850#issuecomment-6572794716
Thanks for the suggestion. We did prototype a dedicated metadata-only loading path before choosing this design: [implementation branch](https://github.com/zhoulii/paimon/tree/fix/sql-catalog-metadata-operations). This is the preserved earlier prototype, shared for comparison. That version preserves eager validation for normal Core `getTable()`/`copy()` calls and routes engine lookups through `getTableForPlanning()` and `LazyFileStoreTable`. The implementation also adds a separate planning cache, wrapper delegation, and Catalog/engine integration, including compatibility handling for custom Catalog loading behavior. We preferred the current approach because it keeps one table-loading path and the existing cache, with effective-option validation and runtime initialization centralized in Core. CREATE and ALTER still validate the resulting schema before committing, and data operations still reject invalid runtime options. The SDK validation-timing change is an intentional compatibility trade-off. Do you consider preserving eager validation in Core `getTable()`/`copy()` a compatibility requirement here? If so, the dedicated path would be appropriate. Otherwise, I think the shared boundary is worth considering for its simpler lifecycle and lower maintenance cost. -- 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]
