ranger-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pradeep Agrawal <pradeep.agra...@freestoneinfotech.com>
Subject Review Request 51812: RANGER-1173 : Improve Ranger database schema import logic and make it more robust
Date Mon, 12 Sep 2016 16:01:24 GMT

This is an automatically generated e-mail. To reply, visit:

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

Bugs: RANGER-1173

Repository: ranger


**Problem Statement: ** Ranger installation process should handle concurrent import of DB
schema as concurrent execution of db schema files can lead to an inconsistent state of data
and application.

**Proposed Solution: ** Before importing db schema file; installation process will insert
status in x_db_version_h table with active='N' value. If schema will get created/imported
successfully then status of the schema creation flag will be set to 'Y' else status row from
x_db_version_h will be deleted. If the Ranger DB schema is being imported then the active
column will have the value 'N' and no other process will be allowed to import that file.


  security-admin/db/oracle/create_dbversion_catalog.sql 0017748 
  security-admin/db/oracle/xa_core_db_oracle.sql 2ede810 
  security-admin/scripts/db_setup.py a2b26f5 

Diff: https://reviews.apache.org/r/51812/diff/


**Steps Performed (With Patch) :**

After configuring values in install.properties file, called setup.sh from different terminals.

**Result Behaviour :**
Ranger Was installed successfully and was able to login in Ranger Admin UI.

Note: Patch has been tested for all DB flavors.


Pradeep Agrawal

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message