yuqi1129 opened a new issue, #13923: URL: https://github.com/apache/gravitino/issues/13923
### Version main branch ### Describe what's wrong Creating a table in a StarRocks catalog with non-empty `indexes` succeeds, but the requested indexes are not created. The create response still includes those indexes, so it reports metadata that does not match the generated DDL. `StarRocksTableOperations.generateCreateTableSql` ignores its `indexes` argument, while `JdbcCatalogOperations.createTable` copies the requested indexes into the returned table. ### Error message and/or stacktrace No error is returned; the unsupported request succeeds silently. ### How to reproduce 1. Configure a StarRocks catalog and schema. 2. Create a table through the Gravitino API with valid columns and distribution, and include a non-empty `indexes` array, for example a `PRIMARY_KEY` on an `id` column. 3. Compare the indexes in the create response with the actual table definition in StarRocks. The requested index is returned but is absent from the generated CREATE TABLE SQL. ### Additional context The StarRocks catalog documentation already marks table indexes as unsupported. Reject non-empty index definitions before creating the table, with an error explaining that the caller must remove them. Requests without indexes should retain their existing behavior. -- 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]
