[
https://issues.apache.org/jira/browse/RANGER-3454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramesh Mani updated RANGER-3454:
--------------------------------
Description:
Hive command RELOAD FUNCTION failing in Ranger HiveAuthorization. This is due
to the check that was put in https://issues.apache.org/jira/browse/RANGER-3368.
To overcome this we need to have the previous behavior for RELOAD FUNCTION
which is not to authorized in Ranger. If there are authorization that needs to
be done in future, we can revisit Ranger HiveAuthorizer for enabling the
correct permission for this command and more over this doesn't possess any
security issue by not authorizing.
Command description from HIVE:
creating permanent functions in one Hive CLI session may not be reflected in
HiveServer2 or other Hive CLI sessions, if they were started before the
function was created. Issuing RELOAD FUNCTIONS within a HiveServer2 or HiveCLI
session will allow it to pick up any changes to the permanent functions that
may have been done by a different HiveCLI session. Due to backward
compatibility reasons RELOAD FUNCTION; is also accepted.
was:
Hive command REFRESH FUNCTION failing in Ranger HiveAuthorization. This is due
to the check that was put in https://issues.apache.org/jira/browse/RANGER-3368.
To overcome this we need to have the previous behavior for REFRESH FUNCTION
which is not to authorized in Ranger. If there are authorization that needs to
be done in future, we can revisit Ranger HiveAuthorizer for enabling the
correct permission for this command and more over this doesn't possess any
security issue by not authorizing.
Command description from HIVE:
creating permanent functions in one Hive CLI session may not be reflected in
HiveServer2 or other Hive CLI sessions, if they were started before the
function was created. Issuing RELOAD FUNCTIONS within a HiveServer2 or HiveCLI
session will allow it to pick up any changes to the permanent functions that
may have been done by a different HiveCLI session. Due to backward
compatibility reasons RELOAD FUNCTION; is also accepted.
> Hive command RELOAD FUNCTION failing in Ranger HiveAuthorization.
> -----------------------------------------------------------------
>
> Key: RANGER-3454
> URL: https://issues.apache.org/jira/browse/RANGER-3454
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
> Affects Versions: 3.0.0, 2.2.0
> Reporter: Ramesh Mani
> Priority: Minor
> Fix For: 3.0.0, 2.2.0
>
>
> Hive command RELOAD FUNCTION failing in Ranger HiveAuthorization. This is due
> to the check that was put in
> https://issues.apache.org/jira/browse/RANGER-3368.
> To overcome this we need to have the previous behavior for RELOAD FUNCTION
> which is not to authorized in Ranger. If there are authorization that needs
> to be done in future, we can revisit Ranger HiveAuthorizer for enabling the
> correct permission for this command and more over this doesn't possess any
> security issue by not authorizing.
>
> Command description from HIVE:
> creating permanent functions in one Hive CLI session may not be reflected in
> HiveServer2 or other Hive CLI sessions, if they were started before the
> function was created. Issuing RELOAD FUNCTIONS within a HiveServer2 or
> HiveCLI session will allow it to pick up any changes to the permanent
> functions that may have been done by a different HiveCLI session. Due to
> backward compatibility reasons RELOAD FUNCTION; is also accepted.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
