X-LightYear opened a new issue, #7204: URL: https://github.com/apache/rocketmq-dashboard/issues/7204
## Problem The `rmq.litetopic.extend_ttl` MCP mutation tool reports the requested TTL, but not the TTL that the broker actually applies. The Apache provider rounds TTL values to whole minutes and clamps them to the 30-day protocol maximum. For example, a request for 31 days is applied as 30 days, while the tool result still only echoes the requested value. This leaves an operator or MCP planner unable to determine the effective broker configuration from a successful mutation response. ## Expected behavior The mutation result should retain the requested TTL and also report the broker-normalized TTL that was applied after rounding and the protocol maximum. ## Scope Add `appliedTtlMillis` to the MCP result, propagate the value from the provider through the service and handler, and document it in the tool catalog. The REST endpoint remains unchanged. ## Testing - `LiteTopicExtendTtlToolHandlerTest` verifies requested and applied values are both returned. - `RocketMQLiteTopicProviderTest` verifies minute conversion and the 30-day clamp. - `ToolOutputSchemaContractTest` verifies the catalog result schema. -- 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]
