You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Ignite TC Bot (Jira)" <ji...@apache.org> on 2023/11/13 07:59:00 UTC

[jira] [Commented] (IGNITE-20822) Refactoring WALIterator filter by higher bound

    [ https://issues.apache.org/jira/browse/IGNITE-20822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17785399#comment-17785399 ] 

Ignite TC Bot commented on IGNITE-20822:
----------------------------------------

{panel:title=Branch: [pull/11034/head] Base: [master] : No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/11034/head] Base: [master] : No new tests found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--&gt; Run :: All* Results|https://ci2.ignite.apache.org/viewLog.html?buildId=7606677&amp;buildTypeId=IgniteTests24Java8_RunAll]

> 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
>          Time Spent: 0.5h
>  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)