[
https://issues.apache.org/jira/browse/HIVE-16777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16027050#comment-16027050
]
Sergey Shelukhin edited comment on HIVE-16777 at 5/27/17 12:08 AM:
-------------------------------------------------------------------
+1 as a quick fix... however
1) it would be better to add field to the protocol promising single AM (or not,
as in case with external interface); relying on external flag itself is hacky
since, potentially, other clients could use external record reader from a
single "AM", allowing them to utilize the UGI pool.
2) also, the comment might not be correct w.r.t. it being temporary; even if
Spark thing uses a single port per instance, it can still have multiple spark
tasks for the same query as far as I understand. That would make this solution
permanent :)
was (Author: sershe):
+1 as a quick fix... however
1) it would be better to add field to the protocol promising single AM (or not,
as in case with external interface); relying on external flag itself is hacky.
2) also, the comment might not be correct w.r.t. it being temporary; even if
Spark thing uses a single port per instance, it can still have multiple spark
tasks for the same query as far as I understand. That would make this solution
permanent :)
> LLAP: Use separate tokens and UGI instances when an external client is used
> ---------------------------------------------------------------------------
>
> Key: HIVE-16777
> URL: https://issues.apache.org/jira/browse/HIVE-16777
> Project: Hive
> Issue Type: Bug
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Attachments: HIVE-16777.01.patch
>
>
> Otherwise leads to errors since the token is shared, and there's different
> nodes running Umbilical.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
