[
https://issues.apache.org/jira/browse/HIVE-12812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16622768#comment-16622768
]
Alice Fan commented on HIVE-12812:
----------------------------------
Hi [~ctang.ma], [~kgyrtkirk],
Do we still want to complete the patch here for the ticket ?
By default, FileInputFormat of mapreduce project set INPUT_DIR_RECURSIVE =
false. It still caused the issue like
[HIVE-20319|https://issues.apache.org/jira/browse/HIVE-20319] when user turn on
hive.optimize.union.remove. Is there any concerns not to make the change here?
> 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)
