[jira] [Comment Edited] (RANGER-2203) Review and update database schema for ranger policies to minimize database queries/updates

2018-10-16 Thread Pradeep Agrawal (JIRA) 


[ 
https://issues.apache.org/jira/browse/RANGER-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651789#comment-16651789
 ] 

Pradeep Agrawal edited comment on RANGER-2203 at 10/17/18 5:34 AM:
---

Steps required before applying the patch:

Before upgrading to code base of this patch(RANGER-2203) please take the backup 
of your current ranger database first. After taking the backup please delete 
‘DB_PATCHES’ and  ‘JAVA_PATCHES’ entry from *x_db_version_h* table of current 
ranger db.

To delete the entries please login to ranger db and execute the following sql 
command:
 * select max(id) *db_patch_id* from x_db_version_h where version='DB_PATCHES';
 * delete from x_db_version_h where id=<*db_patch_id*>

Here *db_patch_id* is the max row id of the 'DB_PATCHES' entry in 
x_db_version_h table for current ranger version.
 * select max(id) *java_patch_id* from x_db_version_h where 
version='JAVA_PATCHES';
 * delete from x_db_version_h where id=<*java_patch_id*>

Here *java_patch_id* is the max row id of the 'JAVA_PATCHES' entry in 
x_db_version_h table for current ranger version.

 


was (Author: pradeep.agrawal):
Steps required before applying the patch:

Before upgrading to the code base of this patch(RANGER-2203) please take the 
backup of your current ranger database first. After taking the backup please 
delete ‘DB_PATCHES’ and  ‘JAVA_PATCHES’ entry from *x_db_version_h* table of 
ranger db.

To delete the entries please login to ranger db and execute the following sql 
command:
 * delete from x_db_version_h where version in('DB_PATCHES','JAVA_PATCHES');

 

> Review and update database schema for ranger policies to minimize database 
> queries/updates
> --
>
> Key: RANGER-2203
> URL: https://issues.apache.org/jira/browse/RANGER-2203
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Affects Versions: 0.7.0, master
>Reporter: Abhay Kulkarni
>Assignee: Abhay Kulkarni
>Priority: Major
> Fix For: 0.7.2, 2.0.0
>
>
> Currently, ranger policies are fully normalized and stored in a multiple 
> Relational database tables. There is a performance overhead incurred when 
> retrieving a ranger policy, as multiple database accesses are required to 
> fully reconstruct it. This is significant when there are large ranger 
> policies (that is, the number of resources addressed by the policy is large), 
> and/or when there is a large number of ranger policies in an installation.
> This Jira tracks alternate design of database schema, where a policy is 
> stored in a de-normalized way, in its entirely, in one database table 
> (preferably as a JSON string).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Review Request 69040: RANGER-2229 : Perform graceful terminate with retries before doing forceful kill for usersync and tagsync

2018-10-16 Thread Mehul Parikh 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/69040/#review209674
---


Ship it!




Ship It!

- Mehul Parikh


On Oct. 16, 2018, 8:39 a.m., bhavik patel wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/69040/
> ---
> 
> (Updated Oct. 16, 2018, 8:39 a.m.)
> 
> 
> Review request for ranger, Ankita Sinha, Don Bosco Durai, Gautam Borad, Abhay 
> Kulkarni, Madhan Neethiraj, Pradeep Agrawal, Ramesh Mani, Selvamohan 
> Neethiraj, Sailaja Polavarapu, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-2229
> https://issues.apache.org/jira/browse/RANGER-2229
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Currently ranger-tagsync-services.sh /ranger-usersync-services.sh are not 
> identical to ranger-admin-service.sh while service is already stopped.
> 
> 
> Diffs
> -
> 
>   tagsync/scripts/ranger-tagsync-services.sh a4ad7b1 
>   unixauthservice/scripts/ranger-usersync-services.sh 476aa0c 
> 
> 
> Diff: https://reviews.apache.org/r/69040/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> bhavik patel
> 
>

Re: Review Request 69040: RANGER-2229 : Perform graceful terminate with retries before doing forceful kill for usersync and tagsync

2018-10-16 Thread bhavik patel 


> On Oct. 16, 2018, 1:51 p.m., Velmurugan Periasamy wrote:
> > tagsync/scripts/ranger-tagsync-services.sh
> > Line 84 (original), 84 (patched)
> > 
> >
> > Could you please make sure that this is merged in 1.x lines? Thanks.

Yes Vel, patch is applying on ranger-1 line branches.


- bhavik


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/69040/#review209619
---


