jarredhj0214 opened a new pull request, #12047: URL: https://github.com/apache/gravitino/pull/12047
### What changes were proposed in this pull request? This PR increases the `table_column_version_info.column_comment` length from `VARCHAR(256)` to `VARCHAR(4096)` for all relational store backends: - MySQL - H2 - PostgreSQL It updates both schema initialization scripts and upgrade scripts so newly initialized databases and upgraded existing databases use the same column comment length. ### Why are the changes needed? Importing an external table can fail when a column comment is longer than 256 characters because Gravitino stores column metadata in `table_column_version_info.column_comment`. Increasing the column length to 4096 follows the discussion in #12038 and avoids import failures for most practical column comments. For comments larger than 4096, users can still customize their database schema definition. Fix: #12038 ### Does this PR introduce _any_ user-facing change? No API or configuration changes. The relational store schema now supports column comments up to 4096 characters in `table_column_version_info`. ### How was this patch tested? - Verified all `table_column_version_info.column_comment` definitions in MySQL, H2, and PostgreSQL schema scripts are updated to `VARCHAR(4096)`. - Verified related upgrade scripts include column type migration statements. - Ran `git diff --check`. -- 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]
