RockteMQ-AI commented on issue #10656: URL: https://github.com/apache/rocketmq/issues/10656#issuecomment-5061222771
**Issue Evaluation** Category: `type/bug` | Status: **Confirmed** The reported issue has been verified against the current codebase. **Root Cause:** In `IndexStoreFile.java` line 117, the recovery constructor reads `endTimestamp` from `INDEX_BEGIN_TIME_STAMP` (offset 4) instead of `INDEX_END_TIME_STAMP` (offset 12). The write path (lines 192-193) correctly stores `endTimestamp` at `INDEX_END_TIME_STAMP`, so the recovery read is inconsistent with the write. **Impact:** After reopening a tiered index file, `endTimestamp` equals `beginTimestamp`, causing valid query results within the time range to be skipped during index lookups. **Severity:** Medium — data query correctness issue in the tiered store index layer. **Fix:** PR #10657 addresses this with a one-line fix and includes a regression test. --- *Automated evaluation by RockteMQ-AI* -- 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]
