You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Rajesh Balamohan (JIRA)" <ji...@apache.org> on 2017/07/05 08:45:01 UTC
[jira] [Updated] (HIVE-17035) Optimizer: Lineage transform() should
be invoked after rest of the optimizers are invoked
[ https://issues.apache.org/jira/browse/HIVE-17035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rajesh Balamohan updated HIVE-17035:
------------------------------------
Assignee: Rajesh Balamohan
Status: Patch Available (was: Open)
> Optimizer: Lineage transform() should be invoked after rest of the optimizers are invoked
> -----------------------------------------------------------------------------------------
>
> Key: HIVE-17035
> URL: https://issues.apache.org/jira/browse/HIVE-17035
> Project: Hive
> Issue Type: Bug
> Components: Logical Optimizer
> Reporter: Rajesh Balamohan
> Assignee: Rajesh Balamohan
> Priority: Minor
> Attachments: HIVE-17035.1.patch
>
>
> In a fairly large query which had tens of left join, time taken to create linageInfo itself took 1500+ seconds. This is due to the fact that the table had lots of columns and in some processing, it ended up having 7000+ value columns in {{ReduceSinkLineage}}.
> It would be good to invoke lineage transform when rest of the optimizers in {{Optimizer}} are invoked. This would avoid help in improving the runtime.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)