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

Posted to issues@ignite.apache.org by "Ivan Bessonov (Jira)" <ji...@apache.org> on 2020/12/02 12:47:00 UTC

[jira] [Commented] (IGNITE-11998) Fix DataPageScan for fragmented pages.

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

Ivan Bessonov commented on IGNITE-11998:
----------------------------------------

Hi [~mmuzaf], just found out that this issue is on you now.

DataPageScan optimization was disabled as a part of https://issues.apache.org/jira/browse/IGNITE-11982. It comes with a bunch of other fixes, which sucks. But you can still use it as a reference, many of those changes must be reapplied back.

BTW, what's your plan? How are you going to fix it?

> Fix DataPageScan for fragmented pages.
> --------------------------------------
>
>                 Key: IGNITE-11998
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11998
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Ivan Bessonov
>            Assignee: Maxim Muzafarov
>            Priority: Critical
>             Fix For: 2.10
>
>
> Fragmented pages crash JVM when accessed by DataPageScan scanner/query optimized scanner. It happens when scanner accesses data in later chunk in fragmented entry but treats it like the first one, expecting length of the payload, which is absent and replaced with raw entry data.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)