You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hivemall.apache.org by "Takeshi Yamamuro (JIRA)" <ji...@apache.org> on 2018/04/01 21:53:00 UTC
[jira] [Commented] (HIVEMALL-183) Add an optimizer rule to prune
joins without significantly reducing ML accuracy
[ https://issues.apache.org/jira/browse/HIVEMALL-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16421824#comment-16421824 ]
Takeshi Yamamuro commented on HIVEMALL-183:
-------------------------------------------
Spark currently does not support FK constraints, so we need to track a Spark Jira ticket to support RIC functionalities in https://issues.apache.org/jira/browse/SPARK-19842
> Add an optimizer rule to prune joins without significantly reducing ML accuracy
> --------------------------------------------------------------------------------
>
> Key: HIVEMALL-183
> URL: https://issues.apache.org/jira/browse/HIVEMALL-183
> Project: Hivemall
> Issue Type: Sub-task
> Reporter: Takeshi Yamamuro
> Assignee: Takeshi Yamamuro
> Priority: Major
> Labels: spark
>
> An objective of this ticket is to implement the proposed technique in the paper [1] below;
> [1] Arun Kumar, Jeffrey Naughton, Jignesh M. Patel, and Xiaojin Zhu, To Join or Not to Join?: Thinking Twice about Joins before Feature Selection, Proceedings of SIGMOD, 2016.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)