fix(wal): filter inner trim record for range get

[superhx]

No description provided.

[Copilot]

Pull Request Overview

This PR fixes a bug where trim marker records were incorrectly included in range query results from the Write-Ahead Log (WAL). The fix filters out internal trim records during batch reads to prevent them from being returned to users.

• Adds filtering logic to skip trim marker records (identified by streamId == -1L, epoch == -1L, and count == 0) during batch range reads
• Adds a test case to verify trim records are correctly filtered when reading across a range that includes a trim marker
• Suppresses cyclomatic complexity warnings for the modified method

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
DefaultReader.java	Added logic to detect and filter out trim marker records during batch reads
ObjectWALServiceTest.java	Added test case to verify trim records are excluded from range query results

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The trim record detection logic is duplicated across the codebase. In RecoverIterator.java line 154, a similar check exists but only checks streamId == -1L && epoch == -1L, omitting the count == 0 check. Consider extracting this logic into a utility method (e.g., ObjectUtils.isTrimRecord()) to ensure consistency and maintainability across all trim record checks.

Suggested change

	boolean isTriggerTrimRecord = batch.getCount() == 0 && batch.getStreamId() == -1L && batch.getEpoch() == -1L;
	boolean isTriggerTrimRecord = ObjectUtils.isTrimRecord(batch);

[Copilot]

The cyclomatic complexity suppression is applied at the class level, which disables the check for all methods in the class. Consider applying this suppression more narrowly at the method level (e.g., on doRunBatchGet0 method) to maintain complexity checks for other methods.