[jira] [Created] (RANGER-4747) [docker]: Exception handling in create-ranger-services.py
Abhishek Kumar created RANGER-4747: -- Summary: [docker]: Exception handling in create-ranger-services.py Key: RANGER-4747 URL: https://issues.apache.org/jira/browse/RANGER-4747 Project: Ranger Issue Type: Bug Components: Ranger Affects Versions: 2.4.0 Reporter: Abhishek Kumar Assignee: Abhishek Kumar create-ranger-services.py creates ranger services after ranger is up in a docker container. If service creation for X fails, subsequent service creation is aborted, the jira aims to fix this behavior. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] RANGER-4747: Add exception handling in docker based service creation [ranger]
kumaab opened a new pull request, #300: URL: https://github.com/apache/ranger/pull/300 ## What changes were proposed in this pull request? create-ranger-services.py creates ranger services after ranger is up in a docker container. If service creation for hdfs fails, subsequent service creation is aborted, the PR aims to fix this behavior. ## How was this patch tested? Tested the changes by bringing up ranger in a container and below are the installation logs seen when only trino is packaged with ranger. (Please explain how this patch was tested. Ex: unit tests, manual tests) (If this patch involves UI changes, please attach a screen-shot; otherwise, remove this) https://github.com/apache/ranger/assets/16475454/a0b8effe-2fdf-4bea-a19e-f1c274b0784a";> -- 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
[PR] RANGER-4746: Fix ranger-jdk11 profile to only have the required modules [ranger]
kumaab opened a new pull request, #301: URL: https://github.com/apache/ranger/pull/301 ## What changes were proposed in this pull request? The ranger profile `ranger-jdk11` has been added to build trino with jdk 11 as currently trino plugin is the only plugin to have a compile time dependency on jdk 11. However, it currently builds the full ranger repo. The PR aims to fix this. When modules have a jdk 11 requirement they can be added to this profile. ## How was this patch tested? - Bring up the containers - Build with JDK 11: `mvn clean package -DskipTests -P ranger-jdk11` - `cp target/ranger-admin.tar.gz dev-support/ranger-docker/dist` - `cp target/ranger-trino-plugin.tar.gz dev-support/ranger-docker/dist/` - `cd dev-support/ranger-docker` - `docker-compose -f docker-compose.ranger.yml -f docker-compose.ranger-postgres.yml -f docker-compose.ranger-trino.yml build` - `docker-compose -f docker-compose.ranger.yml -f docker-compose.ranger-postgres.yml up -d` - `docker-compose -f docker-compose.ranger.yml -f docker-compose.ranger-postgres.yml -f docker-compose.ranger-trino.yml up -d` - Verified ranger and ranger-trino are successfully up in containers. - Verified ranger policy creation, policies created for trino are working. - Verified audits to Solr are visible in ranger UI. -- 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
Re: [PR] RANGER-4747: Add exception handling in docker based service creation [ranger]
mneethiraj merged PR #300: URL: https://github.com/apache/ranger/pull/300 -- 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] [Resolved] (RANGER-4747) [docker]: Exception handling in create-ranger-services.py
[ https://issues.apache.org/jira/browse/RANGER-4747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar resolved RANGER-4747. Fix Version/s: 3.0.0 Resolution: Fixed [Commit|https://github.com/apache/ranger/commit/05cba7318264691cbfec492fa26f8045aa340752] > [docker]: Exception handling in create-ranger-services.py > - > > Key: RANGER-4747 > URL: https://issues.apache.org/jira/browse/RANGER-4747 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 2.4.0 >Reporter: Abhishek Kumar >Assignee: Abhishek Kumar >Priority: Major > Fix For: 3.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > create-ranger-services.py creates ranger services after ranger is up in a > docker container. > If service creation for X fails, subsequent service creation is aborted, the > jira aims to fix this behavior. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (RANGER-4748) Admin audits UI is slow when x_trx_log table has large numer of rows
Madhan Neethiraj created RANGER-4748: Summary: Admin audits UI is slow when x_trx_log table has large numer of rows Key: RANGER-4748 URL: https://issues.apache.org/jira/browse/RANGER-4748 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Madhan Neethiraj Admin tab in Ranger audit UI lists changes performed on policies/users/groups/security-zones/service - one row for each object. Details of changes to an object (like old and new value of attributes) are available in a dialog box that pops up on clicking the row. API to retrieve list of admin audit log can take a long time when large number of rows exists in that database table that stores change details i.e. table named x_trx_log. This is due to the use of database view, vx_trx_log, on top of table x_trx_log, which performs a group-by operation that would require a full-table scan. This view is necessary since x_trx_log can have multiple rows for one change to an object - one row for each changed attribute. To avoid this issue, one option to consider is store changes to all attributes of an object in a single row (instead of one row per changed attribute). This will eliminate the need for a view that performs group by. CC: [~siddheshphatak] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (RANGER-4681) Audit logs for Mask & Row policy does not show policy condition under policy item
[ https://issues.apache.org/jira/browse/RANGER-4681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mugdha Varadkar updated RANGER-4681: Attachment: 0001-RANGER-4681.patch > Audit logs for Mask & Row policy does not show policy condition under policy > item > - > > Key: RANGER-4681 > URL: https://issues.apache.org/jira/browse/RANGER-4681 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Vishal Bhavsar >Assignee: Brijesh Bhalala >Priority: Major > Labels: ranger-react > Attachments: 0001-RANGER-4681.patch > > > Audit logs for Mask & Row policy does not show policy condition under policy > item. > > Steps to repro: > 1) Inside Hive service, navigate hive masking policy listing page. > 2) Click on "Add New Policy", add all the details. Under policy item section > add policy condition. Now save the policy > 3) Go to Audits, Admin page, click on the audit record of above newly policy. > One modal would be opened which show all the details for the policy > 4) Under "Row Level Filter Policy Items" section we would not see policy > condition details. -- This message was sent by Atlassian Jira (v8.20.10#820010)
