yuqi1129 opened a new issue, #12941: URL: https://github.com/apache/gravitino/issues/12941
### Version main branch ### Describe what's wrong JDBC catalogs append Gravitino's internal entity identifier to source table comments when creating tables. Gravitino hides this marker on read, but it remains visible in the source database. Table comments should preserve user-provided text. For JDBC sources without a suitable metadata property, entity identity should remain in Gravitino's entity store. ### Error message and/or stacktrace No exception. A comment such as `created through Gravitino` becomes: ```text created through Gravitino (From Gravitino, DO NOT EDIT: gravitino.v1.uid...) ``` ### How to reproduce 1. Create a MySQL table through Gravitino with a comment. 2. Query `information_schema.tables.table_comment`. 3. Compare it with the comment returned by Gravitino. ### Additional context The shared `JdbcCatalogOperations.createTable()` injects the marker. Several JDBC connectors also preserve or append markers when updating comments. The fix should stop writing markers, retain compatibility when reading existing tables, and cover entity identity and rename behavior with tests. Related: #1751. -- 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]
