Description
While using attributes with default values introduced in RANGER-3997 like GET_USER_ATTR('state', 'null') in policy condition.
It is observed that ranger is splitting condition string in to 2 parts separated by comma of the parameters passed to GET_USER_ATTR(), due to this it is not taking default value and conditions are converted to invalid strings.
Kindly refer to screenshots attached below.
Attachments
Attachments
Issue Links
- is required by
-
RANGER-3997 option to use default value when user/group/tag does not have the attribute
-
- Resolved
-