315157973 commented on pull request #10008: URL: https://github.com/apache/pulsar/pull/10008#issuecomment-812349412
This PR is a great feature, and we can later migrate other usage information from zk to here. So I have the above suggestions. Using `SystemTopic` is just a way, not our goal. Even if we do not use `SystemTopic`, I suggest other methods to achieve these goals: 1) No errors can be reported and no manual intervention is required. For example, if there is no data after a period of time, and it is deleted, a topic needs to be created manually. So hard to maintain. 2) Internal topics should be a reserved field, and it is better not be perceived by users. This is just my suggestion Here is an explanation of your question above: 1) SystemTopic allows automatic creation: `isAllowAutoTopicCreation(final TopicName topicName)` 2) Although SystemTopic is persistent, it is compressed topic, and the same key will only save the last one. I didn’t think deeply about the impact if the usage information is lost 3) We do not have a tenant-level policy now, and may need to be at the namespace level or topic level -- 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. For queries about this service, please contact Infrastructure at: [email protected]
