[
https://issues.apache.org/jira/browse/IGNITE-20822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikita Amelchev updated IGNITE-20822:
-------------------------------------
Ignite Flags: (was: Docs Required,Release Notes Required)
> Refactoring WALIterator filter by higher bound
> ----------------------------------------------
>
> Key: IGNITE-20822
> URL: https://issues.apache.org/jira/browse/IGNITE-20822
> Project: Ignite
> Issue Type: Improvement
> Reporter: Maksim Timonin
> Assignee: Maksim Timonin
> Priority: Major
> Labels: ise
> Fix For: 2.17
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Currently filter by higher bound has different implementation in WAL iterator
> implementations:
> # Standalone filters by self. It has a little bug - one excess iteration
> over underlying iterator to check bounds.
> # RecordsIterator filters only by index of higherBound. It might be
> dangerous in concurrent scenario. It's better to filter by fixed position (as
> it guarantees that this part of segment is completed).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
