You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/09/24 20:53:00 UTC
[jira] [Commented] (IMPALA-589) add sql function to return the
impalad coordinator hostname
[ https://issues.apache.org/jira/browse/IMPALA-589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626453#comment-16626453 ]
ASF subversion and git services commented on IMPALA-589:
--------------------------------------------------------
Commit 15e40a3c9407e5f3d9cf44bfd270b2c4bbc842e9 in impala's branch refs/heads/master from [~asherman]
[ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=15e40a3 ]
IMPALA-589: Add sql function returning the impalad coordinator hostname.
In every execution of an Impala query, one of the impalad daemons acts
as the coordinator node. In some cases, such as when using a proxy, a
user cannot predict which host will act as the coordinator. To aid in
diagnosis, we provide a sql function which returns the name of the host
on which the coordinator is running.
EXTERNAL DESCRIPTION:
Add a builtin function called coordinator(), which returns the name of
the host which is running the impalad that is acting as the coordinator
for the current query.
TESTING:
- Added a basic unit test for the new function.
- Added a unit test which simulates the case when coord_address is
unset.
- Added a query that uses coordinator() to exprs.test
- Hand tested in a development deployment.
- Ran regression tests and got a clean run.
Change-Id: I94d6e2664ba659b48df53c5c06f67b502c533e47
Reviewed-on: http://gerrit.cloudera.org:8080/11459
Reviewed-by: Thomas Marshall <th...@cmu.edu>
Tested-by: Impala Public Jenkins <im...@cloudera.com>
> add sql function to return the impalad coordinator hostname
> -----------------------------------------------------------
>
> Key: IMPALA-589
> URL: https://issues.apache.org/jira/browse/IMPALA-589
> Project: IMPALA
> Issue Type: New Feature
> Components: Frontend
> Affects Versions: Impala 1.1.1
> Reporter: Greg Rahn
> Assignee: Andrew Sherman
> Priority: Minor
> Labels: built-in-function, newbie
>
> When using a proxy, etc. there isnt a way for a client to know what impalad it is connected to. Adding a sql function to return this value would prove useful.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org