[
https://issues.apache.org/jira/browse/KYLIN-2926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fengYu updated KYLIN-2926:
--------------------------
Description:
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.
was:
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.
> DumpMerger return incorrect results
> -----------------------------------
>
> Key: KYLIN-2926
> URL: https://issues.apache.org/jira/browse/KYLIN-2926
> Project: Kylin
> Issue Type: Bug
> Affects Versions: v2.0.0
> Reporter: fengYu
> Assignee: fengYu
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
