hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jesus Camacho Rodriguez (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HIVE-21395) Refactor HiveSemiJoinRule
Date Mon, 25 Mar 2019 23:29:00 GMT

    [ https://issues.apache.org/jira/browse/HIVE-21395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16801232#comment-16801232
] 

Jesus Camacho Rodriguez edited comment on HIVE-21395 at 3/25/19 11:28 PM:
--------------------------------------------------------------------------

[~vgarg], patch LGTM. However, can you remove {{some}} from the operand matching? Aggregate
or Project operators have a single inputs, thus it is not needed.


was (Author: jcamachorodriguez):
[~vgarg], patch LGTM. However, can you remove {{some}} from the operand matching? Aggregate
has a single input, thus it is not needed.

> Refactor HiveSemiJoinRule
> -------------------------
>
>                 Key: HIVE-21395
>                 URL: https://issues.apache.org/jira/browse/HIVE-21395
>             Project: Hive
>          Issue Type: Improvement
>          Components: Query Planning
>    Affects Versions: 4.0.0
>            Reporter: Vineet Garg
>            Assignee: Vineet Garg
>            Priority: Major
>         Attachments: HIVE-21395.1.patch
>
>
> Following refactoring needs to be done:
> * Update the rule matching pattern to avoid using HepVertex
> * HIVE-21338 adds logic to determine if rel plan will produce at most one row. Use this
in HiveSemiJoinRule



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message