hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pengcheng Xiong (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HIVE-15399) Parser change for UniqueJoin
Date Thu, 22 Dec 2016 00:57:58 GMT

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

Pengcheng Xiong edited comment on HIVE-15399 at 12/22/16 12:57 AM:
-------------------------------------------------------------------

included in HIVE-15200


was (Author: pxiong):
included in HIVE-15220

> Parser change for UniqueJoin
> ----------------------------
>
>                 Key: HIVE-15399
>                 URL: https://issues.apache.org/jira/browse/HIVE-15399
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Pengcheng Xiong
>            Assignee: Pengcheng Xiong
>         Attachments: HIVE-15399.01.patch
>
>
> UniqueJoin was introduced in HIVE-591. Add Unique Join. (Emil Ibrishimov via namit).
It sounds like that there is only one q test for unique join, i.e., uniquejoin.q. In the q
test, unique join source can only come from a table. However, in parser, its source can come
from not only tableSource, but also
> {code}
> partitionedTableFunction | tableSource | subQuerySource | virtualTableSource
> {code}
> I think it would be better to change the parser and limit it to meet the user's real
requirement.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message