[
https://issues.apache.org/jira/browse/HIVE-14392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Seth updated HIVE-14392:
----------------------------------
Attachment: HIVE-14392.01.patch
The ordering is as follows.
1. work.dirs specified - they will be used (except for a specific string value).
2. work.dirs not specified, or specific string value set - try using work dirs
from YARN container env.
3. Fail
Using the work dirs from the yarn container env gets rid of the problems with
having to setup explicit directories for secure clusters. YARN will take care
of setting up the base dirs for the llap app - which will operate within this
dir where it has access.
Containers running for apps which actually run the query (mode=map instead of
mode=ALL) - access the data via LLAP shuffle, which knows how to deal with
these dirs (noone outside of LLAP is accessing these dirs directly)
[~sershe], [~gopalv] - please review.
> llap daemons should try using YARN local dirs, if available
> -----------------------------------------------------------
>
> Key: HIVE-14392
> URL: https://issues.apache.org/jira/browse/HIVE-14392
> Project: Hive
> Issue Type: Improvement
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Attachments: HIVE-14392.01.patch
>
>
> LLAP required hive.llap.daemon.work.dirs to be specified. When running as a
> YARN app - this can use the local dirs for the container - removing the
> requirement to setup this parameter (for secure and non-secure clusters).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
