You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Shaofeng SHI (JIRA)" <ji...@apache.org> on 2017/11/05 09:31:00 UTC

[jira] [Updated] (KYLIN-2926) DumpMerger return incorrect results

     [ https://issues.apache.org/jira/browse/KYLIN-2926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Shaofeng SHI updated KYLIN-2926:
--------------------------------
    Fix Version/s: v2.2.0
      Component/s: Query Engine

> DumpMerger return incorrect results
> -----------------------------------
>
>                 Key: KYLIN-2926
>                 URL: https://issues.apache.org/jira/browse/KYLIN-2926
>             Project: Kylin
>          Issue Type: Bug
>          Components: Query Engine
>    Affects Versions: v2.0.0
>            Reporter: fengYu
>            Assignee: fengYu
>             Fix For: v2.2.0
>
>         Attachments: 0001-KYLIN-2926-DumpMerger-return-incorrect-results-creat.patch
>
>
> I our scenario, a cube query will get wrong result once coprocessor need to spill to disk, Our version is 2.0.0 and I find the root cause is that in DumpMerger.enqueueFromDump
> because in DataTypeSerializer kylin use a ThreadLocal variable ‘current’, It leading to different elements in dumpCurrentValues share the same object, so next fill up measure values will change the existing values. 
> the incorrect measures is HLLC and raw, which use current variable in deserialize.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)