RockteMQ-AI commented on issue #10879: URL: https://github.com/apache/rocketmq/issues/10879#issuecomment-5229872913
**Issue Evaluation** Category: `type/bug` | Status: **Confirmed** The reported issue has been verified against the current codebase at commit `fd0c959`. **Root Cause:** `DefaultMetadataStore.updateTopic` refreshes the update timestamp on the currently stored metadata object, then replaces the map entry with the caller-provided `TopicMetadata`. When the caller supplies a distinct replacement object, the stored object keeps its stale timestamp. **Impact:** Topic metadata store — consumers relying on update timestamps for metadata freshness may read stale values after a topic update. **Severity:** medium The bug is in the metadata update logic where the timestamp refresh targets the wrong object reference. --- *Automated evaluation by github-manager-bot* -- 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]
