Thanks Dilli :-)

On Thu, Dec 10, 2015 at 3:35 AM, Dilli Dorai <[email protected]> wrote:

> Gautam,
> Your great description and testing are highly appreciated.
> Thanks
> Dilli
>
> On Wed, Dec 9, 2015 at 7:44 AM, Velmurugan Periasamy <
> [email protected]> wrote:
>
>>
>> -----------------------------------------------------------
>> This is an automatically generated e-mail. To reply, visit:
>> https://reviews.apache.org/r/41128/#review109532
>> -----------------------------------------------------------
>>
>> Ship it!
>>
>>
>> Ship It!
>>
>> - Velmurugan Periasamy
>>
>>
>> On Dec. 9, 2015, 12:05 p.m., Gautam Borad wrote:
>> >
>> > -----------------------------------------------------------
>> > This is an automatically generated e-mail. To reply, visit:
>> > https://reviews.apache.org/r/41128/
>> > -----------------------------------------------------------
>> >
>> > (Updated Dec. 9, 2015, 12:05 p.m.)
>> >
>> >
>> > Review request for ranger, Alok Lal, Don Bosco Durai, Abhay Kulkarni,
>> Madhan Neethiraj, Ramesh Mani, Selvamohan Neethiraj, and Velmurugan
>> Periasamy.
>> >
>> >
>> > Bugs: RANGER-776
>> >     https://issues.apache.org/jira/browse/RANGER-776
>> >
>> >
>> > Repository: ranger
>> >
>> >
>> > Description
>> > -------
>> >
>> > **Problem Statement:**
>> > Ranger tagsync code uses 'rangertagsync' user to sync Tags in Ranger
>> Policy manager. For this the 'rangertagsync' user should be created at the
>> time of Ranger installation.
>> > SQL patch to create 'rangertagsync' user is available currently only
>> for MySQL and Oracle DB. Since Ranger can run on Postgres, SQL-Anywhere and
>> MSSQL Server, it is expected that support be extended to these DB.
>> > Since currently Ranger doesnt have a script to create the
>> 'rangertagsync' user for Postgres/SQL-Anywhere and MSSQL Server, tagsync
>> will not work unless the user is created manually from Ranger UI.
>> >
>> > **Proposed Solution:**
>> > Create separate SQL patches for Postgres, SQL-Anywhere and MSSQL Server
>> which will create 'rangertagsync' user in Ranger.
>> >
>> >
>> > Diffs
>> > -----
>> >
>> >   security-admin/db/mysql/patches/017-createtagsyncuser.sql 02a5285
>> >   security-admin/db/mysql/patches/018-createtagsyncuser.sql PRE-CREATION
>> >   security-admin/db/oracle/patches/017-createtagsyncuser.sql 7b72262
>> >   security-admin/db/oracle/patches/018-createtagsyncuser.sql
>> PRE-CREATION
>> >   security-admin/db/postgres/patches/018-createtagsyncuser.sql
>> PRE-CREATION
>> >   security-admin/db/sqlanywhere/patches/018-createtagsyncuser.sql
>> PRE-CREATION
>> >   security-admin/db/sqlserver/patches/018-createtagsyncuser.sql
>> PRE-CREATION
>> >
>> > Diff: https://reviews.apache.org/r/41128/diff/
>> >
>> >
>> > Testing
>> > -------
>> >
>> > Steps performed :
>> > 1. Build Ranger by using mvn command.
>> > 2. Untar the generated Ranger tar file.
>> > 3. Changed configuration of install.properties according to local MySQL
>> DB server.
>> > 4. Run setup.sh to install Ranger.
>> > 5. During installation it was observed that sql patch '018' was
>> executed successfully.
>> > 6. Logged in to configured Ranger DB on MySQL server machine and it was
>> observed that 'rangertagsync' user was created in x_portal_user and x_user
>> table.
>> >
>> >
>> > Did above testing with Oracle, Postgres, SQL Server and SQL Anywhere DB
>> also in local environment.
>> >
>> >
>> > Thanks,
>> >
>> > Gautam Borad
>> >
>> >
>>
>>
>


-- 
Regards,
Gautam.

Reply via email to