[RANGER-523] Update embedded service-def creation sequence and other misc fixes

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.5.0
• Fix Version/s: 0.5.0
• Component/s: admin
• Assignee: Madhan Neethiraj
• Reporter: Madhan Neethiraj
• Created: 02/Jun/15 23:50
• Updated: 03/Jun/15 02:48
• Resolved: 03/Jun/15 02:48

Description

ID for service-defs are auto-generated during creation in the current version. In earlier version (0.4), the equivalent of service-def is assetType - which had the following pre-defined values:

{ HDFS: 1, HBase:2, Hive:3, Knox:5, Storm:6 }

.

It will be good to maintain service-def IDs for HDFS/HBase/Hive/Knox/Strom same as their equivalent assetType from earlier version. These service-defs are created when Ranger Admin starts up for the first time (or during upgrade from the earlier version). Creating these service-defs in the correct order should get them the desired IDs in most deployments.

Also noticed that AppConstants.java has 1037 assigned to two class-types: CLASS_TYPE_RANGER_POLICY_WITH_ASSIGNED_ID and CLASS_TYPE_XA_KMS_KEY. This needs to be fixed.