You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Jason Dere (JIRA)" <ji...@apache.org> on 2016/03/30 23:23:25 UTC

[jira] [Updated] (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:all-tabpanel ]

Jason Dere updated HIVE-13389:
------------------------------
    Attachment: HIVE-13389.1-llap.patch

- Allow LlapZkRegistry to get the user via the conf, if it is set.
- Change LlapInputSplit to include the LLAP user. LlapInputFormat.getRecordReader() now sets the conf with this user name prior to instantiating the external client.

> 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
>         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)