[
https://issues.apache.org/jira/browse/RANGER-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15839002#comment-15839002
]
Yan commented on RANGER-1252:
-----------------------------
[~vperiasamy] Thanks for reviewing the patch. On the configuration side, I
think it's probably good to let the case sensitivity flag, as specified in the
ResourceDef in ServiceDef, to determine the case sensitivity check during the
search. Otherwise even a hit in search could not be useful to the user. A
bottom line is that the flag should serve as a single-point-of-truth for this
type of case-sensitivity-based searches. Please let me know your thoughts.
> Policy lookup does not honor the case sensitivity flag of resources
> -------------------------------------------------------------------
>
> Key: RANGER-1252
> URL: https://issues.apache.org/jira/browse/RANGER-1252
> Project: Ranger
> Issue Type: Bug
> Components: admin
> Affects Versions: 0.6.2
> Reporter: Yan
> Fix For: 0.7.0
>
> Attachments: Ranger-1252.patch
>
>
> For case insensitive Hive db/table names, the public API's policy lookup does
> not hit the case insensitive names. For instance, the following curl command:
> curl -iv -u admin:admin -H "Content-type:application/json" -X GET
> http://11.22.33.444:6080/service/public/api/policy?databases=db1&tables=table1
> returns different results from running the following command using different
> cases in names:
> curl -iv -u admin:admin -H "Content-type:application/json" -X GET
> http://11.22.33.444:6080/service/public/api/policy?databases=DB1&tables=TABLE1
> if there exists such a Hive table db1/table1 in the metastore.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
