[
https://issues.apache.org/jira/browse/IGNITE-18518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17724820#comment-17724820
]
Aleksandr Polovtcev commented on IGNITE-18518:
----------------------------------------------
LGTM!
> Sorted index scan may return obsolete row versions
> --------------------------------------------------
>
> Key: IGNITE-18518
> URL: https://issues.apache.org/jira/browse/IGNITE-18518
> Project: Ignite
> Issue Type: Bug
> Reporter: Ivan Bessonov
> Assignee: Semyon Danilov
> Priority: Major
> Labels: ignite-3
> Time Spent: 20m
> Remaining Estimate: 0h
>
> According to the MV store design, indexes must be filtered before returning
> data to user. For example, imagine that a row is deleted. This means that
> there's a tombstone.
> But, there's still an entry in indexes, for column values that the row used
> to have. These should not be visible to end user.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
