You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Lefty Leverenz (JIRA)" <ji...@apache.org> on 2016/03/31 09:08:25 UTC
[jira] [Commented] (HIVE-13389) LLAP external submission client
ends up attempting to find an LLAP instance based on the submitting user
instead of the hive user
[ https://issues.apache.org/jira/browse/HIVE-13389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219489#comment-15219489 ]
Lefty Leverenz commented on HIVE-13389:
---------------------------------------
Doc note: This adds *hive.llap.zk.registry.user* to HiveConf.java, so it will need to be documented in the wiki when this gets merged to master.
We don't use a TODOC-LLAP label, but see HIVE-9850 for other post-2.0.0 llap configuration parameters:
* [post-2.0.0 doc note for llap | https://issues.apache.org/jira/browse/HIVE-9850?focusedCommentId=15162758&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15162758]
> LLAP external submission client ends up attempting to find an LLAP instance based on the submitting user instead of the hive user
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: HIVE-13389
> URL: https://issues.apache.org/jira/browse/HIVE-13389
> Project: Hive
> Issue Type: Sub-task
> Components: llap
> Reporter: Jason Dere
> Assignee: Jason Dere
> Fix For: llap
>
> Attachments: HIVE-13389.1-llap.patch
>
>
> In the LLAP external client, the LLAP Zookeeper registry creates the Zk path based on the current user, but the user specified here should really be the user running LLAP.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)