yuqi1129 opened a new pull request, #13588: URL: https://github.com/apache/gravitino/pull/13588
### What changes were proposed in this pull request? After creating a Doris table, compare the stored comment with the submitted comment and restore it with `ALTER TABLE ... MODIFY COMMENT` when they differ. Preserve the Gravitino ID suffix and SQL escaping, reuse the metadata lookup helper, and add unit tests, Doris 2.1.0 integration coverage, and documentation. ### Why are the changes needed? Doris 2.1.0 with Nereids enabled can replace a supplied CREATE TABLE comment with `OLAP`. The existing read-time fallback cannot recover a comment that was lost during creation. Related to #13346; follow-up to #13347. ### Does this PR introduce _any_ user-facing change? Table comments now survive creation on affected Doris servers without changing planner settings or adding catalog properties. Repair requires ALTER permission. If metadata lookup or repair fails after CREATE succeeds, the error is reported and the created table may remain. ### How was this patch tested? - The unpatched Doris 2.1.0 regression failed both comment cases with `OLAP`; the patched run passed all 3 integration tests with Nereids enabled, including special characters and Gravitino ID preservation. - All 83 Doris module unit tests passed, covering conditional repair, escaping, failed CREATE, and lookup/repair errors. - Comment round-trip integration tests passed on Doris 1.2.7 and 4.0.6 (5 integration tests passed in total). - `./gradlew spotlessApply` and `git diff --check` passed. Run the Doris module unit suite with `./gradlew :catalogs:catalog-jdbc-doris:test -PskipITs -PskipDockerTests=true`. Run the new integration coverage with `./gradlew :catalogs:catalog-jdbc-doris:test --tests '*CatalogDoris2xIT' -PskipDockerTests=false -PdorisMultiVersionTest`. -- 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]
