[jira] [Updated] (RANGER-4674) User Sync Audit shows wrong date in Sync Details for Last modified time on Ranger-admin UI
[
https://issues.apache.org/jira/browse/RANGER-4674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rakesh Gupta updated RANGER-4674:
-
Attachment: usersync-audit-screen.png
> User Sync Audit shows wrong date in Sync Details for Last modified time on
> Ranger-admin UI
> --
>
> Key: RANGER-4674
> URL: https://issues.apache.org/jira/browse/RANGER-4674
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Rakesh Gupta
>Assignee: Rakesh Gupta
>Priority: Major
> Attachments: usersync-audit-screen.png
>
>
> When a request is made to the (/assets/ugsyncAudits) and
> (/assets/ugsyncAudits/\{syncSource}) GET-API, in syncSourceInfo lastModified
> showing the wrong date of 1970.
> {code:java}
> "lastModified": "1970-01-01 00:00:00"
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4674) User Sync Audit shows wrong date in Sync Details for Last modified time on Ranger-admin UI
[
https://issues.apache.org/jira/browse/RANGER-4674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rakesh Gupta updated RANGER-4674:
-
Description:
When a request is made to the (/assets/ugsyncAudits) and
(/assets/ugsyncAudits/\{syncSource}) GET-API, in syncSourceInfo lastModified
showing the wrong date of 1970.
{code:java}
"lastModified": "1970-01-01 00:00:00"
{code}
was:
When a request is made to the (/assets/ugsyncAudits) and
(/assets/ugsyncAudits/\{syncSource}) GET-API, in syncSourceInfo lastModified
showing the wrong date of 1970.
"lastModified": "1970-01-01 00:00:00"
> User Sync Audit shows wrong date in Sync Details for Last modified time on
> Ranger-admin UI
> --
>
> Key: RANGER-4674
> URL: https://issues.apache.org/jira/browse/RANGER-4674
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Rakesh Gupta
>Assignee: Rakesh Gupta
>Priority: Major
>
> When a request is made to the (/assets/ugsyncAudits) and
> (/assets/ugsyncAudits/\{syncSource}) GET-API, in syncSourceInfo lastModified
> showing the wrong date of 1970.
> {code:java}
> "lastModified": "1970-01-01 00:00:00"
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] RANGER-4640: Trino ranger plugin for 433 snapshot [ranger]
shreyas-dview commented on PR #291: URL: https://github.com/apache/ranger/pull/291#issuecomment-1909439755 Give me some time over the weekend, will try to resolve the issues (if exists) or will answer them with proper explanation. -- 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-4674) User Sync Audit shows wrong date in Sync Details for Last modified time on Ranger-admin UI
[
https://issues.apache.org/jira/browse/RANGER-4674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rakesh Gupta updated RANGER-4674:
-
Description:
When a request is made to the (/assets/ugsyncAudits) and
(/assets/ugsyncAudits/\{syncSource}) GET-API, in syncSourceInfo lastModified
showing the wrong date of 1970.
"lastModified": "1970-01-01 00:00:00"
was:
When a request is made to the (/assets/ugsyncAudits) and
(/assets/ugsyncAudits/\{syncSource}) GET-API, in syncSourceInfo lastModified
showing the wrong date of 1970.
??"lastModified": "1970-01-01 00:00:00",??
> User Sync Audit shows wrong date in Sync Details for Last modified time on
> Ranger-admin UI
> --
>
> Key: RANGER-4674
> URL: https://issues.apache.org/jira/browse/RANGER-4674
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Rakesh Gupta
>Assignee: Rakesh Gupta
>Priority: Major
>
> When a request is made to the (/assets/ugsyncAudits) and
> (/assets/ugsyncAudits/\{syncSource}) GET-API, in syncSourceInfo lastModified
> showing the wrong date of 1970.
> "lastModified": "1970-01-01 00:00:00"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4674) User Sync Audit shows wrong date in Sync Details for Last modified time on Ranger-admin UI
[
https://issues.apache.org/jira/browse/RANGER-4674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rakesh Gupta updated RANGER-4674:
-
Description:
When a request is made to the (/assets/ugsyncAudits) and
(/assets/ugsyncAudits/\{syncSource}) GET-API, in syncSourceInfo lastModified
showing the wrong date of 1970.
??"lastModified": "1970-01-01 00:00:00",??
was:
When a request is made to the (/assets/ugsyncAudits) and
(/assets/ugsyncAudits/\{syncSource}) GET-API, in syncSourceInfo lastModified
showing the wrong date of 1970.
"lastModified": "1970-01-01 00:00:00",
> User Sync Audit shows wrong date in Sync Details for Last modified time on
> Ranger-admin UI
> --
>
> Key: RANGER-4674
> URL: https://issues.apache.org/jira/browse/RANGER-4674
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Rakesh Gupta
>Assignee: Rakesh Gupta
>Priority: Major
>
> When a request is made to the (/assets/ugsyncAudits) and
> (/assets/ugsyncAudits/\{syncSource}) GET-API, in syncSourceInfo lastModified
> showing the wrong date of 1970.
> ??"lastModified": "1970-01-01 00:00:00",??
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (RANGER-4674) User Sync Audit shows wrong date in Sync Details for Last modified time on Ranger-admin UI
Rakesh Gupta created RANGER-4674:
Summary: User Sync Audit shows wrong date in Sync Details for Last
modified time on Ranger-admin UI
Key: RANGER-4674
URL: https://issues.apache.org/jira/browse/RANGER-4674
Project: Ranger
Issue Type: Bug
Components: Ranger
Reporter: Rakesh Gupta
Assignee: Rakesh Gupta
When a request is made to the (/assets/ugsyncAudits) and
(/assets/ugsyncAudits/\{syncSource}) GET-API, in syncSourceInfo lastModified
showing the wrong date of 1970.
"lastModified": "1970-01-01 00:00:00",
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (RANGER-4361) Tag policy can be created with more than one tag resource through an API request
[
https://issues.apache.org/jira/browse/RANGER-4361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek reassigned RANGER-4361:
Assignee: Abhishek
> Tag policy can be created with more than one tag resource through an API
> request
>
>
> Key: RANGER-4361
> URL: https://issues.apache.org/jira/browse/RANGER-4361
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Abhishek
>Assignee: Abhishek
>Priority: Major
>
> {color:#172b4d}When creating a tag based policy through the UI, only one tag
> name is allowed {color}
> {color:#172b4d}in the tag policy resource section.{color}
> {color:#172b4d}But if an API request is made using a policy json with more
> than one tag in the resource section, the policy is created.{color}
> {color:#172b4d}Ideally, if the policy creation via UI is restricted for more
> than one tag, then the same check should be enforced for tag based policy
> creation through API requests{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (RANGER-4673) Pagination on the Ranger Admin - Plugin Status page
Dhaval Rajpara created RANGER-4673: -- Summary: Pagination on the Ranger Admin - Plugin Status page Key: RANGER-4673 URL: https://issues.apache.org/jira/browse/RANGER-4673 Project: Ranger Issue Type: Bug Components: Ranger Reporter: Dhaval Rajpara Assignee: Dhaval Rajpara The Ranger Admin UI's "Plugin Status" page does not offer pagination. The UI shows only (the first? random?) 200 entries, we have no way to go to next pages, and the ordering/sorting on columns is only a "client side" sorting so some entries cannot be seen easily. (only if we search by Host Name for example) This is a usability issue with bigger clusters. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4668) Need to have new local storage item for column show hide functionality in plugin status table
[ https://issues.apache.org/jira/browse/RANGER-4668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated RANGER-4668: Labels: ranger-react (was: ) > Need to have new local storage item for column show hide functionality in > plugin status table > -- > > Key: RANGER-4668 > URL: https://issues.apache.org/jira/browse/RANGER-4668 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: ranger-react > Fix For: 3.0.0 > > Attachments: 0001-RANGER-4668.patch > > > Need to have new local storage item for column show hide functionality in > plugin status table. > *Current Behaviour :-* > * The same local storage item is been used in both Access & Plugin Status > table for column show hide functionality , this causes regression in Access > Table column. > So need to make a new local storage item for column show hide functionality > in plugin status table. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4659) Add eye icon for password visibility in Ranger Login Page
[
https://issues.apache.org/jira/browse/RANGER-4659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brijesh Bhalala updated RANGER-4659:
Attachment: 0003-RANGER-4659.patch
> Add eye icon for password visibility in Ranger Login Page
> -
>
> Key: RANGER-4659
> URL: https://issues.apache.org/jira/browse/RANGER-4659
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
>Reporter: Brijesh Bhalala
>Assignee: Brijesh Bhalala
>Priority: Major
> Labels: ranger-react
> Fix For: 3.0.0
>
> Attachments: 0001-RANGER-4659.patch, 0002-RANGER-4659.patch,
> 0003-RANGER-4659.patch
>
>
> Add eye icon for password visibility in Ranger Login Page
> {*}Current Behaviour{*}:-
> * The Ranger login page doesn't have the password visibility functionality.
> * Users can't check the entered password, in case of wrong password.
> User should able to view the entered password by clicking on eye icon on
> password field in Ranger Login page.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (RANGER-4672) Tagsync log file name is not containing hostname and user
[ https://issues.apache.org/jira/browse/RANGER-4672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17810303#comment-17810303 ] Himanshu Maurya commented on RANGER-4672: - Hi, Kindly review this patch [https://reviews.apache.org/r/74854/] and merge it. Thanks & Regards > Tagsync log file name is not containing hostname and user > - > > Key: RANGER-4672 > URL: https://issues.apache.org/jira/browse/RANGER-4672 > Project: Ranger > Issue Type: Improvement > Components: Ranger, tagsync >Reporter: Himanshu Maurya >Assignee: Himanshu Maurya >Priority: Major > Fix For: 3.0.0 > > > Ranger admin and usersync logs file name is containing hostname and user but > tagsync is missing that -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4672) Tagsync log file name is not containing hostname and user
[ https://issues.apache.org/jira/browse/RANGER-4672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Himanshu Maurya updated RANGER-4672: Description: Ranger admin and usersync logs file name is containing hostname and user but tagsync is missing that > Tagsync log file name is not containing hostname and user > - > > Key: RANGER-4672 > URL: https://issues.apache.org/jira/browse/RANGER-4672 > Project: Ranger > Issue Type: Improvement > Components: Ranger, tagsync >Reporter: Himanshu Maurya >Assignee: Himanshu Maurya >Priority: Major > Fix For: 3.0.0 > > > Ranger admin and usersync logs file name is containing hostname and user but > tagsync is missing that -- This message was sent by Atlassian Jira (v8.20.10#820010)
Review Request 74854: RANGER-4672: Tagsync log file name is not containing hostname and user
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74854/ --- Review request for ranger, bhavik patel, Dhaval Shah, Dineshkumar Yadav, Harshal Chavan, Kishor Gollapalliwar, Madhan Neethiraj, Mehul Parikh, Nitin Galave, Pradeep Agrawal, and Velmurugan Periasamy. Bugs: RANGER-4672 https://issues.apache.org/jira/browse/RANGER-4672 Repository: ranger Description --- Ranger admin and usersync logs file name is containing hostname and user but tagsync is missing that Diffs - tagsync/conf.dist/logback.xml c1a94fee4 tagsync/scripts/ranger-tagsync-services.sh 460c4a130 Diff: https://reviews.apache.org/r/74854/diff/1/ Testing --- Checked the ranger-tagsync log files it is created with correct hostname and user Thanks, Himanshu Maurya
[jira] [Updated] (RANGER-4656) Filtering the resources in the search filter options on the policy listing page based on policy type.
[ https://issues.apache.org/jira/browse/RANGER-4656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated RANGER-4656: Attachment: (was: 0002-RANGER-4659.patch) > Filtering the resources in the search filter options on the policy listing > page based on policy type. > - > > Key: RANGER-4656 > URL: https://issues.apache.org/jira/browse/RANGER-4656 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: ranger-react > Fix For: 3.0.0 > > Attachments: 0001-RANGER-4656.patch > > > Filtering the resources in the search filter options on the policy listing > page based on policy type. > *Current Behaviour* :- > * All the resources are displayed in search filter options on policy listing > page, > * For masking and row level all resources are there in search filter option, > there is no filteration of resources on the basis of policy type. > The resources should be filter on the basis of policy type in search filter > options in policy listing page. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4659) Add eye icon for password visibility in Ranger Login Page
[
https://issues.apache.org/jira/browse/RANGER-4659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brijesh Bhalala updated RANGER-4659:
Attachment: 0002-RANGER-4659.patch
> Add eye icon for password visibility in Ranger Login Page
> -
>
> Key: RANGER-4659
> URL: https://issues.apache.org/jira/browse/RANGER-4659
> Project: Ranger
> Issue Type: Improvement
> Components: Ranger
>Reporter: Brijesh Bhalala
>Assignee: Brijesh Bhalala
>Priority: Major
> Labels: ranger-react
> Fix For: 3.0.0
>
> Attachments: 0001-RANGER-4659.patch, 0002-RANGER-4659.patch
>
>
> Add eye icon for password visibility in Ranger Login Page
> {*}Current Behaviour{*}:-
> * The Ranger login page doesn't have the password visibility functionality.
> * Users can't check the entered password, in case of wrong password.
> User should able to view the entered password by clicking on eye icon on
> password field in Ranger Login page.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (RANGER-4656) Filtering the resources in the search filter options on the policy listing page based on policy type.
[ https://issues.apache.org/jira/browse/RANGER-4656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brijesh Bhalala updated RANGER-4656: Attachment: 0002-RANGER-4659.patch > Filtering the resources in the search filter options on the policy listing > page based on policy type. > - > > Key: RANGER-4656 > URL: https://issues.apache.org/jira/browse/RANGER-4656 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Brijesh Bhalala >Assignee: Brijesh Bhalala >Priority: Major > Labels: ranger-react > Fix For: 3.0.0 > > Attachments: 0001-RANGER-4656.patch, 0002-RANGER-4659.patch > > > Filtering the resources in the search filter options on the policy listing > page based on policy type. > *Current Behaviour* :- > * All the resources are displayed in search filter options on policy listing > page, > * For masking and row level all resources are there in search filter option, > there is no filteration of resources on the basis of policy type. > The resources should be filter on the basis of policy type in search filter > options in policy listing page. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: Review Request 74844: RANGER-4663: New tag service will not be created if a tag service is selected while creating a resource service.
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/74844/#review226172 --- Ship it! Ship It! - Ankita Sinha On Jan. 18, 2024, 5:21 p.m., Siddhesh Phatak wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/74844/ > --- > > (Updated Jan. 18, 2024, 5:21 p.m.) > > > Review request for ranger, Anand Nadar, Ankita Sinha, Madhan Neethiraj, > Monika Kachhadiya, Prashant Satam, Subhrat Chaudhary, and Vanita Ubale. > > > Bugs: RANGER-4663 > https://issues.apache.org/jira/browse/RANGER-4663 > > > Repository: ranger > > > Description > --- > > If a tag service is selected while creating a resource service, a new tag > service should not be created for this resource service. This has been fixed > by adding the condition to check if user has selected tag service or not. > > > Diffs > - > > security-admin/src/main/java/org/apache/ranger/rest/ServiceREST.java > f9fd4941e > > > Diff: https://reviews.apache.org/r/74844/diff/1/ > > > Testing > --- > > Following cases have been tested and working as expected. > Case 1: > 1) Create a service in ranger > 2) Do not select tag service. > 3) A resource service will be created, a new tag service will also get > created and it will be linked to the resource service. > > Case 2: > 1) Create a resource service in ranger. > 2) Select a tag service for it. > 3) A resource service will get created, a new tag service will not get > created and the selected tag service will be linked to the resource service. > > > Thanks, > > Siddhesh Phatak > >