On Oct. 16, 2018, 8:39 a.m., bhavik patel wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/69040/
> ---
> 
> (Updated Oct. 16, 2018, 8:39 a.m.)
> 
> 
> Review request for ranger, Ankita Sinha, Don Bosco Durai, Gautam Borad, Abhay 
> Kulkarni, Madhan Neethiraj, Pradeep Agrawal, Ramesh Mani, Selvamohan 
> Neethiraj, Sailaja Polavarapu, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-2229
> https://issues.apache.org/jira/browse/RANGER-2229
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Currently ranger-tagsync-services.sh /ranger-usersync-services.sh are not 
> identical to ranger-admin-service.sh while service is already stopped.
> 
> 
> Diffs
> -
> 
>   tagsync/scripts/ranger-tagsync-services.sh a4ad7b1 
>   unixauthservice/scripts/ranger-usersync-services.sh 476aa0c 
> 
> 
> Diff: https://reviews.apache.org/r/69040/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> bhavik patel
> 
>

[jira] [Updated] (RANGER-2253) Unable to get dashboard page after login

2018-10-16 Thread Pradeep Agrawal (JIRA) 


 [ 
https://issues.apache.org/jira/browse/RANGER-2253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pradeep Agrawal updated RANGER-2253:

Description: 
After login I am not getting Ranger dashboard and this page is coming:
!Screen Shot 2018-10-17 at 5.00.45 AM.png!

> Unable to get dashboard page after login
> 
>
> Key: RANGER-2253
> URL: https://issues.apache.org/jira/browse/RANGER-2253
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Affects Versions: 0.7.2
>Reporter: Pradeep Agrawal
>Assignee: Pradeep Agrawal
>Priority: Blocker
> Fix For: 0.7.2
>
> Attachments: Screen Shot 2018-10-17 at 5.00.45 AM.png
>
>
> After login I am not getting Ranger dashboard and this page is coming:
> !Screen Shot 2018-10-17 at 5.00.45 AM.png!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (RANGER-2253) Unable to get dashboard page after login

2018-10-16 Thread Pradeep Agrawal (JIRA) 


 [ 
https://issues.apache.org/jira/browse/RANGER-2253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pradeep Agrawal updated RANGER-2253:

Attachment: Screen Shot 2018-10-17 at 5.00.45 AM.png

> Unable to get dashboard page after login
> 
>
> Key: RANGER-2253
> URL: https://issues.apache.org/jira/browse/RANGER-2253
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Affects Versions: 0.7.2
>Reporter: Pradeep Agrawal
>Assignee: Pradeep Agrawal
>Priority: Blocker
> Fix For: 0.7.2
>
> Attachments: Screen Shot 2018-10-17 at 5.00.45 AM.png
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (RANGER-2253) Unable to get dashboard page after login

2018-10-16 Thread Pradeep Agrawal (JIRA) 
Pradeep Agrawal created RANGER-2253:
---

 Summary: Unable to get dashboard page after login
 Key: RANGER-2253
 URL: https://issues.apache.org/jira/browse/RANGER-2253
 Project: Ranger
  Issue Type: Bug
  Components: Ranger
Affects Versions: 0.7.2
Reporter: Pradeep Agrawal
Assignee: Pradeep Agrawal
 Fix For: 0.7.2






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (RANGER-2209) Service Definition for ABFS to support Ranger Authorization

2018-10-16 Thread Velmurugan Periasamy (JIRA) 


 [ 
https://issues.apache.org/jira/browse/RANGER-2209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Velmurugan Periasamy reassigned RANGER-2209:


Assignee: Yuan Gao

> Service Definition for ABFS to support Ranger Authorization
> ---
>
> Key: RANGER-2209
> URL: https://issues.apache.org/jira/browse/RANGER-2209
> Project: Ranger
>  Issue Type: New Feature
>  Components: Ranger
>Affects Versions: 0.7.0, master
>Reporter: Yuan Gao
>Assignee: Yuan Gao
>Priority: Major
> Fix For: 0.7.2, 2.0.0, 1.1.1, 1.2.1
>
> Attachments: RANGER-2209-001.patch, RANGER-2209-002.patch
>
>
> This is to add Service Definition for Azure Blob File System (ABFS) in Ranger 
> Authorization. This will give an option to add ABFS as a Service in the 
> Ranger.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (RANGER-2209) Service Definition for ABFS to support Ranger Authorization

2018-10-16 Thread Velmurugan Periasamy (JIRA) 


[ 
https://issues.apache.org/jira/browse/RANGER-2209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16652628#comment-16652628
 ] 

Velmurugan Periasamy commented on RANGER-2209:
--

Patch committed. [~kowon2008] - thanks for the contribution and [~rmani] - 
thanks for the review.

master - 
[https://git-wip-us.apache.org/repos/asf?p=ranger.git;a=commit;h=db7e261448411eabe233bf34631ea209ab6a42bb]

ranger-1 - 
[https://git-wip-us.apache.org/repos/asf?p=ranger.git;a=commit;h=883f6bf3d07ff7845a0a2ed0e6eabc70e7cd994a]
 

ranger-1.2 - 
[https://git-wip-us.apache.org/repos/asf?p=ranger.git;a=commit;h=77aa4abf63020905ba6ed33342832c0e061a375c]
 

ranger-1.1 - 
[https://git-wip-us.apache.org/repos/asf?p=ranger.git;a=commit;h=9e783c5b0a3634e9781c50f641ccbd88d6033297]

ranger-0.7 - 
[https://git-wip-us.apache.org/repos/asf?p=ranger.git;a=commit;h=63ed5feb116d789ee827c7577e6d93267860c4ef]
 

> Service Definition for ABFS to support Ranger Authorization
> ---
>
> Key: RANGER-2209
> URL: https://issues.apache.org/jira/browse/RANGER-2209
> Project: Ranger
>  Issue Type: New Feature
>  Components: Ranger
>Affects Versions: 0.7.0, master
>Reporter: Yuan Gao
>Priority: Major
> Fix For: 0.7.2, 2.0.0, 1.1.1, 1.2.1
>
> Attachments: RANGER-2209-001.patch, RANGER-2209-002.patch
>
>
> This is to add Service Definition for Azure Blob File System (ABFS) in Ranger 
> Authorization. This will give an option to add ABFS as a Service in the 
> Ranger.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (RANGER-2209) Service Definition for ABFS to support Ranger Authorization

2018-10-16 Thread Velmurugan Periasamy (JIRA) 


 [ 
https://issues.apache.org/jira/browse/RANGER-2209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Velmurugan Periasamy updated RANGER-2209:
-
Fix Version/s: (was: 1.0.1)

> Service Definition for ABFS to support Ranger Authorization
> ---
>
> Key: RANGER-2209
> URL: https://issues.apache.org/jira/browse/RANGER-2209
> Project: Ranger
>  Issue Type: New Feature
>  Components: Ranger
>Affects Versions: 0.7.0, master
>Reporter: Yuan Gao
>Priority: Major
> Fix For: 0.7.2, 2.0.0, 1.1.1, 1.2.1
>
> Attachments: RANGER-2209-001.patch, RANGER-2209-002.patch
>
>
> This is to add Service Definition for Azure Blob File System (ABFS) in Ranger 
> Authorization. This will give an option to add ABFS as a Service in the 
> Ranger.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (RANGER-2209) Service Definition for ABFS to support Ranger Authorization

2018-10-16 Thread Yuan Gao (JIRA) 


[ 
https://issues.apache.org/jira/browse/RANGER-2209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16652429#comment-16652429
 ] 

Yuan Gao commented on RANGER-2209:
--

For ranger-0.7: [https://reviews.apache.org/r/68418/] (This is patch 001)

For master and 1.x lines: [https://reviews.apache.org/r/69056/] (This is patch 
002)

> Service Definition for ABFS to support Ranger Authorization
> ---
>
> Key: RANGER-2209
> URL: https://issues.apache.org/jira/browse/RANGER-2209
> Project: Ranger
>  Issue Type: New Feature
>  Components: Ranger
>Affects Versions: 0.7.0, master
>Reporter: Yuan Gao
>Priority: Major
> Fix For: 0.7.2, 1.0.1, 2.0.0, 1.1.1, 1.2.1
>
> Attachments: RANGER-2209-001.patch, RANGER-2209-002.patch
>
>
> This is to add Service Definition for Azure Blob File System (ABFS) in Ranger 
> Authorization. This will give an option to add ABFS as a Service in the 
> Ranger.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Review Request 69027: RANGER-2250-Service configs fields are not showing for atlas service form page

2018-10-16 Thread Abhay Kulkarni 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/69027/#review209655
---


Ship it!




Ship It!

- Abhay Kulkarni


On Oct. 16, 2018, 12:56 p.m., Nitin Galave wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/69027/
> ---
> 
> (Updated Oct. 16, 2018, 12:56 p.m.)
> 
> 
> Review request for ranger, Abhay Kulkarni, Mehul Parikh, Pradeep Agrawal, and 
> Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-2250
> https://issues.apache.org/jira/browse/RANGER-2250
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Service configs  fields are not showing for atlas service form page.
> 
> 
> Diffs
> -
> 
>   security-admin/src/main/webapp/scripts/models/BackboneFormDataType.js 
> 22a418d 
> 
> 
> Diff: https://reviews.apache.org/r/69027/diff/2/
> 
> 
> Testing
> ---
> 
> 1)Able to see configs field in service create/edit page. 
> 2)Tested Service CRUD on working as expected.
> 
> 
> Thanks,
> 
> Nitin Galave
> 
>

Re: Review Request 69027: RANGER-2250-Service configs fields are not showing for atlas service form page

2018-10-16 Thread Velmurugan Periasamy 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/69027/#review209651
---


Ship it!




Ship It!

- Velmurugan Periasamy


On Oct. 16, 2018, 12:56 p.m., Nitin Galave wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/69027/
> ---
> 
> (Updated Oct. 16, 2018, 12:56 p.m.)
> 
> 
> Review request for ranger, Abhay Kulkarni, Mehul Parikh, Pradeep Agrawal, and 
> Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-2250
> https://issues.apache.org/jira/browse/RANGER-2250
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Service configs  fields are not showing for atlas service form page.
> 
> 
> Diffs
> -
> 
>   security-admin/src/main/webapp/scripts/models/BackboneFormDataType.js 
> 22a418d 
> 
> 
> Diff: https://reviews.apache.org/r/69027/diff/2/
> 
> 
> Testing
> ---
> 
> 1)Able to see configs field in service create/edit page. 
> 2)Tested Service CRUD on working as expected.
> 
> 
> Thanks,
> 
> Nitin Galave
> 
>

Review Request 69051: RANGER-2252:Permission "Kafka Admin" should not be part of Topic resource in Ranger Kafka resource definition

2018-10-16 Thread Ramesh Mani 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/69051/
---

Review request for ranger, Abhay Kulkarni, Madhan Neethiraj, and Velmurugan 
Periasamy.


Bugs: RANGER-2252
https://issues.apache.org/jira/browse/RANGER-2252


Repository: ranger


Description
---

RANGER-2252:Permission "Kafka Admin" should not be part of Topic resource in 
Ranger Kafka resource definition


Diffs
-

  agents-common/src/main/resources/service-defs/ranger-servicedef-kafka.json 
78ae9ea 


Diff: https://reviews.apache.org/r/69051/diff/1/


Testing
---

Tested in local VM


Thanks,

Ramesh Mani

[jira] [Updated] (RANGER-2252) Permission "Kafka Admin" should not be part of Topic resource in Ranger Kafka resource definition

2018-10-16 Thread Ramesh Mani (JIRA) 


 [ 
https://issues.apache.org/jira/browse/RANGER-2252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ramesh Mani updated RANGER-2252:

Attachment: 0001-RANGER-2252-Permission-Kafka-Admin-should-not-be-par.patch

> Permission "Kafka Admin" should not be part of Topic resource in Ranger Kafka 
> resource definition 
> --
>
> Key: RANGER-2252
> URL: https://issues.apache.org/jira/browse/RANGER-2252
> Project: Ranger
>  Issue Type: Bug
>  Components: Ranger
>Affects Versions: master, 2.0.0
>Reporter: Ramesh Mani
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: 
> 0001-RANGER-2252-Permission-Kafka-Admin-should-not-be-par.patch
>
>
> Permission "Kafka Admin" should not be part of Topic resource in Ranger Kafka 
> resource definition. Only "Cluster" resource should be having this permission.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (RANGER-2252) Permission "Kafka Admin" should not be part of Topic resource in Ranger Kafka resource definition

2018-10-16 Thread Ramesh Mani (JIRA) 
Ramesh Mani created RANGER-2252:
---

 Summary: Permission "Kafka Admin" should not be part of Topic 
resource in Ranger Kafka resource definition 
 Key: RANGER-2252
 URL: https://issues.apache.org/jira/browse/RANGER-2252
 Project: Ranger
  Issue Type: Bug
  Components: Ranger
Affects Versions: master, 2.0.0
Reporter: Ramesh Mani
 Fix For: 2.0.0


Permission "Kafka Admin" should not be part of Topic resource in Ranger Kafka 
resource definition. Only "Cluster" resource should be having this permission.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (RANGER-2203) Review and update database schema for ranger policies to minimize database queries/updates

2018-10-16 Thread Pradeep Agrawal (JIRA) 


[ 
https://issues.apache.org/jira/browse/RANGER-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651789#comment-16651789
 ] 

Pradeep Agrawal commented on RANGER-2203:
-

Steps required before applying the patch:

Before upgrading to the code base of this patch(RANGER-2203) please take the 
backup of your current ranger database first. After taking the backup please 
delete ‘DB_PATCHES’ and  ‘JAVA_PATCHES’ entry from *x_db_version_h* table of 
ranger db.

To delete the entries please login to ranger db and execute the following sql 
command:
 * delete from x_db_version_h where version in('DB_PATCHES','JAVA_PATCHES');

 

> Review and update database schema for ranger policies to minimize database 
> queries/updates
> --
>
> Key: RANGER-2203
> URL: https://issues.apache.org/jira/browse/RANGER-2203
> Project: Ranger
>  Issue Type: Improvement
>  Components: Ranger
>Affects Versions: 0.7.0, master
>Reporter: Abhay Kulkarni
>Assignee: Abhay Kulkarni
>Priority: Major
> Fix For: 0.7.2, 2.0.0
>
>
> Currently, ranger policies are fully normalized and stored in a multiple 
> Relational database tables. There is a performance overhead incurred when 
> retrieving a ranger policy, as multiple database accesses are required to 
> fully reconstruct it. This is significant when there are large ranger 
> policies (that is, the number of resources addressed by the policy is large), 
> and/or when there is a large number of ranger policies in an installation.
> This Jira tracks alternate design of database schema, where a policy is 
> stored in a de-normalized way, in its entirely, in one database table 
> (preferably as a JSON string).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Review Request 69027: RANGER-2250-Service configs fields are not showing for atlas service form page

2018-10-16 Thread Mehul Parikh 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/69027/#review209622
---


Ship it!




Ship It!

- Mehul Parikh


On Oct. 16, 2018, 12:56 p.m., Nitin Galave wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/69027/
> ---
> 
> (Updated Oct. 16, 2018, 12:56 p.m.)
> 
> 
> Review request for ranger, Abhay Kulkarni, Mehul Parikh, Pradeep Agrawal, and 
> Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-2250
> https://issues.apache.org/jira/browse/RANGER-2250
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Service configs  fields are not showing for atlas service form page.
> 
> 
> Diffs
> -
> 
>   security-admin/src/main/webapp/scripts/models/BackboneFormDataType.js 
> 22a418d 
> 
> 
> Diff: https://reviews.apache.org/r/69027/diff/2/
> 
> 
> Testing
> ---
> 
> 1)Able to see configs field in service create/edit page. 
> 2)Tested Service CRUD on working as expected.
> 
> 
> Thanks,
> 
> Nitin Galave
> 
>

Re: Review Request 69040: RANGER-2229 : Perform graceful terminate with retries before doing forceful kill for usersync and tagsync

2018-10-16 Thread Velmurugan Periasamy 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/69040/#review209619
---


Fix it, then Ship it!





tagsync/scripts/ranger-tagsync-services.sh
Line 84 (original), 84 (patched)


Could you please make sure that this is merged in 1.x lines? Thanks.


- Velmurugan Periasamy


On Oct. 16, 2018, 8:39 a.m., bhavik patel wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/69040/
> ---
> 
> (Updated Oct. 16, 2018, 8:39 a.m.)
> 
> 
> Review request for ranger, Ankita Sinha, Don Bosco Durai, Gautam Borad, Abhay 
> Kulkarni, Madhan Neethiraj, Pradeep Agrawal, Ramesh Mani, Selvamohan 
> Neethiraj, Sailaja Polavarapu, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-2229
> https://issues.apache.org/jira/browse/RANGER-2229
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Currently ranger-tagsync-services.sh /ranger-usersync-services.sh are not 
> identical to ranger-admin-service.sh while service is already stopped.
> 
> 
> Diffs
> -
> 
>   tagsync/scripts/ranger-tagsync-services.sh a4ad7b1 
>   unixauthservice/scripts/ranger-usersync-services.sh 476aa0c 
> 
> 
> Diff: https://reviews.apache.org/r/69040/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> bhavik patel
> 
>

Re: Review Request 69027: RANGER-2250-Service configs fields are not showing for atlas service form page

2018-10-16 Thread Nitin Galave 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/69027/
---

(Updated Oct. 16, 2018, 12:56 p.m.)


Review request for ranger, Abhay Kulkarni, Mehul Parikh, Pradeep Agrawal, and 
Velmurugan Periasamy.


Changes
---

Modified changes.


Bugs: RANGER-2250
https://issues.apache.org/jira/browse/RANGER-2250


Repository: ranger


Description
---

Service configs  fields are not showing for atlas service form page.


Diffs (updated)
-

  security-admin/src/main/webapp/scripts/models/BackboneFormDataType.js 22a418d 


Diff: https://reviews.apache.org/r/69027/diff/2/

Changes: https://reviews.apache.org/r/69027/diff/1-2/


Testing
---

1)Able to see configs field in service create/edit page. 
2)Tested Service CRUD on working as expected.


Thanks,

Nitin Galave

Re: Review Request 69028: RANGER-2234 : Cannot add or update a child row, a foreign key constraint fails when installing ranger-admin

2018-10-16 Thread Akash Pawale 


> On Oct. 15, 2018, 2:26 p.m., Pradeep Agrawal wrote:
> > security-admin/db/mysql/patches/013-permissionmodel.sql
> > Line 28 (original), 28 (patched)
> > 
> >
> > try removing hard-coding of ID's from this table also.

hard-coding of ID's removed from x_modules_master


- Akash


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/69028/#review209544
---


On Oct. 16, 2018, 9:07 a.m., Akash Pawale wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/69028/
> ---
> 
> (Updated Oct. 16, 2018, 9:07 a.m.)
> 
> 
> Review request for ranger, Ankita Sinha, Don Bosco Durai, Gautam Borad, Abhay 
> Kulkarni, Madhan Neethiraj, Mehul Parikh, Pradeep Agrawal, Ramesh Mani, 
> Selvamohan Neethiraj, Sailaja Polavarapu, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-2234
> https://issues.apache.org/jira/browse/RANGER-2234
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Installing ranger-admin use mysql as the database,execute setup.sh, in 
> progress something happend, the error logs are as flowing:
> 
> 2018-09-26 17:17:08,539 [I] Importing db schema to database ranger from file: 
> ranger_core_db_mysql.sql
> 2018-09-26 17:17:08,540 [JISQL] /home/ranger/jdk1.8.0_121/bin/java -cp 
> /usr/share/java/mysql-connector-java.jar:/home/ranger/ranger-1.1.0-admin/jisql/lib/*
>  org.apache.util.sql.Jisql -driver mysqlconj -cstring 
> jdbc:mysql://10.139.16.75/ranger -u 'root' -p '' -noheader -trim -c 
> \; -input 
> /home/ranger/ranger-1.1.0-admin/db/mysql/optimized/current/ranger_core_db_mysql.sql
> Error executing: INSERT INTO 
> x_portal_user_role(create_time,update_time,added_by_id,upd_by_id,user_id,user_role,status)
>  VALUES (UTC_TIMESTAMP(),UTC_TIMESTAMP(),NULL,NULL,2,'ROLE_SYS_ADMIN',1); 
> com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: 
> Cannot add or update a child row: a foreign key constraint fails 
> (`ranger`.`x_portal_user_role`, CONSTRAINT `x_portal_user_role_FK_user_id` 
> FOREIGN KEY (`user_id`) REFERENCES `x_portal_user` (`id`))
> SQLException : SQL state: 23000 
> com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: 
> Cannot add or update a child row: a foreign key constraint fails 
> (`ranger`.`x_portal_user_role`, CONSTRAINT `x_portal_user_role_FK_user_id` 
> FOREIGN KEY (`user_id`) REFERENCES `x_portal_user` (`id`)) ErrorCode: 1452
> 2018-09-26 17:22:20,882 [E] ranger_core_db_mysql.sql file import failed!
> 
> 
> Diffs
> -
> 
>   security-admin/db/mysql/optimized/current/ranger_core_db_mysql.sql 32cf6db 
>   security-admin/db/mysql/patches/013-permissionmodel.sql 381bb6f 
>   security-admin/db/oracle/optimized/current/ranger_core_db_oracle.sql 
> 2e577f3 
>   security-admin/db/oracle/patches/013-permissionmodel.sql 4ac7901 
>   
> security-admin/db/oracle/patches/016-updated-schema-for-tag-based-policy.sql 
> 12627f5 
>   security-admin/db/postgres/optimized/current/ranger_core_db_postgres.sql 
> bad32ef 
>   
> security-admin/db/sqlanywhere/optimized/current/ranger_core_db_sqlanywhere.sql
>  9482992 
>   security-admin/db/sqlserver/optimized/current/ranger_core_db_sqlserver.sql 
> 85f3285 
>   
> security-admin/db/sqlserver/patches/016-updated-schema-for-tag-based-policy.sql
>  4b856d7 
> 
> 
> Diff: https://reviews.apache.org/r/69028/diff/2/
> 
> 
> Testing
> ---
> 
> Done testing for all Db flavors
> DB_FLAVOR=MYSQL|ORACLE|POSTGRES|MSSQL|SQLA
> 
> ranger_core_db_mysql.sql, ranger_core_db_sqlserver.sql, 
> ranger_core_db_oracle.sql, ranger_core_db_postgres.sql, 
> ranger_core_db_sqlanywhere.sql files importing successfully.
> 
> 
> Thanks,
> 
> Akash Pawale
> 
>

Re: Review Request 69028: RANGER-2234 : Cannot add or update a child row, a foreign key constraint fails when installing ranger-admin

2018-10-16 Thread Akash Pawale 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/69028/
---

(Updated Oct. 16, 2018, 9:07 a.m.)


Review request for ranger, Ankita Sinha, Don Bosco Durai, Gautam Borad, Abhay 
Kulkarni, Madhan Neethiraj, Mehul Parikh, Pradeep Agrawal, Ramesh Mani, 
Selvamohan Neethiraj, Sailaja Polavarapu, and Velmurugan Periasamy.


Bugs: RANGER-2234
https://issues.apache.org/jira/browse/RANGER-2234


Repository: ranger


Description
---

Installing ranger-admin use mysql as the database,execute setup.sh, in progress 
something happend, the error logs are as flowing:

2018-09-26 17:17:08,539 [I] Importing db schema to database ranger from file: 
ranger_core_db_mysql.sql
2018-09-26 17:17:08,540 [JISQL] /home/ranger/jdk1.8.0_121/bin/java -cp 
/usr/share/java/mysql-connector-java.jar:/home/ranger/ranger-1.1.0-admin/jisql/lib/*
 org.apache.util.sql.Jisql -driver mysqlconj -cstring 
jdbc:mysql://10.139.16.75/ranger -u 'root' -p '' -noheader -trim -c \; 
-input 
/home/ranger/ranger-1.1.0-admin/db/mysql/optimized/current/ranger_core_db_mysql.sql
Error executing: INSERT INTO 
x_portal_user_role(create_time,update_time,added_by_id,upd_by_id,user_id,user_role,status)
 VALUES (UTC_TIMESTAMP(),UTC_TIMESTAMP(),NULL,NULL,2,'ROLE_SYS_ADMIN',1); 
com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: 
Cannot add or update a child row: a foreign key constraint fails 
(`ranger`.`x_portal_user_role`, CONSTRAINT `x_portal_user_role_FK_user_id` 
FOREIGN KEY (`user_id`) REFERENCES `x_portal_user` (`id`))
SQLException : SQL state: 23000 
com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: 
Cannot add or update a child row: a foreign key constraint fails 
(`ranger`.`x_portal_user_role`, CONSTRAINT `x_portal_user_role_FK_user_id` 
FOREIGN KEY (`user_id`) REFERENCES `x_portal_user` (`id`)) ErrorCode: 1452
2018-09-26 17:22:20,882 [E] ranger_core_db_mysql.sql file import failed!


Diffs (updated)
-

  security-admin/db/mysql/optimized/current/ranger_core_db_mysql.sql 32cf6db 
  security-admin/db/mysql/patches/013-permissionmodel.sql 381bb6f 
  security-admin/db/oracle/optimized/current/ranger_core_db_oracle.sql 2e577f3 
  security-admin/db/oracle/patches/013-permissionmodel.sql 4ac7901 
  security-admin/db/oracle/patches/016-updated-schema-for-tag-based-policy.sql 
12627f5 
  security-admin/db/postgres/optimized/current/ranger_core_db_postgres.sql 
bad32ef 
  
security-admin/db/sqlanywhere/optimized/current/ranger_core_db_sqlanywhere.sql 
9482992 
  security-admin/db/sqlserver/optimized/current/ranger_core_db_sqlserver.sql 
85f3285 
  
security-admin/db/sqlserver/patches/016-updated-schema-for-tag-based-policy.sql 
4b856d7 


Diff: https://reviews.apache.org/r/69028/diff/2/

Changes: https://reviews.apache.org/r/69028/diff/1-2/


Testing
---

Done testing for all Db flavors
DB_FLAVOR=MYSQL|ORACLE|POSTGRES|MSSQL|SQLA

ranger_core_db_mysql.sql, ranger_core_db_sqlserver.sql, 
ranger_core_db_oracle.sql, ranger_core_db_postgres.sql, 
ranger_core_db_sqlanywhere.sql files importing successfully.


Thanks,

Akash Pawale

[jira] [Created] (RANGER-2251) Need to provide options for making java heap size memory configurable in Ranger services

2018-10-16 Thread Vishal Suvagia (JIRA) 
Vishal Suvagia created RANGER-2251:
--

 Summary: Need to provide options for making java heap size memory 
configurable in Ranger services
 Key: RANGER-2251
 URL: https://issues.apache.org/jira/browse/RANGER-2251
 Project: Ranger
  Issue Type: Bug
  Components: Ranger
Affects Versions: 1.2.0
Reporter: Vishal Suvagia
Assignee: Vishal Suvagia
 Fix For: 2.0.0


Need to make java heap size memory configurable for Ranger services.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (RANGER-2234) Cannot add or update a child row,a foreign key constraint fails when installing ranger-admin

2018-10-16 Thread Akash Pawale (JIRA) 


 [ 
https://issues.apache.org/jira/browse/RANGER-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Akash Pawale updated RANGER-2234:
-
Attachment: RANGER-2234-01.patch

> Cannot add or update a child row,a foreign key constraint fails when 
> installing ranger-admin
> 
>
> Key: RANGER-2234
> URL: https://issues.apache.org/jira/browse/RANGER-2234
> Project: Ranger
>  Issue Type: Bug
>  Components: admin, Ranger
>Affects Versions: 1.1.0
>Reporter: Haihui Xu
>Assignee: Akash Pawale
>Priority: Major
>  Labels: patch
> Fix For: 2.0.0
>
> Attachments: RANGER-2234-01.patch, RANGER-2234_Cannot add or update a 
> child row,a foreign key constraint fails when installing ranger-admin.patch
>
>
> Installing ranger-admin use mysql as the database,execute setup.sh, in 
> progress something happend, the error logs are as flowing:
> 2018-09-26 17:17:08,539 [I] Table xa_access_audit does not exist in database 
> ranger
> 2018-09-26 17:17:08,539 [I] Importing db schema to database ranger from file: 
> ranger_core_db_mysql.sql
> 2018-09-26 17:17:08,540 [JISQL] /home/ranger/jdk1.8.0_121/bin/java -cp 
> /usr/share/java/mysql-connector-java.jar:/home/ranger/ranger-1.1.0-admin/jisql/lib/*
>  org.apache.util.sql.Jisql -driver mysqlconj -cstring 
> jdbc:mysql://10.139.16.75/ranger -u 'root' -p '' -noheader -trim -c 
> \; -input 
> /home/ranger/ranger-1.1.0-admin/db/mysql/optimized/current/ranger_core_db_mysql.sql
> Error executing: INSERT INTO 
> x_portal_user_role(create_time,update_time,added_by_id,upd_by_id,user_id,user_role,status)
>  VALUES (UTC_TIMESTAMP(),UTC_TIMESTAMP(),NULL,NULL,2,'ROLE_SYS_ADMIN',1); 
> com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: 
> Cannot add or update a child row: a foreign key constraint fails 
> (`ranger`.`x_portal_user_role`, CONSTRAINT `x_portal_user_role_FK_user_id` 
> FOREIGN KEY (`user_id`) REFERENCES `x_portal_user` (`id`))
> SQLException : SQL state: 23000 
> com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: 
> Cannot add or update a child row: a foreign key constraint fails 
> (`ranger`.`x_portal_user_role`, CONSTRAINT `x_portal_user_role_FK_user_id` 
> FOREIGN KEY (`user_id`) REFERENCES `x_portal_user` (`id`)) ErrorCode: 1452
> 2018-09-26 17:22:20,882 [E] ranger_core_db_mysql.sql file import failed!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Review Request 69040: RANGER-2229 : Perform graceful terminate with retries before doing forceful kill for usersync and tagsync

2018-10-16 Thread bhavik patel 

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/69040/
---

Review request for ranger, Ankita Sinha, Don Bosco Durai, Gautam Borad, Abhay 
Kulkarni, Madhan Neethiraj, Pradeep Agrawal, Ramesh Mani, Selvamohan Neethiraj, 
Sailaja Polavarapu, and Velmurugan Periasamy.


Bugs: RANGER-2229
https://issues.apache.org/jira/browse/RANGER-2229


Repository: ranger


Description
---

Currently ranger-tagsync-services.sh /ranger-usersync-services.sh are not 
identical to ranger-admin-service.sh while service is already stopped.


Diffs
-

  tagsync/scripts/ranger-tagsync-services.sh a4ad7b1 
  unixauthservice/scripts/ranger-usersync-services.sh 476aa0c 


Diff: https://reviews.apache.org/r/69040/diff/1/


Testing
---


Thanks,

bhavik patel

[jira] [Updated] (RANGER-2229) Perform graceful terminate with retries before doing forceful kill for usersync and tagsync

2018-10-16 Thread bhavik patel (JIRA) 


 [ 
https://issues.apache.org/jira/browse/RANGER-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

bhavik patel updated RANGER-2229:
-
Attachment: RANGER-2229-01.patch

> Perform graceful terminate with retries before doing forceful kill for 
> usersync and tagsync
> ---
>
> Key: RANGER-2229
> URL: https://issues.apache.org/jira/browse/RANGER-2229
> Project: Ranger
>  Issue Type: Bug
>  Components: tagsync, usersync
>Affects Versions: 1.1.0
>Reporter: suja s
>Assignee: bhavik patel
>Priority: Major
> Attachments: RANGER-2229-01.patch, RANGER-2229.patch
>
>
> In ranger usersync and tagsync scripts, stop of the process is done 
> forcefully using kill -9.
> Suggestion is to do a graceful shutdown with retries and do a force kill only 
> if graceful shutdown is not successful.
> Stop section from ranger-tagsync-services.sh and ranger-tusersync-services.sh
> {noformat}
> lif [ "${action}" == "STOP" ]; then
>  WAIT_TIME_FOR_SHUTDOWN=2
>  NR_ITER_FOR_SHUTDOWN_CHECK=15
>  if [ -f "$pidf" ] ; then
>  pid=`cat $pidf` > /dev/null 2>&1
>  echo "Found Apache Ranger TagSync Service with pid $pid, Stopping..."
>  kill -9 $pid > /dev/null 2>&1
>  sleep 1 #Give kill -9 sometime to "kill"
>  if ps -p $pid > /dev/null; then
>  echo "Wow, even kill -9 failed, giving up! Sorry.."
>  else
>  rm -f $pidf
>  echo "Apache Ranger Tagsync Service pid = ${pid} has been stopped."
>  fi
>  else
>  echo "Ranger Tagsync Service not running"
>  fi
>  exit;
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)