You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Madhan Neethiraj (Jira)" <ji...@apache.org> on 2020/08/09 17:50:00 UTC

[jira] [Assigned] (RANGER-2945) Need to check if RANGER_LOGIN_PASSWORD exists in HadoopConfigHolder

     [ https://issues.apache.org/jira/browse/RANGER-2945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Madhan Neethiraj reassigned RANGER-2945:
----------------------------------------

    Assignee: Jiayi Liu

> Need to check if RANGER_LOGIN_PASSWORD exists in HadoopConfigHolder
> -------------------------------------------------------------------
>
>                 Key: RANGER-2945
>                 URL: https://issues.apache.org/jira/browse/RANGER-2945
>             Project: Ranger
>          Issue Type: Bug
>          Components: plugins
>            Reporter: Jiayi Liu
>            Assignee: Jiayi Liu
>            Priority: Major
>             Fix For: 2.1.0, 3.0.0
>
>         Attachments: 0001-RANGER-2945.patch, 0002-RANGER-2945.patch
>
>
> Since Presto service allows not to set password, when constructing {{HadoopConfigHolder}}, we need to check whether {{RANGER_LOGIN_PASSWORD}} is set. If it is not set, we need to set it to null in connectionProperties in order to make the password in dataSource2HadoopConfigHolder be updated. Otherwise, when we set the password in the Presto service, the static variable {{dataSource2HadoopConfigHolder}} will store the password. If we change the password in the Presto service to empty, if we do not check the {{RANGER_LOGIN_PASSWORD}}, the old password stored in {{dataSource2HadoopConfigHolder}} will never be updated, causing the presto client connection to fail.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)