You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/11/26 10:35:00 UTC
[jira] [Commented] (KYLIN-3693) TopN, Count distinct incorrect in
Spark engine
[ https://issues.apache.org/jira/browse/KYLIN-3693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16698723#comment-16698723 ]
ASF subversion and git services commented on KYLIN-3693:
--------------------------------------------------------
Commit 1a7789cb5f01b22d6ca81fc28fc16e8d27c8e8c4 in kylin's branch refs/heads/2.5.x from shaofengshi
[ https://gitbox.apache.org/repos/asf?p=kylin.git;h=1a7789c ]
KYLIN-3693 TopN incorrect in Spark engine
> TopN, Count distinct incorrect in Spark engine
> ----------------------------------------------
>
> Key: KYLIN-3693
> URL: https://issues.apache.org/jira/browse/KYLIN-3693
> Project: Kylin
> Issue Type: Bug
> Components: Spark Engine
> Affects Versions: v2.5.0, v2.5.1
> Reporter: Shaofeng SHI
> Assignee: Shaofeng SHI
> Priority: Major
> Fix For: v2.5.2
>
>
> Long Chao firstly reported this bug; And then we found the currect integration test didn't cover this count distinct, topn measures with Spark engine. In "ITKylinQueryTest", some queries are not tested in the "left" join case, which means they were not covered the spark case. If we manually change to built the "left join" cube with spark, IT will report wrong result:
>
>
> {code:java}
> [ERROR] Failures:
> [ERROR] ITCombinationTest>ITKylinQueryTest.testPreciselyDistinctCountQuery:284->KylinTestBase.execAndCompQuery:544->KylinTestBase.execAndCompQuery:647->KylinTestBase.assertTableEquals:691 value (table=query result of query01, row=0, col=USER_COUNT) expected:<8[46]> but was:<8[52]>
> [ERROR] ITCombinationTest>ITKylinQueryTest.testTopNQuery:277->KylinTestBase.execAndCompQuery:544->KylinTestBase.execAndCompQuery:647->KylinTestBase.assertTableEquals:691 value (table=query result of query82, row=0, col=CAL_DT) expected:<2012-01-[28]> but was:<2012-01-[05]>
> [INFO]
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)