yuqi1129 opened a new issue, #13417: URL: https://github.com/apache/gravitino/issues/13417
### What would you like to be improved? When a JDBC catalog does not support schema comments, `JdbcDatabaseOperations.create` rejects a create request that carries one with: ``` Doesn't support setting schema comment: <comment value> ``` The message appends the comment VALUE where the schema name belongs and reads as a fragment, e.g. `Doesn't support setting schema comment: probe`. On the server it surfaces as: ``` 501 Failed to operate schema(s) [probe_schema] operation [CREATE] under catalog [oracle], reason [Doesn't support setting schema comment: probe] ``` The same wording is duplicated in `ClickHouseDatabaseOperations`. ### How should we improve? Name the schema and state what is unsupported, for example: ``` Schema probe_schema: catalog does not support schema comments ``` Update the assertions in `CatalogMysqlIT` / `CatalogOceanBaseIT` that pin the current wording, and cover the message in `TestJdbcDatabaseOperations`. -- 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]
