hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chaoyu Tang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-12812) Enable mapred.input.dir.recursive by default to support union with aggregate function
Date Fri, 21 Sep 2018 19:18:00 GMT

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

Chaoyu Tang commented on HIVE-12812:
------------------------------------

I could not remember the exact reason why this patch was not be committed years ago. It might
probably be that we were going to decommission the MR soon and there was a regression in one
test case. But as a workaround, you can always set the property to true on the command (not
necessary in hive-site.xml):
set mapred.input.dir.recursive=true

> Enable mapred.input.dir.recursive by default to support union with aggregate function
> -------------------------------------------------------------------------------------
>
>                 Key: HIVE-12812
>                 URL: https://issues.apache.org/jira/browse/HIVE-12812
>             Project: Hive
>          Issue Type: Bug
>          Components: Hive
>    Affects Versions: 1.2.1, 2.1.0
>            Reporter: Chaoyu Tang
>            Priority: Major
>         Attachments: HIVE-12812.patch, HIVE-12812.patch, HIVE-12812.patch
>
>
> When union remove optimization is enabled, union query with aggregate function writes
its subquery intermediate results to subdirs which needs mapred.input.dir.recursive to be
enabled in order to be fetched. This property is not defined by default in Hive and often
ignored by user, which causes the query failure and is hard to be debugged.
> So we need set mapred.input.dir.recursive to true whenever union remove optimization
is enabled.



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

Mime
View raw message