[jira] [Created] (RANGER-4092) [Ranger UI] [React JS] Showing multiple msg prompts for multiple user visibility toggle with same msg.
Kundan Kumar Jha created RANGER-4092:
Summary: [Ranger UI] [React JS] Showing multiple msg prompts for
multiple user visibility toggle with same msg.
Key: RANGER-4092
URL: https://issues.apache.org/jira/browse/RANGER-4092
Project: Ranger
Issue Type: Bug
Components: Ranger
Reporter: Kundan Kumar Jha
Behaviour in React UI:
Showing multiple success/failure msg prompts for multiple user visibility
toggle with same msg.
Behaviour in Backbone JS UI:
Shows a dialog box once with users already visible or already hidden if all the
selected users are in the state which it was supposed to acquire.
Expected behaviour:
Either it shows the combine one status that user is already hidden or visible
as in already present UI.
Or
If shows individual popups then show with name for eg. "Selected user
\{user_name} is already hidden or visible" instead of just showing "Selected
user is already hidden or visible".
Steps to reproduce:
# Create 4 users user_1, user_2, user_3, user_4 in ranger.
# Then in users table of users page in ranger UI select those 4 users.
# Then from set visibility dropdown select visible.
# 4 popups can be seen in the right side of page with same msg as "Selected
user is already visible". And none of the popup contains the name of the user
to which it was concerned to.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4092) [Ranger UI] [React JS] Showing multiple msg prompts for multiple user visibility toggle with same msg.
[
https://issues.apache.org/jira/browse/RANGER-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kundan Kumar Jha updated RANGER-4092:
-
Attachment: Screenshot 2023-02-16 at 8.36.52 PM.png
> [Ranger UI] [React JS] Showing multiple msg prompts for multiple user
> visibility toggle with same msg.
> --
>
> Key: RANGER-4092
> URL: https://issues.apache.org/jira/browse/RANGER-4092
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Kundan Kumar Jha
>Priority: Major
> Attachments: Screenshot 2023-02-16 at 8.36.52 PM.png
>
>
> Behaviour in React UI:
> Showing multiple success/failure msg prompts for multiple user visibility
> toggle with same msg.
> Behaviour in Backbone JS UI:
> Shows a dialog box once with users already visible or already hidden if all
> the selected users are in the state which it was supposed to acquire.
> Expected behaviour:
> Either it shows the combine one status that user is already hidden or visible
> as in already present UI.
> Or
> If shows individual popups then show with name for eg. "Selected user
> \{user_name} is already hidden or visible" instead of just showing "Selected
> user is already hidden or visible".
>
> Steps to reproduce:
> # Create 4 users user_1, user_2, user_3, user_4 in ranger.
> # Then in users table of users page in ranger UI select those 4 users.
> # Then from set visibility dropdown select visible.
> # 4 popups can be seen in the right side of page with same msg as "Selected
> user is already visible". And none of the popup contains the name of the user
> to which it was concerned to.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4092) [Ranger UI] [React JS] Showing multiple msg prompts for multiple user/groups visibility toggle with same msg.
[
https://issues.apache.org/jira/browse/RANGER-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kundan Kumar Jha updated RANGER-4092:
-
Summary: [Ranger UI] [React JS] Showing multiple msg prompts for multiple
user/groups visibility toggle with same msg. (was: [Ranger UI] [React JS]
Showing multiple msg prompts for multiple user visibility toggle with same msg.)
> [Ranger UI] [React JS] Showing multiple msg prompts for multiple user/groups
> visibility toggle with same msg.
> -
>
> Key: RANGER-4092
> URL: https://issues.apache.org/jira/browse/RANGER-4092
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Kundan Kumar Jha
>Priority: Major
> Attachments: Screenshot 2023-02-16 at 8.36.52 PM.png
>
>
> Behaviour in React UI:
> Showing multiple success/failure msg prompts for multiple user visibility
> toggle with same msg.
> Behaviour in Backbone JS UI:
> Shows a dialog box once with users already visible or already hidden if all
> the selected users are in the state which it was supposed to acquire.
> Expected behaviour:
> Either it shows the combine one status that user is already hidden or visible
> as in already present UI.
> Or
> If shows individual popups then show with name for eg. "Selected user
> \{user_name} is already hidden or visible" instead of just showing "Selected
> user is already hidden or visible".
>
> Steps to reproduce:
> # Create 4 users user_1, user_2, user_3, user_4 in ranger.
> # Then in users table of users page in ranger UI select those 4 users.
> # Then from set visibility dropdown select visible.
> # 4 popups can be seen in the right side of page with same msg as "Selected
> user is already visible". And none of the popup contains the name of the user
> to which it was concerned to.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4092) [Ranger UI] [React JS] Showing multiple msg prompts for multiple users/groups visibility toggle with same msg.
[
https://issues.apache.org/jira/browse/RANGER-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kundan Kumar Jha updated RANGER-4092:
-
Summary: [Ranger UI] [React JS] Showing multiple msg prompts for multiple
users/groups visibility toggle with same msg. (was: [Ranger UI] [React JS]
Showing multiple msg prompts for multiple user/groups visibility toggle with
same msg.)
> [Ranger UI] [React JS] Showing multiple msg prompts for multiple users/groups
> visibility toggle with same msg.
> --
>
> Key: RANGER-4092
> URL: https://issues.apache.org/jira/browse/RANGER-4092
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Kundan Kumar Jha
>Priority: Major
> Attachments: Screenshot 2023-02-16 at 8.36.52 PM.png
>
>
> Behaviour in React UI:
> Showing multiple success/failure msg prompts for multiple user visibility
> toggle with same msg.
> Behaviour in Backbone JS UI:
> Shows a dialog box once with users already visible or already hidden if all
> the selected users are in the state which it was supposed to acquire.
> Expected behaviour:
> Either it shows the combine one status that user is already hidden or visible
> as in already present UI.
> Or
> If shows individual popups then show with name for eg. "Selected user
> \{user_name} is already hidden or visible" instead of just showing "Selected
> user is already hidden or visible".
>
> Steps to reproduce:
> # Create 4 users user_1, user_2, user_3, user_4 in ranger.
> # Then in users table of users page in ranger UI select those 4 users.
> # Then from set visibility dropdown select visible.
> # 4 popups can be seen in the right side of page with same msg as "Selected
> user is already visible". And none of the popup contains the name of the user
> to which it was concerned to.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4092) [Ranger UI] [React JS] Showing multiple msg prompts for multiple users/groups visibility toggle with same msg.
[
https://issues.apache.org/jira/browse/RANGER-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kundan Kumar Jha updated RANGER-4092:
-
Description:
Behaviour in React UI:
Showing multiple success/failure msg prompts for multiple users/groups
visibility toggle with same msg.
Behaviour in Backbone JS UI:
Shows a dialog box once with users/groups already visible or already hidden if
all the selected users/groups are in the state which it was supposed to acquire.
Expected behaviour:
Either it shows the combine one status that users/groups are already hidden or
visible as in already present UI.
Or
If shows individual popups then show with name for eg.
For users: "Selected user \{user_name} is already hidden or visible" instead of
just showing "Selected user is already hidden or visible".
For groups: "Selected groups group_name} is already hidden or visible" instead
of just showing "Selected group is already hidden or visible".
Steps to reproduce:
# Create 4 users user_1, user_2, user_3, user_4 in ranger.
# Then in users table of users page in ranger UI select those 4 users.
# Then from set visibility dropdown select visible.
# 4 popups can be seen in the right side of page with same msg as "Selected
user is already visible". And none of the popup contains the name of the user
to which it was concerned to.
was:
Behaviour in React UI:
Showing multiple success/failure msg prompts for multiple user visibility
toggle with same msg.
Behaviour in Backbone JS UI:
Shows a dialog box once with users already visible or already hidden if all the
selected users are in the state which it was supposed to acquire.
Expected behaviour:
Either it shows the combine one status that user is already hidden or visible
as in already present UI.
Or
If shows individual popups then show with name for eg. "Selected user
\{user_name} is already hidden or visible" instead of just showing "Selected
user is already hidden or visible".
Steps to reproduce:
# Create 4 users user_1, user_2, user_3, user_4 in ranger.
# Then in users table of users page in ranger UI select those 4 users.
# Then from set visibility dropdown select visible.
# 4 popups can be seen in the right side of page with same msg as "Selected
user is already visible". And none of the popup contains the name of the user
to which it was concerned to.
> [Ranger UI] [React JS] Showing multiple msg prompts for multiple users/groups
> visibility toggle with same msg.
> --
>
> Key: RANGER-4092
> URL: https://issues.apache.org/jira/browse/RANGER-4092
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Kundan Kumar Jha
>Priority: Major
> Attachments: Screenshot 2023-02-16 at 8.36.52 PM.png
>
>
> Behaviour in React UI:
> Showing multiple success/failure msg prompts for multiple users/groups
> visibility toggle with same msg.
> Behaviour in Backbone JS UI:
> Shows a dialog box once with users/groups already visible or already hidden
> if all the selected users/groups are in the state which it was supposed to
> acquire.
> Expected behaviour:
> Either it shows the combine one status that users/groups are already hidden
> or visible as in already present UI.
> Or
> If shows individual popups then show with name for eg.
> For users: "Selected user \{user_name} is already hidden or visible" instead
> of just showing "Selected user is already hidden or visible".
> For groups: "Selected groups group_name} is already hidden or visible"
> instead of just showing "Selected group is already hidden or visible".
>
> Steps to reproduce:
> # Create 4 users user_1, user_2, user_3, user_4 in ranger.
> # Then in users table of users page in ranger UI select those 4 users.
> # Then from set visibility dropdown select visible.
> # 4 popups can be seen in the right side of page with same msg as "Selected
> user is already visible". And none of the popup contains the name of the user
> to which it was concerned to.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4092) [Ranger UI] [React JS] Showing multiple msg prompts for multiple users/groups visibility toggle with same msg.
[
https://issues.apache.org/jira/browse/RANGER-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kundan Kumar Jha updated RANGER-4092:
-
Attachment: Screenshot 2023-02-16 at 8.44.48 PM.png
> [Ranger UI] [React JS] Showing multiple msg prompts for multiple users/groups
> visibility toggle with same msg.
> --
>
> Key: RANGER-4092
> URL: https://issues.apache.org/jira/browse/RANGER-4092
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Kundan Kumar Jha
>Priority: Major
> Attachments: Screenshot 2023-02-16 at 8.36.52 PM.png, Screenshot
> 2023-02-16 at 8.44.48 PM.png
>
>
> Behaviour in React UI:
> Showing multiple success/failure msg prompts for multiple users/groups
> visibility toggle with same msg.
> Behaviour in Backbone JS UI:
> Shows a dialog box once with users/groups already visible or already hidden
> if all the selected users/groups are in the state which it was supposed to
> acquire.
> Expected behaviour:
> Either it shows the combine one status that users/groups are already hidden
> or visible as in already present UI.
> Or
> If shows individual popups then show with name for eg.
> For users: "Selected user \{user_name} is already hidden or visible" instead
> of just showing "Selected user is already hidden or visible".
> For groups: "Selected groups group_name} is already hidden or visible"
> instead of just showing "Selected group is already hidden or visible".
>
> Steps to reproduce:
> # Create 4 users user_1, user_2, user_3, user_4 in ranger.
> # Then in users table of users page in ranger UI select those 4 users.
> # Then from set visibility dropdown select visible.
> # 4 popups can be seen in the right side of page with same msg as "Selected
> user is already visible". And none of the popup contains the name of the user
> to which it was concerned to.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4092) [Ranger UI] [React JS] Showing multiple msg prompts for multiple users/groups visibility toggle with same msg.
[
https://issues.apache.org/jira/browse/RANGER-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek updated RANGER-4092:
-
Labels: ranger-react (was: )
> [Ranger UI] [React JS] Showing multiple msg prompts for multiple users/groups
> visibility toggle with same msg.
> --
>
> Key: RANGER-4092
> URL: https://issues.apache.org/jira/browse/RANGER-4092
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Kundan Kumar Jha
>Priority: Major
> Labels: ranger-react
> Attachments: Screenshot 2023-02-16 at 8.36.52 PM.png, Screenshot
> 2023-02-16 at 8.44.48 PM.png
>
>
> Behaviour in React UI:
> Showing multiple success/failure msg prompts for multiple users/groups
> visibility toggle with same msg.
> Behaviour in Backbone JS UI:
> Shows a dialog box once with users/groups already visible or already hidden
> if all the selected users/groups are in the state which it was supposed to
> acquire.
> Expected behaviour:
> Either it shows the combine one status that users/groups are already hidden
> or visible as in already present UI.
> Or
> If shows individual popups then show with name for eg.
> For users: "Selected user \{user_name} is already hidden or visible" instead
> of just showing "Selected user is already hidden or visible".
> For groups: "Selected groups group_name} is already hidden or visible"
> instead of just showing "Selected group is already hidden or visible".
>
> Steps to reproduce:
> # Create 4 users user_1, user_2, user_3, user_4 in ranger.
> # Then in users table of users page in ranger UI select those 4 users.
> # Then from set visibility dropdown select visible.
> # 4 popups can be seen in the right side of page with same msg as "Selected
> user is already visible". And none of the popup contains the name of the user
> to which it was concerned to.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (RANGER-4093) [Ranger UI] [React JS] On create role page clicking continuously multiple times the "Add user", "Add Group" and "Add role" button without selecting anything shows multip
Kundan Kumar Jha created RANGER-4093: Summary: [Ranger UI] [React JS] On create role page clicking continuously multiple times the "Add user", "Add Group" and "Add role" button without selecting anything shows multiple prompts in series with same msg. Key: RANGER-4093 URL: https://issues.apache.org/jira/browse/RANGER-4093 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Kundan Kumar Jha Behaviour in React UI: On the create role page when "Add user", "Add group" and "Add role" button is clicked without selecting any user, group or roles continuously it shows a lot of popups. Behaviour in Backbone JS UI: Shows a single dialog box with no user, group or role selected and the page is blocked until the prompt is removed by clicking OK or it automatically gone after some time. Expected Behaviour: It should block the page for some time until the popup goes away or not show multiple popups. Steps to reproduce: # Navigate to create role page of ranger UI # Click on "Add Users"/"Add Groups"/"Add Roles" button continuously. # Lot of popups with msg "Please select at least one user" appear on right side of screen. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4094) [Ranger UI] [React JS] User_name/ group_name/ roles field of their tables clipping names more that 14-15 characters long.
Kundan Kumar Jha created RANGER-4094: Summary: [Ranger UI] [React JS] User_name/ group_name/ roles field of their tables clipping names more that 14-15 characters long. Key: RANGER-4094 URL: https://issues.apache.org/jira/browse/RANGER-4094 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Kundan Kumar Jha Behaviour in React UI: User_name field of user table not fully showing more than 12 characters. User_name field of user table not fully showing more than 14 characters. User_name field of user table not fully showing more than 21 characters. Behaviour in Backbone JS UI: User_name field of user table not fully showing more than 30 characters. User_name field of user table not fully showing more than 30 characters. User_name field of user table not fully showing more than 30 characters. Expected behaviour: Analyse and see if its a requirement increase the no. of char visibility. As in legacy it allows more than 30 chars. Steps to reproduce: # Add users with long names(more that 15 chars). # And navigate to the user in user table of users page of ranger UI. # The name is only showing 12 chars and followed by ... -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4095) [Ranger UI] [Ranger-React] On users/groups/roles page in settings - The page number can be decreased to zero and negative and can be increased beyond max pages available
Kundan Kumar Jha created RANGER-4095: Summary: [Ranger UI] [Ranger-React] On users/groups/roles page in settings - The page number can be decreased to zero and negative and can be increased beyond max pages available to show. Key: RANGER-4095 URL: https://issues.apache.org/jira/browse/RANGER-4095 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Kundan Kumar Jha Behaviour in React UI: In users/groups/roles page in settings - The page number can be decreased to zero and negative and can be increased beyond max pages available to show. Behaviour in Backbone JS UI: Not available Expected Behaviour: Although logically the result is not affected through this behaviour as for zero and negative page no. its showing page 1 and for page no greater than max available page its showing the data of max page only. But from UI perspective we should at-least restrict the increase and decrease page no feature to min and max limit. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4095) [Ranger UI] [Ranger-React] On users/groups/roles page in settings - The page number can be decreased to zero and negative and can be increased beyond max pages available
[ https://issues.apache.org/jira/browse/RANGER-4095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kundan Kumar Jha updated RANGER-4095: - Attachment: Screenshot 2023-02-16 at 9.26.43 PM.png Screenshot 2023-02-16 at 9.27.06 PM.png > [Ranger UI] [Ranger-React] On users/groups/roles page in settings - The page > number can be decreased to zero and negative and can be increased beyond max > pages available to show. > -- > > Key: RANGER-4095 > URL: https://issues.apache.org/jira/browse/RANGER-4095 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Kundan Kumar Jha >Priority: Major > Labels: ranger-react > Attachments: Screenshot 2023-02-16 at 9.26.43 PM.png, Screenshot > 2023-02-16 at 9.27.06 PM.png > > > Behaviour in React UI: > In users/groups/roles page in settings - The page number can be decreased to > zero and negative and can be increased beyond max pages available to show. > > Behaviour in Backbone JS UI: > Not available > > Expected Behaviour: > Although logically the result is not affected through this behaviour as for > zero and negative page no. its showing page 1 and for page no greater than > max available page its showing the data of max page only. > But from UI perspective we should at-least restrict the increase and decrease > page no feature to min and max limit. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4096) [Ranger UI] [React JS] "show all users" button is not available in the show users prompt of groups table even if the users list is longer than 100.
Kundan Kumar Jha created RANGER-4096: Summary: [Ranger UI] [React JS] "show all users" button is not available in the show users prompt of groups table even if the users list is longer than 100. Key: RANGER-4096 URL: https://issues.apache.org/jira/browse/RANGER-4096 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Kundan Kumar Jha Behaviour in React UI: Add more than 100 users with public as group and click on the users column of public group from group tables. Its clipping the users list after 100 but not showing the option to show more. Behaviour in backbone JS UI: In the similar case in old UI the show all users option is available. Steps to reproduce: Add more than 100 users with public as group and click on the users column of public group from group tables. Its clipping the users list after 100 but not showing the option to show more. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4096) [Ranger UI] [React JS] "show all users" button is not available in the show users prompt of groups table even if the users list is longer than 100.
[
https://issues.apache.org/jira/browse/RANGER-4096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kundan Kumar Jha updated RANGER-4096:
-
Description:
Behaviour in React UI:
"Show all users" option is not available although if the no. of user added to a
group is more than 100 and they are clipped in the show user prompt.
Behaviour in backbone JS UI:
In the similar case in old UI the show all users option is available.
Steps to reproduce:
# create a group "\{random}_group".
# Add more than 100 users with "\{random}_group" as group and click on the
users column of "\{random}_group" group from group tables.
# Its clipping the users list after 100 but not showing the option to show all
users.
was:
Behaviour in React UI:
Add more than 100 users with public as group and click on the users column of
public group from group tables. Its clipping the users list after 100 but not
showing the option to show more.
Behaviour in backbone JS UI:
In the similar case in old UI the show all users option is available.
Steps to reproduce:
Add more than 100 users with public as group and click on the users column of
public group from group tables. Its clipping the users list after 100 but not
showing the option to show more.
> [Ranger UI] [React JS] "show all users" button is not available in the show
> users prompt of groups table even if the users list is longer than 100.
> ---
>
> Key: RANGER-4096
> URL: https://issues.apache.org/jira/browse/RANGER-4096
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Kundan Kumar Jha
>Priority: Major
> Labels: ranger-react
>
> Behaviour in React UI:
> "Show all users" option is not available although if the no. of user added to
> a group is more than 100 and they are clipped in the show user prompt.
> Behaviour in backbone JS UI:
> In the similar case in old UI the show all users option is available.
>
> Steps to reproduce:
> # create a group "\{random}_group".
> # Add more than 100 users with "\{random}_group" as group and click on the
> users column of "\{random}_group" group from group tables.
> # Its clipping the users list after 100 but not showing the option to show
> all users.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (RANGER-4097) [Ranger UI] [React JS] Deletion of zone from resource based policy page leads to disappearance of all the other services before refreshing the page.
Kundan Kumar Jha created RANGER-4097: Summary: [Ranger UI] [React JS] Deletion of zone from resource based policy page leads to disappearance of all the other services before refreshing the page. Key: RANGER-4097 URL: https://issues.apache.org/jira/browse/RANGER-4097 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Kundan Kumar Jha On deleting all the services from the service headers inside a zone in resource policy page and removing the zone name from zone filter it refreshes the page but instead of just removing services from those service headers which are targeted in zone all the services inside all the service headers are gone. Steps to reproduce: # Create a zone named "temp_zone" and select cm_hive as the service from Hadoop SQL service header. # Navigate to resources based policies page and select "temp_zone" from the dropdown security zone. # Click on delete icon of the "cm_hive" service inside zone. # Then remove the filter of "temp_zone" from security zone search bar. # Then the resource based policy page loads but all the services inside service headers are gone for all the services instead of only those service headers whose all services are deleted. NOTE: After refreshing the page everything works fine. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4095) [Ranger UI] [React JS] On users/groups/roles page in settings - The page number can be decreased to zero and negative and can be increased beyond max pages available to
[ https://issues.apache.org/jira/browse/RANGER-4095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kundan Kumar Jha updated RANGER-4095: - Summary: [Ranger UI] [React JS] On users/groups/roles page in settings - The page number can be decreased to zero and negative and can be increased beyond max pages available to show. (was: [Ranger UI] [Ranger-React] On users/groups/roles page in settings - The page number can be decreased to zero and negative and can be increased beyond max pages available to show.) > [Ranger UI] [React JS] On users/groups/roles page in settings - The page > number can be decreased to zero and negative and can be increased beyond max > pages available to show. > -- > > Key: RANGER-4095 > URL: https://issues.apache.org/jira/browse/RANGER-4095 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Kundan Kumar Jha >Priority: Major > Labels: ranger-react > Attachments: Screenshot 2023-02-16 at 9.26.43 PM.png, Screenshot > 2023-02-16 at 9.27.06 PM.png > > > Behaviour in React UI: > In users/groups/roles page in settings - The page number can be decreased to > zero and negative and can be increased beyond max pages available to show. > > Behaviour in Backbone JS UI: > Not available > > Expected Behaviour: > Although logically the result is not affected through this behaviour as for > zero and negative page no. its showing page 1 and for page no greater than > max available page its showing the data of max page only. > But from UI perspective we should at-least restrict the increase and decrease > page no feature to min and max limit. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4097) [Ranger UI] [React JS] Deletion of all services inside a zone in resource based policy page leads to disappearance of all the other services before refreshing the page.
[ https://issues.apache.org/jira/browse/RANGER-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kundan Kumar Jha updated RANGER-4097: - Summary: [Ranger UI] [React JS] Deletion of all services inside a zone in resource based policy page leads to disappearance of all the other services before refreshing the page. (was: [Ranger UI] [React JS] Deletion of zone from resource based policy page leads to disappearance of all the other services before refreshing the page.) > [Ranger UI] [React JS] Deletion of all services inside a zone in resource > based policy page leads to disappearance of all the other services before > refreshing the page. > > > Key: RANGER-4097 > URL: https://issues.apache.org/jira/browse/RANGER-4097 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Kundan Kumar Jha >Priority: Major > Labels: ranger-react > > On deleting all the services from the service headers inside a zone in > resource policy page and removing the zone name from zone filter it refreshes > the page but instead of just removing services from those service headers > which are targeted in zone all the services inside all the service headers > are gone. > > Steps to reproduce: > # Create a zone named "temp_zone" and select cm_hive as the service from > Hadoop SQL service header. > # Navigate to resources based policies page and select "temp_zone" from the > dropdown security zone. > # Click on delete icon of the "cm_hive" service inside zone. > # Then remove the filter of "temp_zone" from security zone search bar. > # Then the resource based policy page loads but all the services inside > service headers are gone for all the services instead of only those service > headers whose all services are deleted. > NOTE: After refreshing the page everything works fine. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4097) [Ranger UI] [React JS] Deletion of all services inside a zone in resource based policy page leads to disappearance of all the other services before refreshing the page.
[ https://issues.apache.org/jira/browse/RANGER-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kundan Kumar Jha updated RANGER-4097: - Attachment: Screenshot 2023-02-16 at 10.53.01 PM.png Screenshot 2023-02-16 at 10.53.21 PM.png > [Ranger UI] [React JS] Deletion of all services inside a zone in resource > based policy page leads to disappearance of all the other services before > refreshing the page. > > > Key: RANGER-4097 > URL: https://issues.apache.org/jira/browse/RANGER-4097 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Kundan Kumar Jha >Priority: Major > Labels: ranger-react > Attachments: Screenshot 2023-02-16 at 10.53.01 PM.png, Screenshot > 2023-02-16 at 10.53.21 PM.png > > > On deleting all the services from the service headers inside a zone in > resource policy page and removing the zone name from zone filter it refreshes > the page but instead of just removing services from those service headers > which are targeted in zone all the services inside all the service headers > are gone. > > Steps to reproduce: > # Create a zone named "temp_zone" and select cm_hive as the service from > Hadoop SQL service header. > # Navigate to resources based policies page and select "temp_zone" from the > dropdown security zone. > # Click on delete icon of the "cm_hive" service inside zone. > # Then remove the filter of "temp_zone" from security zone search bar. > # Then the resource based policy page loads but all the services inside > service headers are gone for all the services instead of only those service > headers whose all services are deleted. > NOTE: After refreshing the page everything works fine. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (RANGER-3063) 404 http status response on requesting an existing policy
[
https://issues.apache.org/jira/browse/RANGER-3063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramachandran resolved RANGER-3063.
--
Resolution: Fixed
> 404 http status response on requesting an existing policy
> -
>
> Key: RANGER-3063
> URL: https://issues.apache.org/jira/browse/RANGER-3063
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Affects Versions: 2.0.0
> Environment: Cloudera, CDP (CDH) 7.1.3
> Hadoop - 3.1.1.7.1.3.0-100
> Ranger - 2.0.0.7.1.3.0-100
>Reporter: Vyacheslav Tutrinov
>Assignee: Ramachandran
>Priority: Major
>
> I caught a strange behavior of the ranger admin REST API.
> The challenge was started as I saw that the 'cm_kms' service doesn't appear
> on the UI side however it exists in the REST API response.
> Then the trying to get policies list for this service respond by the list
> that contains the single policy:
> {code:bash}
> [root@vm path]# curl -XGET -u user:** -v
> http://my-ranger-server-host:6080/service/public/v2/api/service/cm_kms/policy
> * About to connect() tomy-ranger-server-host port 6080 (#0)
> * Trying 10.6.120.140...
> * Connected to my-ranger-server-host (10.6.120.140) port 6080 (#0)
> * Server auth using Basic with user 'user'
> > GET /service/public/v2/api/service/cm_kms/policy HTTP/1.1
> > Authorization: Basic *
> > User-Agent: curl/7.29.0
> > Host: my-ranger-server-host:6080
> > Accept: */*
> >
> < HTTP/1.1 200 OK
> < Set-Cookie: RANGERADMINSESSIONID=42E2616A84477202A0CB4442C9C4EA88; Path=/;
> HttpOnly
> < X-Frame-Options: DENY
> < X-XSS-Protection: 1; mode=block
> < Strict-Transport-Security: max-age=31536000; includeSubDomains
> < Content-Security-Policy: default-src 'none'; script-src 'self'
> 'unsafe-inline' 'unsafe-eval'; connect-src 'self'; img-src 'self'; style-src
> 'self' 'unsafe-inline';font-src 'self'
> < Cache-Control: no-cache, no-store, max-age=0, must-revalidate
> < Pragma: no-cache
> < Expires: 0
> < X-Content-Type-Options: nosniff
> < Content-Type: application/json
> < Transfer-Encoding: chunked
> < Date: Thu, 29 Oct 2020 07:11:15 GMT
> < Server: Apache Ranger
> <
> [{"id":41,"guid":"52b42504-5798-4340-9da3-8e9188a3592f","isEnabled":true,"version":1,"service":"cm_kms","name":"all
> - keyname","policyType":0,"policyPriority":0,"description":"Policy for all -
> keyname","isAuditEnabled":true,"resources":{"keyname":{"values":["*"],"isExcludes":false,"isRecursive":false}},"policyItems":[{"accesses":[{"type":"create","isAllowed":true},{"type":"delete","isAllowed":true},{"type":"rollover","isAllowed":true},{"type":"setkeymaterial","isAllowed":true},{"type":"get","isAllowed":true},{"type":"getkeys","isAllowed":true},{"type":"getmetadata","isAllowed":true},{"type":"generateeek","isAllowed":true},{"type":"decrypteek","isAllowed":true}],"users":["keyadmin"],"groups":[],"roles":[],"conditions":[],"delegateAdmin":true},{"accesses":[{"type":"getmetadata","isAllowed":true},{"type":"generateeek","isAllowed":true}],"users":["hdfs"],"groups":[],"roles":[],"conditions":[],"delegateAdmin":true},{"accesses":[{"type":"getmetadata","isAllowed":true},{"type":"decrypteek","isAllowed":true}],"users":["hive"],"groups":[],"roles":[],"conditions":[],"delegateAdmin":true}],"denyPolicyItems":[],"allowExceptions":[],"denyExceptions":[],"dataMaskPolicyItems":[],"rowFilterPolicyItems":[],"serviceType":"kms","options":{},"validitySchedules":[],"policyLabels":[],"zoneName":"","isDenyAllElse":false}]
> {code}
> However the request for the specific policy by name 'all - keyname' responded
> by 404 status:
> {code:bash}
> [root@vm path]# curl -XGET -u user:** -v
> http://my-ranger-server-host:6080/service/public/v2/api/service/cm_kms/policy/all%20-%20keyname
> * About to connect() to my-ranger-server-host port 6080 (#0)
> * Trying 10.6.120.140...
> * Connected to my-ranger-server-host (10.6.120.140) port 6080 (#0)
> * Server auth using Basic with user 'user'
> > GET /service/public/v2/api/service/cm_kms/policy/all%20-%20keyname HTTP/1.1
> > Authorization: Basic ***
> > User-Agent: curl/7.29.0
> > Host: my-ranger-server-host:6080
> > Accept: */*
> >
> < HTTP/1.1 404 Not Found
> < Set-Cookie: RANGERADMINSESSIONID=2885FFB77C5B83345F5F6C0F4E7CB4D8; Path=/;
> HttpOnly
> < X-Frame-Options: DENY
> < X-XSS-Protection: 1; mode=block
> < Strict-Transport-Security: max-age=31536000; includeSubDomains
> < Content-Security-Policy: default-src 'none'; script-src 'self'
> 'unsafe-inline' 'unsafe-eval'; connect-src 'self'; img-src 'self'; style-src
> 'self' 'unsafe-inline';font-src 'self'
> < Cache-Control: no-cache, no-store, max-age=0, must-revalidate
> < Pragma: no-cache
> < Expires: 0
> < X-Content-Type-Options: nosniff
> < Content-Type: application/json
> < Transfer-Encod
[jira] [Resolved] (RANGER-2738) is there limit on maximum number of ranger policies?
[ https://issues.apache.org/jira/browse/RANGER-2738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramachandran resolved RANGER-2738. -- Assignee: Ramachandran Resolution: Fixed > is there limit on maximum number of ranger policies? > > > Key: RANGER-2738 > URL: https://issues.apache.org/jira/browse/RANGER-2738 > Project: Ranger > Issue Type: Wish > Components: Ranger >Reporter: t oo >Assignee: Ramachandran >Priority: Major > > can i have 1 million policies or is there some hard limit? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4098) [Ranger UI] [React JS] On deletion of all services inside a zone leads to a blank page for other zones also before manually refreshing the whole page.
Kundan Kumar Jha created RANGER-4098: Summary: [Ranger UI] [React JS] On deletion of all services inside a zone leads to a blank page for other zones also before manually refreshing the whole page. Key: RANGER-4098 URL: https://issues.apache.org/jira/browse/RANGER-4098 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Kundan Kumar Jha Deleting all the services form all the service types inside a zone and selecting another zone in "security zone" search bar in resources based policy page leads to a blank page with no services instead of showing services attached to the selected zone. Steps to reproduce: # create two zones "temp_zone_1" and"temp_zone_2" with different services of different service types # Then select zone "temp_zone_1" from security zone search bar. # Delete the all services inside the zone "temp_zone_1" by clicking on delete icon. # Then again click on the security zone search bar and select zone "temp_zone_2" the page will load but no services appear there. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4098) [Ranger UI] [React JS] On deletion of all services inside a zone leads to a blank page for other zones also before manually refreshing the whole page.
[ https://issues.apache.org/jira/browse/RANGER-4098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kundan Kumar Jha updated RANGER-4098: - Attachment: (was: Screenshot 2023-02-16 at 11.01.02 PM.png) > [Ranger UI] [React JS] On deletion of all services inside a zone leads to a > blank page for other zones also before manually refreshing the whole page. > -- > > Key: RANGER-4098 > URL: https://issues.apache.org/jira/browse/RANGER-4098 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Kundan Kumar Jha >Priority: Major > Labels: ranger-react > Attachments: Screenshot 2023-02-16 at 11.01.36 PM.png > > > Deleting all the services form all the service types inside a zone and > selecting another zone in "security zone" search bar in resources based > policy page leads to a blank page with no services instead of showing > services attached to the selected zone. > > Steps to reproduce: > # create two zones "temp_zone_1" and"temp_zone_2" with different services of > different service types > # Then select zone "temp_zone_1" from security zone search bar. > # Delete the all services inside the zone "temp_zone_1" by clicking on > delete icon. > # Then again click on the security zone search bar and select zone > "temp_zone_2" the page will load but no services appear there. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4098) [Ranger UI] [React JS] On deletion of all services inside a zone leads to a blank page for other zones also before manually refreshing the whole page.
[ https://issues.apache.org/jira/browse/RANGER-4098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kundan Kumar Jha updated RANGER-4098: - Attachment: (was: Screenshot 2023-02-16 at 11.01.11 PM.png) > [Ranger UI] [React JS] On deletion of all services inside a zone leads to a > blank page for other zones also before manually refreshing the whole page. > -- > > Key: RANGER-4098 > URL: https://issues.apache.org/jira/browse/RANGER-4098 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Kundan Kumar Jha >Priority: Major > Labels: ranger-react > Attachments: Screenshot 2023-02-16 at 11.01.36 PM.png > > > Deleting all the services form all the service types inside a zone and > selecting another zone in "security zone" search bar in resources based > policy page leads to a blank page with no services instead of showing > services attached to the selected zone. > > Steps to reproduce: > # create two zones "temp_zone_1" and"temp_zone_2" with different services of > different service types > # Then select zone "temp_zone_1" from security zone search bar. > # Delete the all services inside the zone "temp_zone_1" by clicking on > delete icon. > # Then again click on the security zone search bar and select zone > "temp_zone_2" the page will load but no services appear there. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4098) [Ranger UI] [React JS] On deletion of all services inside a zone leads to a blank page for other zones also before manually refreshing the whole page.
[ https://issues.apache.org/jira/browse/RANGER-4098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kundan Kumar Jha updated RANGER-4098: - Attachment: Screenshot 2023-02-16 at 11.01.02 PM.png Screenshot 2023-02-16 at 11.01.11 PM.png Screenshot 2023-02-16 at 11.01.36 PM.png > [Ranger UI] [React JS] On deletion of all services inside a zone leads to a > blank page for other zones also before manually refreshing the whole page. > -- > > Key: RANGER-4098 > URL: https://issues.apache.org/jira/browse/RANGER-4098 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Kundan Kumar Jha >Priority: Major > Labels: ranger-react > Attachments: Screenshot 2023-02-16 at 11.01.36 PM.png > > > Deleting all the services form all the service types inside a zone and > selecting another zone in "security zone" search bar in resources based > policy page leads to a blank page with no services instead of showing > services attached to the selected zone. > > Steps to reproduce: > # create two zones "temp_zone_1" and"temp_zone_2" with different services of > different service types > # Then select zone "temp_zone_1" from security zone search bar. > # Delete the all services inside the zone "temp_zone_1" by clicking on > delete icon. > # Then again click on the security zone search bar and select zone > "temp_zone_2" the page will load but no services appear there. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [ranger] vijayinani commented on pull request #74: Fix usersync properties configmap
vijayinani commented on PR #74: URL: https://github.com/apache/ranger/pull/74#issuecomment-1433471492 The issue still persists. I went crazy as my Ranger LDAP integration was not working. Finally solved after ghosting the key value pair. -- 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: dev-unsubscr...@ranger.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (RANGER-4097) [Ranger UI] [React JS] Deletion of all services inside a zone in resource based policy page leads to disappearance of all the other services before refreshing the page.
[ https://issues.apache.org/jira/browse/RANGER-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kundan Kumar Jha updated RANGER-4097: - Attachment: (was: Screenshot 2023-02-16 at 10.53.01 PM.png) > [Ranger UI] [React JS] Deletion of all services inside a zone in resource > based policy page leads to disappearance of all the other services before > refreshing the page. > > > Key: RANGER-4097 > URL: https://issues.apache.org/jira/browse/RANGER-4097 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Kundan Kumar Jha >Priority: Major > Labels: ranger-react > Attachments: Screenshot 2023-02-16 at 10.53.21 PM.png > > > On deleting all the services from the service headers inside a zone in > resource policy page and removing the zone name from zone filter it refreshes > the page but instead of just removing services from those service headers > which are targeted in zone all the services inside all the service headers > are gone. > > Steps to reproduce: > # Create a zone named "temp_zone" and select cm_hive as the service from > Hadoop SQL service header. > # Navigate to resources based policies page and select "temp_zone" from the > dropdown security zone. > # Click on delete icon of the "cm_hive" service inside zone. > # Then remove the filter of "temp_zone" from security zone search bar. > # Then the resource based policy page loads but all the services inside > service headers are gone for all the services instead of only those service > headers whose all services are deleted. > NOTE: After refreshing the page everything works fine. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4099) [Ranger UI] [React JS] Focus remains on last hovered element in the dropdown of security zone search bar of resource based policy page.
Kundan Kumar Jha created RANGER-4099: Summary: [Ranger UI] [React JS] Focus remains on last hovered element in the dropdown of security zone search bar of resource based policy page. Key: RANGER-4099 URL: https://issues.apache.org/jira/browse/RANGER-4099 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Kundan Kumar Jha Focus remains on the last hovered element in the security zone search bar dropdown on resource based policy page even after moving out the cursor from the dropdown. Steps to reproduce: # Create two zones "temp_zone_1" and "temp_zone_2". # Then select temp_zone_1" from "security zone" search bar of resource based policy page. # Then click on the search bar again and hover on the "temp_zone_2" and then move out the cursor but the "temp_zone_2" still focused. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4099) [Ranger UI] [React JS] Focus remains on last hovered element in the dropdown of security zone search bar of resource based policy page.
[ https://issues.apache.org/jira/browse/RANGER-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kundan Kumar Jha updated RANGER-4099: - Attachment: Screenshot 2023-02-16 at 11.26.57 PM.png > [Ranger UI] [React JS] Focus remains on last hovered element in the dropdown > of security zone search bar of resource based policy page. > --- > > Key: RANGER-4099 > URL: https://issues.apache.org/jira/browse/RANGER-4099 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Kundan Kumar Jha >Priority: Major > Labels: ranger-react > Attachments: Screenshot 2023-02-16 at 11.26.57 PM.png > > > Focus remains on the last hovered element in the security zone search bar > dropdown on resource based policy page even after moving out the cursor from > the dropdown. > > Steps to reproduce: > # Create two zones "temp_zone_1" and "temp_zone_2". > # Then select temp_zone_1" from "security zone" search bar of resource based > policy page. > # Then click on the search bar again and hover on the "temp_zone_2" and then > move out the cursor but the "temp_zone_2" still focused. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (RANGER-3999) Implement more efficient way to handle _any access authorization
[ https://issues.apache.org/jira/browse/RANGER-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17644065#comment-17644065 ] Abhay Kulkarni edited comment on RANGER-3999 at 2/16/23 6:41 PM: - Commit details: master: [https://github.com/apache/ranger/commit/56d5bf9173dc2c6d04692a07e67eace5e5d98ed4] Additional review: [https://reviews.apache.org/r/74304/] and commit detail: [https://github.com/apache/ranger/commit/7a7215f67e7db807ee0401f2b41d7bb871a248f5] Additional review: [https://reviews.apache.org/r/74308/] and commit details: https://github.com/apache/ranger/commit/4b941b2f0d7a8390155c61fa0960c42aa8a37b69 was (Author: abhayk): Commit details: master: [https://github.com/apache/ranger/commit/56d5bf9173dc2c6d04692a07e67eace5e5d98ed4] Additional review: [https://reviews.apache.org/r/74304/] and commit detail: [https://github.com/apache/ranger/commit/7a7215f67e7db807ee0401f2b41d7bb871a248f5] > Implement more efficient way to handle _any access authorization > > > Key: RANGER-3999 > URL: https://issues.apache.org/jira/browse/RANGER-3999 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Abhay >Assignee: Abhay Kulkarni >Priority: Major > > If a user-initiated operation requires checking if more than one permission > is granted, then currently, each permission requires a call to internal > Policy Engine API for the same accessed resource. This leads to many > repetitive computations which may be avoided if the policy engine API > supports multiple permissions. In that case, optimization may be achieved by > pushing authorization for multiple permissions down to the lowest possible > level. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [ranger] kumaab merged pull request #210: RANGER-4071: Support for LDAP/AD usernames and group names with special chars
kumaab merged PR #210: URL: https://github.com/apache/ranger/pull/210 -- 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: dev-unsubscr...@ranger.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (RANGER-3508) Enable easier access to user/group/tag/resource attributes in condition expressions
[
https://issues.apache.org/jira/browse/RANGER-3508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Madhan Neethiraj updated RANGER-3508:
-
Fix Version/s: 2.3.0
> Enable easier access to user/group/tag/resource attributes in condition
> expressions
> ---
>
> Key: RANGER-3508
> URL: https://issues.apache.org/jira/browse/RANGER-3508
> Project: Ranger
> Issue Type: Improvement
> Components: plugins
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 3.0.0, 2.3.0
>
>
> User/group/tags/resource attributes should be easily accessible in condition
> expressions, with expressions like:
> {noformat}
> USER.state == 'CA'
> UG['test'].dept == 'MKTG'
> REQ.accessType == 'SELECT'
> RES.database == 'hr'
> RES.table == 'employee'
> TAG._type == 'PII'
> TAG.attr1 == 'value1'
> TAGS.PII.attr1 == 'value1'
> TNAMES.length == 2
> TNAMES.indexOf('PCI') != -1{noformat}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (RANGER-3508) Enable easier access to user/group/tag/resource attributes in condition expressions
[
https://issues.apache.org/jira/browse/RANGER-3508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17444278#comment-17444278
]
Madhan Neethiraj edited comment on RANGER-3508 at 2/17/23 12:08 AM:
{noformat}
commit a0363eaba9f708088fd0a83f5c89bda5bec58b3c
Author: Madhan Neethiraj
Date: Thu Nov 11 13:20:35 2021 -0800
RANGER-3508: enhanced script condition expression for easier access to
user/group/tag/resource attributes
{noformat}
{noformat}
commit 911bdc88c86e316a04e8ae7719fc5a967425648e
Author: Madhan Neethiraj
Date: Mon Nov 8 17:12:58 2021 -0800
RANGER-3508: enhanced script condition expression for easier access to
user/group/tag/resource attributes
(cherry picked from commit befc6d7e28b48c9e783af3e863af891c5fdd2b69)
{noformat}
was (Author: madhan.neethiraj):
{noformat}
commit a0363eaba9f708088fd0a83f5c89bda5bec58b3c
Author: Madhan Neethiraj
Date: Thu Nov 11 13:20:35 2021 -0800
RANGER-3508: enhanced script condition expression for easier access to
user/group/tag/resource attributes
{noformat}
> Enable easier access to user/group/tag/resource attributes in condition
> expressions
> ---
>
> Key: RANGER-3508
> URL: https://issues.apache.org/jira/browse/RANGER-3508
> Project: Ranger
> Issue Type: Improvement
> Components: plugins
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Fix For: 3.0.0, 2.3.0
>
>
> User/group/tags/resource attributes should be easily accessible in condition
> expressions, with expressions like:
> {noformat}
> USER.state == 'CA'
> UG['test'].dept == 'MKTG'
> REQ.accessType == 'SELECT'
> RES.database == 'hr'
> RES.table == 'employee'
> TAG._type == 'PII'
> TAG.attr1 == 'value1'
> TAGS.PII.attr1 == 'value1'
> TNAMES.length == 2
> TNAMES.indexOf('PCI') != -1{noformat}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Review Request 74309: RANGER-4084: Use the exact login ID in the header instead of capitalising the first character
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74309/ --- Review request for ranger, Brijesh Bhalala, Dhaval Rajpara, and Mugdha Varadkar. Bugs: RANGER-4084 https://issues.apache.org/jira/browse/RANGER-4084 Repository: ranger Description --- The first character of the login ID in the header is being converted to uppercase, and this might be confusing because it is possible to create users with same login Id but different case, for ex :- temp_user and Temp_user, and when both the users are logged in, the header will display "Temp_user". Hence, the login ID must be displayed exactly as it is. Diffs - security-admin/src/main/webapp/react-webapp/src/views/Header.jsx b054dc21e Diff: https://reviews.apache.org/r/74309/diff/1/ Testing --- Tested changes on a cluster Thanks, Abhishek Patil
[jira] [Updated] (RANGER-4084) Login id which is available on left most corner coming as Camel case
[ https://issues.apache.org/jira/browse/RANGER-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek updated RANGER-4084: - Attachment: 0001-RANGER-4084-Use-the-exact-login-ID-in-the-header-ins.patch > Login id which is available on left most corner coming as Camel case > - > > Key: RANGER-4084 > URL: https://issues.apache.org/jira/browse/RANGER-4084 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Anupam Rai >Assignee: Abhishek >Priority: Major > Labels: ranger-react > Attachments: > 0001-RANGER-4084-Use-the-exact-login-ID-in-the-header-ins.patch, Screenshot > 2023-02-15 at 4.23.22 PM.png > > > Login id which is available on left most corner coming as Camel case > Create user with > user name - lowercase > first name - lowercase > Still is username is displayed in camel case on ranger banner , Screenshot > attached. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (RANGER-3756) ranger SQL-transaction can not work with GTID-enabled mysql server
[
https://issues.apache.org/jira/browse/RANGER-3756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17689578#comment-17689578
]
kirby zhou edited comment on RANGER-3756 at 2/17/23 7:08 AM:
-
I had encounter this bug with the cloud service of mysql provided by Tencent
Cloud.
[http://cloud.tencent.com|http://cloud.tencent.com/] 【China】or
[https://www.tencentcloud.com/] 【international】
It happens at the ranger-2.3 branch.
{code:sql}
Server version: 5.7.18-txsql-log 20211101
mysql> show variables like '%gtid%';
+--+---+
| Variable_name | Value |
+--+---+
| binlog_gtid_simple_recovery | ON |
| enforce_gtid_consistency | ON |
| gtid_executed_compression_period | 1000 |
| gtid_mode | ON |
| gtid_next | AUTOMATIC |
| gtid_owned | |
| gtid_purged | |
| session_track_gtids | OFF |
+--+---+
8 rows in set (0.01 sec)
{code}
was (Author: kirbyzhou):
I had encounter this bug with the cloud service of mysql provided by Tencent
Cloud.
[http://cloud.tencent.com|http://cloud.tencent.com/] 【China】or
[https://www.tencentcloud.com/] 【international】
It happens at the ranger-2.3 branch.
> ranger SQL-transaction can not work with GTID-enabled mysql server
> --
>
> Key: RANGER-3756
> URL: https://issues.apache.org/jira/browse/RANGER-3756
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Reporter: kirby zhou
>Priority: Critical
>
> A lot of cloud mysql service provider enable GTID_MODE by default.
> Such as TencentCloud, AliCloud, HuaWeiCloud.
> But ranger is not compatible with GTID_MODE.
> {code:java}
> 2022-05-11 07:19:12,533 [http-nio-6080-exec-3] INFO
> n.s.l.Slf4jSpyLogDelegator (Slf4jSpyLogDelegator.java:226) CREATE TEMPORARY
> TABLE IF NOT EXISTS TL_x_rms_resource_mapping (id BIGINT NOT NULL,
> change_timestamp
> DATETIME, hl_resource_id BIGINT, ll_resource_id BIGINT, PRIMARY KEY (id))
> 2022-05-11 07:19:12,543 [http-nio-6080-exec-3] ERROR
> n.s.l.Slf4jSpyLogDelegator (Slf4jSpyLogDelegator.java:111) 1.
> PreparedStatement.executeUpdate() CREATE TEMPORARY TABLE IF NOT EXISTS
> TL_x_rms_resource_mapping (id BIGINT NOT NULL, change_timestamp
> DATETIME, hl_resource_id BIGINT, ll_resource_id BIGINT, PRIMARY KEY (id))
> java.sql.SQLException: Statement violates GTID consistency: CREATE TEMPORARY
> TABLE and DROP TEMPORARY TABLE can only be executed outside transactional
> context. These statements are also not allowed in a function or trigger
> because functions and triggers are also considered to be multi-statement
> transactions.
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:998)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3835)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3771)
> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2435)
> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2582)
> ...
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:890)
> at
> org.apache.ranger.db.XXRMSServiceResourceDao.purge(XXRMSServiceResourceDao.java:248)
> at
> org.apache.ranger.biz.ServiceDBStore.deleteService(ServiceDBStore.java:1809)
> Error! Exception [EclipseLink-4002] (Eclipse Persistence Services -
> 2.5.2.v20140319-9ad6abd):
> org.eclipse.persistence.exceptions.DatabaseException Internal Exception:
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table
> 'ranger.tl_x_rms_resource_mapping' doesn't exist Error Code: 1146 Call:
> INSERT INTO TL_x_rms_resource_mapping (id) SELECT t0.id FROM
> x_rms_resource_mapping t0 WHERE (t0.hl_resource_id IN (SELECT t1.id FROM
> x_rms_service_resource t1 WHERE (t1.service_id = ?)) OR t0.ll_resource_id IN
> (SELECT t2.id FROM x_rms_service_resource t2 WHERE (t2.service_id = ?))) bind
> => [2 parameters bound] Query:
> DeleteAllQuery(name="XXRMSResourceMapping.deleteByServiceId"
> referenceClass=XXRMSResourceMapping sql="DELETE FROM
> TL_x_rms_resource_mapping")
> {code}
>
> Because CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed
> outside transactional context.
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-3756) ranger SQL-transaction can not work with GTID-enabled mysql server
[
https://issues.apache.org/jira/browse/RANGER-3756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kirby zhou updated RANGER-3756:
---
Attachment: image-2023-02-17-15-23-46-271.png
> ranger SQL-transaction can not work with GTID-enabled mysql server
> --
>
> Key: RANGER-3756
> URL: https://issues.apache.org/jira/browse/RANGER-3756
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Reporter: kirby zhou
>Priority: Critical
> Attachments: image-2023-02-17-15-23-26-423.png,
> image-2023-02-17-15-23-46-271.png
>
>
> A lot of cloud mysql service provider enable GTID_MODE by default.
> Such as TencentCloud, AliCloud, HuaWeiCloud.
> But ranger is not compatible with GTID_MODE.
> {code:java}
> 2022-05-11 07:19:12,533 [http-nio-6080-exec-3] INFO
> n.s.l.Slf4jSpyLogDelegator (Slf4jSpyLogDelegator.java:226) CREATE TEMPORARY
> TABLE IF NOT EXISTS TL_x_rms_resource_mapping (id BIGINT NOT NULL,
> change_timestamp
> DATETIME, hl_resource_id BIGINT, ll_resource_id BIGINT, PRIMARY KEY (id))
> 2022-05-11 07:19:12,543 [http-nio-6080-exec-3] ERROR
> n.s.l.Slf4jSpyLogDelegator (Slf4jSpyLogDelegator.java:111) 1.
> PreparedStatement.executeUpdate() CREATE TEMPORARY TABLE IF NOT EXISTS
> TL_x_rms_resource_mapping (id BIGINT NOT NULL, change_timestamp
> DATETIME, hl_resource_id BIGINT, ll_resource_id BIGINT, PRIMARY KEY (id))
> java.sql.SQLException: Statement violates GTID consistency: CREATE TEMPORARY
> TABLE and DROP TEMPORARY TABLE can only be executed outside transactional
> context. These statements are also not allowed in a function or trigger
> because functions and triggers are also considered to be multi-statement
> transactions.
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:998)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3835)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3771)
> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2435)
> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2582)
> ...
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:890)
> at
> org.apache.ranger.db.XXRMSServiceResourceDao.purge(XXRMSServiceResourceDao.java:248)
> at
> org.apache.ranger.biz.ServiceDBStore.deleteService(ServiceDBStore.java:1809)
> Error! Exception [EclipseLink-4002] (Eclipse Persistence Services -
> 2.5.2.v20140319-9ad6abd):
> org.eclipse.persistence.exceptions.DatabaseException Internal Exception:
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table
> 'ranger.tl_x_rms_resource_mapping' doesn't exist Error Code: 1146 Call:
> INSERT INTO TL_x_rms_resource_mapping (id) SELECT t0.id FROM
> x_rms_resource_mapping t0 WHERE (t0.hl_resource_id IN (SELECT t1.id FROM
> x_rms_service_resource t1 WHERE (t1.service_id = ?)) OR t0.ll_resource_id IN
> (SELECT t2.id FROM x_rms_service_resource t2 WHERE (t2.service_id = ?))) bind
> => [2 parameters bound] Query:
> DeleteAllQuery(name="XXRMSResourceMapping.deleteByServiceId"
> referenceClass=XXRMSResourceMapping sql="DELETE FROM
> TL_x_rms_resource_mapping")
> {code}
>
> Because CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed
> outside transactional context.
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-3756) ranger SQL-transaction can not work with GTID-enabled mysql server
[
https://issues.apache.org/jira/browse/RANGER-3756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kirby zhou updated RANGER-3756:
---
Attachment: image-2023-02-17-15-23-26-423.png
> ranger SQL-transaction can not work with GTID-enabled mysql server
> --
>
> Key: RANGER-3756
> URL: https://issues.apache.org/jira/browse/RANGER-3756
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Reporter: kirby zhou
>Priority: Critical
> Attachments: image-2023-02-17-15-23-26-423.png,
> image-2023-02-17-15-23-46-271.png
>
>
> A lot of cloud mysql service provider enable GTID_MODE by default.
> Such as TencentCloud, AliCloud, HuaWeiCloud.
> But ranger is not compatible with GTID_MODE.
> {code:java}
> 2022-05-11 07:19:12,533 [http-nio-6080-exec-3] INFO
> n.s.l.Slf4jSpyLogDelegator (Slf4jSpyLogDelegator.java:226) CREATE TEMPORARY
> TABLE IF NOT EXISTS TL_x_rms_resource_mapping (id BIGINT NOT NULL,
> change_timestamp
> DATETIME, hl_resource_id BIGINT, ll_resource_id BIGINT, PRIMARY KEY (id))
> 2022-05-11 07:19:12,543 [http-nio-6080-exec-3] ERROR
> n.s.l.Slf4jSpyLogDelegator (Slf4jSpyLogDelegator.java:111) 1.
> PreparedStatement.executeUpdate() CREATE TEMPORARY TABLE IF NOT EXISTS
> TL_x_rms_resource_mapping (id BIGINT NOT NULL, change_timestamp
> DATETIME, hl_resource_id BIGINT, ll_resource_id BIGINT, PRIMARY KEY (id))
> java.sql.SQLException: Statement violates GTID consistency: CREATE TEMPORARY
> TABLE and DROP TEMPORARY TABLE can only be executed outside transactional
> context. These statements are also not allowed in a function or trigger
> because functions and triggers are also considered to be multi-statement
> transactions.
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:998)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3835)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3771)
> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2435)
> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2582)
> ...
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:890)
> at
> org.apache.ranger.db.XXRMSServiceResourceDao.purge(XXRMSServiceResourceDao.java:248)
> at
> org.apache.ranger.biz.ServiceDBStore.deleteService(ServiceDBStore.java:1809)
> Error! Exception [EclipseLink-4002] (Eclipse Persistence Services -
> 2.5.2.v20140319-9ad6abd):
> org.eclipse.persistence.exceptions.DatabaseException Internal Exception:
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table
> 'ranger.tl_x_rms_resource_mapping' doesn't exist Error Code: 1146 Call:
> INSERT INTO TL_x_rms_resource_mapping (id) SELECT t0.id FROM
> x_rms_resource_mapping t0 WHERE (t0.hl_resource_id IN (SELECT t1.id FROM
> x_rms_service_resource t1 WHERE (t1.service_id = ?)) OR t0.ll_resource_id IN
> (SELECT t2.id FROM x_rms_service_resource t2 WHERE (t2.service_id = ?))) bind
> => [2 parameters bound] Query:
> DeleteAllQuery(name="XXRMSResourceMapping.deleteByServiceId"
> referenceClass=XXRMSResourceMapping sql="DELETE FROM
> TL_x_rms_resource_mapping")
> {code}
>
> Because CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed
> outside transactional context.
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-3756) ranger SQL-transaction can not work with GTID-enabled mysql server
[
https://issues.apache.org/jira/browse/RANGER-3756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17690196#comment-17690196
]
kirby zhou commented on RANGER-3756:
Reproduce steps:
# create a cloud mysql-5.7 instance on Tencent Cloud
# setup a ranger admin with the mysql db
# use web browser to open ranger-admin site
# create a HDFS service 【You DONOT need a real hdfs cluster】
# delete the HDFS service
# error happens
!image-2023-02-17-15-23-46-271.png!
!image-2023-02-17-15-24-11-315.png!
Additional Info:
I can not reproduce the bug with my private MySQL-8 server with GTID=on;
> ranger SQL-transaction can not work with GTID-enabled mysql server
> --
>
> Key: RANGER-3756
> URL: https://issues.apache.org/jira/browse/RANGER-3756
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Reporter: kirby zhou
>Priority: Critical
> Attachments: image-2023-02-17-15-23-26-423.png,
> image-2023-02-17-15-23-46-271.png, image-2023-02-17-15-24-11-315.png
>
>
> A lot of cloud mysql service provider enable GTID_MODE by default.
> Such as TencentCloud, AliCloud, HuaWeiCloud.
> But ranger is not compatible with GTID_MODE.
> {code:java}
> 2022-05-11 07:19:12,533 [http-nio-6080-exec-3] INFO
> n.s.l.Slf4jSpyLogDelegator (Slf4jSpyLogDelegator.java:226) CREATE TEMPORARY
> TABLE IF NOT EXISTS TL_x_rms_resource_mapping (id BIGINT NOT NULL,
> change_timestamp
> DATETIME, hl_resource_id BIGINT, ll_resource_id BIGINT, PRIMARY KEY (id))
> 2022-05-11 07:19:12,543 [http-nio-6080-exec-3] ERROR
> n.s.l.Slf4jSpyLogDelegator (Slf4jSpyLogDelegator.java:111) 1.
> PreparedStatement.executeUpdate() CREATE TEMPORARY TABLE IF NOT EXISTS
> TL_x_rms_resource_mapping (id BIGINT NOT NULL, change_timestamp
> DATETIME, hl_resource_id BIGINT, ll_resource_id BIGINT, PRIMARY KEY (id))
> java.sql.SQLException: Statement violates GTID consistency: CREATE TEMPORARY
> TABLE and DROP TEMPORARY TABLE can only be executed outside transactional
> context. These statements are also not allowed in a function or trigger
> because functions and triggers are also considered to be multi-statement
> transactions.
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:998)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3835)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3771)
> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2435)
> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2582)
> ...
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:890)
> at
> org.apache.ranger.db.XXRMSServiceResourceDao.purge(XXRMSServiceResourceDao.java:248)
> at
> org.apache.ranger.biz.ServiceDBStore.deleteService(ServiceDBStore.java:1809)
> Error! Exception [EclipseLink-4002] (Eclipse Persistence Services -
> 2.5.2.v20140319-9ad6abd):
> org.eclipse.persistence.exceptions.DatabaseException Internal Exception:
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table
> 'ranger.tl_x_rms_resource_mapping' doesn't exist Error Code: 1146 Call:
> INSERT INTO TL_x_rms_resource_mapping (id) SELECT t0.id FROM
> x_rms_resource_mapping t0 WHERE (t0.hl_resource_id IN (SELECT t1.id FROM
> x_rms_service_resource t1 WHERE (t1.service_id = ?)) OR t0.ll_resource_id IN
> (SELECT t2.id FROM x_rms_service_resource t2 WHERE (t2.service_id = ?))) bind
> => [2 parameters bound] Query:
> DeleteAllQuery(name="XXRMSResourceMapping.deleteByServiceId"
> referenceClass=XXRMSResourceMapping sql="DELETE FROM
> TL_x_rms_resource_mapping")
> {code}
>
> Because CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed
> outside transactional context.
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-3756) ranger SQL-transaction can not work with GTID-enabled mysql server
[
https://issues.apache.org/jira/browse/RANGER-3756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kirby zhou updated RANGER-3756:
---
Attachment: image-2023-02-17-15-24-11-315.png
> ranger SQL-transaction can not work with GTID-enabled mysql server
> --
>
> Key: RANGER-3756
> URL: https://issues.apache.org/jira/browse/RANGER-3756
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Reporter: kirby zhou
>Priority: Critical
> Attachments: image-2023-02-17-15-23-26-423.png,
> image-2023-02-17-15-23-46-271.png, image-2023-02-17-15-24-11-315.png
>
>
> A lot of cloud mysql service provider enable GTID_MODE by default.
> Such as TencentCloud, AliCloud, HuaWeiCloud.
> But ranger is not compatible with GTID_MODE.
> {code:java}
> 2022-05-11 07:19:12,533 [http-nio-6080-exec-3] INFO
> n.s.l.Slf4jSpyLogDelegator (Slf4jSpyLogDelegator.java:226) CREATE TEMPORARY
> TABLE IF NOT EXISTS TL_x_rms_resource_mapping (id BIGINT NOT NULL,
> change_timestamp
> DATETIME, hl_resource_id BIGINT, ll_resource_id BIGINT, PRIMARY KEY (id))
> 2022-05-11 07:19:12,543 [http-nio-6080-exec-3] ERROR
> n.s.l.Slf4jSpyLogDelegator (Slf4jSpyLogDelegator.java:111) 1.
> PreparedStatement.executeUpdate() CREATE TEMPORARY TABLE IF NOT EXISTS
> TL_x_rms_resource_mapping (id BIGINT NOT NULL, change_timestamp
> DATETIME, hl_resource_id BIGINT, ll_resource_id BIGINT, PRIMARY KEY (id))
> java.sql.SQLException: Statement violates GTID consistency: CREATE TEMPORARY
> TABLE and DROP TEMPORARY TABLE can only be executed outside transactional
> context. These statements are also not allowed in a function or trigger
> because functions and triggers are also considered to be multi-statement
> transactions.
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:998)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3835)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3771)
> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2435)
> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2582)
> ...
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:890)
> at
> org.apache.ranger.db.XXRMSServiceResourceDao.purge(XXRMSServiceResourceDao.java:248)
> at
> org.apache.ranger.biz.ServiceDBStore.deleteService(ServiceDBStore.java:1809)
> Error! Exception [EclipseLink-4002] (Eclipse Persistence Services -
> 2.5.2.v20140319-9ad6abd):
> org.eclipse.persistence.exceptions.DatabaseException Internal Exception:
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table
> 'ranger.tl_x_rms_resource_mapping' doesn't exist Error Code: 1146 Call:
> INSERT INTO TL_x_rms_resource_mapping (id) SELECT t0.id FROM
> x_rms_resource_mapping t0 WHERE (t0.hl_resource_id IN (SELECT t1.id FROM
> x_rms_service_resource t1 WHERE (t1.service_id = ?)) OR t0.ll_resource_id IN
> (SELECT t2.id FROM x_rms_service_resource t2 WHERE (t2.service_id = ?))) bind
> => [2 parameters bound] Query:
> DeleteAllQuery(name="XXRMSResourceMapping.deleteByServiceId"
> referenceClass=XXRMSResourceMapping sql="DELETE FROM
> TL_x_rms_resource_mapping")
> {code}
>
> Because CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed
> outside transactional context.
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (RANGER-3756) ranger SQL-transaction can not work with GTID-enabled mysql server
[
https://issues.apache.org/jira/browse/RANGER-3756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17690196#comment-17690196
]
kirby zhou edited comment on RANGER-3756 at 2/17/23 7:27 AM:
-
Reproduce steps:
# create a cloud mysql-5.7 instance on Tencent Cloud 【
[https://www.tencentcloud.com/products/cdb] 】
# setup a ranger admin with the mysql db
# use web browser to open ranger-admin site
# create a HDFS service 【You DONOT need a real hdfs cluster】
# delete the HDFS service
# error happens
!image-2023-02-17-15-23-46-271.png!
!image-2023-02-17-15-24-11-315.png!
Additional Info:
I can not reproduce the bug with my private MySQL-8 server with GTID=on;
was (Author: kirbyzhou):
Reproduce steps:
# create a cloud mysql-5.7 instance on Tencent Cloud
# setup a ranger admin with the mysql db
# use web browser to open ranger-admin site
# create a HDFS service 【You DONOT need a real hdfs cluster】
# delete the HDFS service
# error happens
!image-2023-02-17-15-23-46-271.png!
!image-2023-02-17-15-24-11-315.png!
Additional Info:
I can not reproduce the bug with my private MySQL-8 server with GTID=on;
> ranger SQL-transaction can not work with GTID-enabled mysql server
> --
>
> Key: RANGER-3756
> URL: https://issues.apache.org/jira/browse/RANGER-3756
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Reporter: kirby zhou
>Priority: Critical
> Attachments: image-2023-02-17-15-23-26-423.png,
> image-2023-02-17-15-23-46-271.png, image-2023-02-17-15-24-11-315.png
>
>
> A lot of cloud mysql service provider enable GTID_MODE by default.
> Such as TencentCloud, AliCloud, HuaWeiCloud.
> But ranger is not compatible with GTID_MODE.
> {code:java}
> 2022-05-11 07:19:12,533 [http-nio-6080-exec-3] INFO
> n.s.l.Slf4jSpyLogDelegator (Slf4jSpyLogDelegator.java:226) CREATE TEMPORARY
> TABLE IF NOT EXISTS TL_x_rms_resource_mapping (id BIGINT NOT NULL,
> change_timestamp
> DATETIME, hl_resource_id BIGINT, ll_resource_id BIGINT, PRIMARY KEY (id))
> 2022-05-11 07:19:12,543 [http-nio-6080-exec-3] ERROR
> n.s.l.Slf4jSpyLogDelegator (Slf4jSpyLogDelegator.java:111) 1.
> PreparedStatement.executeUpdate() CREATE TEMPORARY TABLE IF NOT EXISTS
> TL_x_rms_resource_mapping (id BIGINT NOT NULL, change_timestamp
> DATETIME, hl_resource_id BIGINT, ll_resource_id BIGINT, PRIMARY KEY (id))
> java.sql.SQLException: Statement violates GTID consistency: CREATE TEMPORARY
> TABLE and DROP TEMPORARY TABLE can only be executed outside transactional
> context. These statements are also not allowed in a function or trigger
> because functions and triggers are also considered to be multi-statement
> transactions.
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:998)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3835)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3771)
> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2435)
> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2582)
> ...
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:890)
> at
> org.apache.ranger.db.XXRMSServiceResourceDao.purge(XXRMSServiceResourceDao.java:248)
> at
> org.apache.ranger.biz.ServiceDBStore.deleteService(ServiceDBStore.java:1809)
> Error! Exception [EclipseLink-4002] (Eclipse Persistence Services -
> 2.5.2.v20140319-9ad6abd):
> org.eclipse.persistence.exceptions.DatabaseException Internal Exception:
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table
> 'ranger.tl_x_rms_resource_mapping' doesn't exist Error Code: 1146 Call:
> INSERT INTO TL_x_rms_resource_mapping (id) SELECT t0.id FROM
> x_rms_resource_mapping t0 WHERE (t0.hl_resource_id IN (SELECT t1.id FROM
> x_rms_service_resource t1 WHERE (t1.service_id = ?)) OR t0.ll_resource_id IN
> (SELECT t2.id FROM x_rms_service_resource t2 WHERE (t2.service_id = ?))) bind
> => [2 parameters bound] Query:
> DeleteAllQuery(name="XXRMSResourceMapping.deleteByServiceId"
> referenceClass=XXRMSResourceMapping sql="DELETE FROM
> TL_x_rms_resource_mapping")
> {code}
>
> Because CREATE TEMPORARY TABLE and DROP TEMPORARY TABLE can only be executed
> outside transactional context.
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
