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 "Ruslan Dautkhanov (JIRA)" <ji...@apache.org> on 2018/10/29 16:51:00 UTC
[jira] [Commented] (IMPALA-6042) Allow Impala shell to also use a
global impalarc configuration
[ https://issues.apache.org/jira/browse/IMPALA-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16667434#comment-16667434 ]
Ruslan Dautkhanov commented on IMPALA-6042:
-------------------------------------------
Another use case is to update PATH variable, to point to a Python2 home for example.
As impala-shell is not Python3-compatible (IMPALA-3343) and we're migrating all our applications to Python 3.
It would be great to have a way to globally update certain config variables and environment variables like PATHÂ
to have a workaround for this and some other issues.
Thank you.
> Allow Impala shell to also use a global impalarc configuration
> --------------------------------------------------------------
>
> Key: IMPALA-6042
> URL: https://issues.apache.org/jira/browse/IMPALA-6042
> Project: IMPALA
> Issue Type: Improvement
> Components: Clients
> Reporter: Balazs Jeszenszky
> Priority: Minor
> Labels: newbie, shell, usability
>
> Currently, impalarc files can be specified on a per-user basis (stored in ~/.impalarc), and they aren't created by default.
> The Impala shell should pick up /etc/impalarc as well, in addition to the user-specific configurations.
> The intent here is to allow a "global" configuration of the shell by a system administrator with common options like:
> {code}
> --ssl
> -l
> -k
> -u <current_user>
> -i <impala>
> {code}
--
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