roryqi commented on code in PR #13469: URL: https://github.com/apache/gravitino/pull/13469#discussion_r4079989498
########## docs/kafka-catalog.md: ########## @@ -48,6 +48,18 @@ Refer to [Schema operation](./manage-messaging-metadata-using-gravitino.md#schem - The Kafka catalog supports creating, updating, deleting, and listing topics. +::::caution Topic names containing dots +When authorization is enabled, Gravitino cannot authorize a topic whose name contains a dot (`.`), +because dots separate the components of a qualified metadata object name. Loading such a topic +returns `400 Bad Request`. If a Kafka cluster contains one of these topics, Gravitino rejects the +entire topic list request with `400 Bad Request` and identifies the unsupported name instead of +returning a partial result. Consequently, one topic with a dotted name can prevent every topic in the +schema from appearing in list APIs and Explore. Review Comment: Good point. "Explore" referred to an enterprise UI concept and does not belong in the Apache documentation. I removed it and now describe the impact only in terms of list APIs. ########## docs/kafka-catalog.md: ########## @@ -48,6 +48,18 @@ Refer to [Schema operation](./manage-messaging-metadata-using-gravitino.md#schem - The Kafka catalog supports creating, updating, deleting, and listing topics. +::::caution Topic names containing dots Review Comment: Agreed. I moved the general limitation to the Access Control documentation and kept only a short Kafka-specific caution that links to it, since dotted names are especially common for Kafka topics. -- 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]
