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

Posted to issues@hive.apache.org by "Sergey Shelukhin (JIRA)" <ji...@apache.org> on 2016/05/05 01:47:12 UTC

[jira] [Updated] (HIVE-13449) LLAP: HS2 should get the token directly, rather than from LLAP

     [ https://issues.apache.org/jira/browse/HIVE-13449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sergey Shelukhin updated HIVE-13449:
------------------------------------
    Attachment: HIVE-13449.02.WIP.patch

Actually, since the LLAP tokens were scoped to the cluster, there is a problem - HS2 doesn't know the full LLAP cluster name including the appId; also the local and remote paths diverge enough to probably require separate APIs. For now, attaching the rebased WIP patch.



> LLAP: HS2 should get the token directly, rather than from LLAP
> --------------------------------------------------------------
>
>                 Key: HIVE-13449
>                 URL: https://issues.apache.org/jira/browse/HIVE-13449
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Sergey Shelukhin
>            Assignee: Sergey Shelukhin
>         Attachments: HIVE-13449.01.patch, HIVE-13449.02.WIP.patch, HIVE-13449.02.patch, HIVE-13449.patch
>
>
> HS2 doesn't need a roundtrip to LLAP; it can instantiate the SecretManager directly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)