rameeshm commented on code in PR #1220:
URL: https://github.com/apache/ranger/pull/1220#discussion_r3972999212
##########
agents-common/src/main/resources/service-defs/ranger-servicedef-hive.json:
##########
@@ -198,7 +198,7 @@
],
"resources": [
{ "name": "database", "matcherOptions": { "wildCard": "false" },
"lookupSupported": true, "mandatory": true, "uiHint": "{ \"singleValue\":true
}" },
- { "name": "table", "matcherOptions": { "wildCard": "false" },
"lookupSupported": true, "mandatory": true, "uiHint": "{ \"singleValue\":true
}" }
+ { "name": "table", "matcherOptions": { "wildCard": "true" },
"lookupSupported": true, "mandatory": true, "uiHint": "" }
Review Comment:
@rgupta94 Ranger has a functionality of not to allow insert/update of table
which has rowfilter / column masking in it and this will present the users from
insert / update of the table in the database. Please check it out. There is a
check in isBlockAccessIfRowfilterColumnMaskSpecified in RangerHiveAuthorizer
which cause this issue. May be we should document this say that "applying a
wildcard row filter will trigger
RangerHivePlugin.blockUpdateIfRowfilterColumnMaskSpecified, effectively
blocking all UPDATE/ALTER commands for that user across the entire database.
Users should be advised to apply these wildcard policies strictly to Read-Only
roles or disable the property in ranger-hive-security.xml." Also add some test
cases for this in Hive Plugin. CC @mneethiraj
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
