You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Madhan Neethiraj (JIRA)" <ji...@apache.org> on 2015/06/03 01:50:50 UTC
[jira] [Created] (RANGER-523) Update embedded service-def creation
sequence and other misc fixes
Madhan Neethiraj created RANGER-523:
---------------------------------------
Summary: Update embedded service-def creation sequence and other misc fixes
Key: RANGER-523
URL: https://issues.apache.org/jira/browse/RANGER-523
Project: Ranger
Issue Type: Bug
Components: admin
Affects Versions: 0.5.0
Reporter: Madhan Neethiraj
Assignee: Madhan Neethiraj
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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)