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


Ship it!




Ship It!

- Velmurugan Periasamy


On Jan. 23, 2019, 8:54 a.m., Pradeep Agrawal wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/69730/
> -----------------------------------------------------------
> 
> (Updated Jan. 23, 2019, 8:54 a.m.)
> 
> 
> Review request for ranger, Abhay Kulkarni, Madhan Neethiraj, Mehul Parikh, 
> Nikhil P, Ramesh Mani, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-2320
>     https://issues.apache.org/jira/browse/RANGER-2320
> 
> 
> Repository: ranger
> 
> 
> Description
> -------
> 
> RANGER-2291 covers changes only in optimized DB schema script, existing DB 
> patches script should be reviewed and if required these scripts also should 
> be made idempotent.
> 
> 
> Diffs
> -----
> 
>   security-admin/db/mysql/patches/009-updated_schema.sql 14ec1d872 
>   security-admin/db/mysql/patches/013-permissionmodel.sql 1c6bcfd13 
>   security-admin/db/mysql/patches/020-datamask-policy.sql 87c0a183a 
>   security-admin/db/mysql/patches/030-policy-labels-schema.sql 33af2a858 
>   security-admin/db/mysql/patches/035-update-schema-for-x-policy.sql 
> 84db52604 
>   security-admin/db/oracle/optimized/current/ranger_core_db_oracle.sql 
> 98c45b05d 
>   security-admin/db/postgres/patches/020-datamask-policy.sql 795721c99 
>   security-admin/db/postgres/patches/035-update-schema-for-x-policy.sql 
> 61c7986e4 
>   security-admin/db/sqlserver/patches/020-datamask-policy.sql c50d2b83d 
>   security-admin/db/sqlserver/patches/035-update-schema-for-x-policy.sql 
> bd646d695 
> 
> 
> Diff: https://reviews.apache.org/r/69730/diff/2/
> 
> 
> Testing
> -------
> 
> Tested the upgrade case from ranger-0.7 to ranger-2.0 for mysql, postgres and 
> sqlserver db.
> 
> 
> Thanks,
> 
> Pradeep Agrawal
> 
>

Reply via email to