hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xuefu Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-21524) Impala Engine
Date Wed, 27 Mar 2019 17:07:00 GMT

    [ https://issues.apache.org/jira/browse/HIVE-21524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16803073#comment-16803073
] 

Xuefu Zhang commented on HIVE-21524:
------------------------------------

This sounds interesting. However, I'm trying to figure out what a user gains from this if
query is simply routed to Impala coordinator. As an alternative, a user can just connect the
client (ex. beeline) to Impala coordinator directly.

> Impala Engine
> -------------
>
>                 Key: HIVE-21524
>                 URL: https://issues.apache.org/jira/browse/HIVE-21524
>             Project: Hive
>          Issue Type: New Feature
>    Affects Versions: 4.0.0
>            Reporter: David Mollitor
>            Priority: Major
>
> Now that Impala has "dedicated coordinator" capability, it could be interesting to pair
HiveServer2 instances with Impala dedicated coordinators on the same localhost.  A client
could request an 'impala' execution engine and subsequent queries would be routed to the local
coordinator.
> {code:sql}
> set hive.execution.engine=impala;
> {code}
> This would allow clients seamless access to both capabilities without needing different
connections or drivers, Hive would also be a central location for auditing and authorization.
> https://www.cloudera.com/documentation/enterprise/latest/topics/impala_dedicated_coordinator.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message