[jira] [Commented] (IMPALA-7553) Rework server_name across impalad and catalogd

["Vuk Ercegovac (JIRA)" <ji...@apache.org>]

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

Vuk Ercegovac commented on IMPALA-7553:
---------------------------------------

One idea here is to store it in hive-site.xml conf and let the impalad and catalogd servers pull it from there. That would at least move the setting from server flags to conf files and make the conf files setup more in-line with how HMS conf is setup.

Even with a setup like this, the confs that impalads and catalogd read may differ. Since catalogd sees this value from all impalad coordinators, it can warn if there is a misconfiguration.

An additional point to consider is that user-level SQL stmts that specify server name, for example, grant, should be re-examined to see if this level of flexibility is needed or is more likely to lead to inadvertent errors.

> Rework server_name across impalad and catalogd
> ----------------------------------------------
>
>                 Key: IMPALA-7553
>                 URL: https://issues.apache.org/jira/browse/IMPALA-7553
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Frontend
>    Affects Versions: Impala 3.1.0
>            Reporter: Adam Holley
>            Priority: Major
>
> The server_name is used by Impala to create privileges for sentry.  This is needed in both impalad and catalogd.  Currently this is not synchronized between impalad and catalogd and there is no enforcement to ensure the server_names are all the same.



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