lizhimins commented on PR #4847: URL: https://github.com/apache/rocketmq-dashboard/pull/4847#issuecomment-6262596131
Thanks for the detailed write-up. Closing this one: the topic-type dispatch constraints (FIFO requires a message group, DELAY requires a future delivery timestamp, TRANSACTION is not sendable) are enforced by the broker/proxy itself, so we don't want a second copy of that policy living in Studio — it would drift from the server's real behaviour as soon as those rules change. If the goal is a clearer error in the console, the direction we'd take is surfacing the broker's rejection (mapping it to a readable message) rather than pre-validating in `MetadataService`. The AI tool handler keeps its contract text because it shapes the request before sending, not because it re-implements server policy. -- 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]
