[
https://issues.apache.org/jira/browse/RANGER-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14243328#comment-14243328
]
Alok Lal commented on RANGER-194:
---------------------------------
I agree on using option 1. My reasons are following:
- I tested this by creating a VM that had HDFS, hive, hbase on it. Then used
the tar balls (not rpms) to hand install and test the following:
- policy manager, user-sync.
- hdfs, hbase and hive plugins with audit to db.
This test was done in a simple cluster using mysql. Also I have stayed away
from any changes that isn't strictly related to renaming.
On a different note, for now I am having trouble in getting the review tool to
generate a review for me. We do have a precedence in Dilli's patch for adding
apache licensing on top of every file but -- that patch also changes many
files. But mine is a bit more involved.
- Aside from touching almost all files I also moved files around in directory
tree due to package renaming.
- The moved files were renamed due to class name change.
So currently the review tool is stuck. If I can't get it to let me proceed
them I may have to break up this into multiple commits just to review tool can
work! :(
> Rename packages from xasecure to apache ranger
> ----------------------------------------------
>
> Key: RANGER-194
> URL: https://issues.apache.org/jira/browse/RANGER-194
> Project: Ranger
> Issue Type: New Feature
> Affects Versions: 0.4.0
> Reporter: Alok Lal
> Assignee: Alok Lal
> Fix For: 0.5.0
>
> Attachments:
> 0001-RANGER-194-Rename-packages-classes-to-apache-ranger-.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
