You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hivemall.apache.org by "Makoto Yui (JIRA)" <ji...@apache.org> on 2017/11/08 07:53:01 UTC
[jira] [Updated] (HIVEMALL-76) [SPARK] each_top_k behavior on Spark
is wrong
[ https://issues.apache.org/jira/browse/HIVEMALL-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Makoto Yui updated HIVEMALL-76:
-------------------------------
Fix Version/s: 0.5.0
> [SPARK] each_top_k behavior on Spark is wrong
> ---------------------------------------------
>
> Key: HIVEMALL-76
> URL: https://issues.apache.org/jira/browse/HIVEMALL-76
> Project: Hivemall
> Issue Type: Bug
> Reporter: Makoto Yui
> Assignee: Takeshi Yamamuro
> Fix For: 0.5.0
>
>
> I found that each_top_k behavior on Spark is little bit difference one from Hive for the ranking scheme in
> https://github.com/apache/incubator-hivemall/blob/master/core/src/main/java/hivemall/tools/EachTopKUDTF.java#L198
> Hive provides a dense_rank but Spark does not.
> https://github.com/apache/incubator-hivemall/blob/72d6a629f972abc2f38c63d20fe5c978618f8bf8/spark/spark-2.0/src/main/scala/org/apache/spark/sql/catalyst/expressions/EachTopK.scala#L101
> Better to return a same rank where compared score is same.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)