[
https://issues.apache.org/jira/browse/RANGER-4719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17818785#comment-17818785
]
Himanshu Maurya commented on RANGER-4719:
-----------------------------------------
Hi [~madhan]
I have debugged this issue, fixed and validated
!Screenshot 2024-02-20 at 5.26.46 PM.png|width=702,height=424!
!image-2024-02-20-17-28-28-558.png|width=709,height=139!
!image-2024-02-20-17-39-05-432.png|width=707,height=146!
Kindly review and merge
Review board link :- [https://reviews.apache.org/r/74897/]
Thanks and Regards
> Policy condition expressions are split by the Ranger UI on commas
> ------------------------------------------------------------------
>
> Key: RANGER-4719
> URL: https://issues.apache.org/jira/browse/RANGER-4719
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
> Reporter: Himanshu Maurya
> Assignee: Himanshu Maurya
> Priority: Major
> Attachments: Screenshot 2024-02-15 at 5.07.02 PM.png, Screenshot
> 2024-02-15 at 5.20.36 PM.png, Screenshot 2024-02-15 at 5.27.54 PM.png,
> Screenshot 2024-02-20 at 5.26.46 PM.png, image-2024-02-20-17-28-17-767.png,
> image-2024-02-20-17-28-28-558.png, image-2024-02-20-17-39-05-432.png
>
>
> While using attributes with default values introduced in
> [RANGER-3997|https://issues.apache.org/jira/browse/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.
> !Screenshot 2024-02-15 at 5.07.02 PM.png|width=645,height=376!
>
> !Screenshot 2024-02-15 at 5.20.36 PM.png|width=645,height=112!
>
> !Screenshot 2024-02-15 at 5.27.54 PM.png|width=642,height=176!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
