GitHub user DadanielZ opened a pull request:

    https://github.com/apache/incubator-eagle/pull/321

    EAGLE-283: Convert fid,uid in MapR's audit log to FIle/folder name, user 
name

    1. Added resolver for user's input of "volume", "file/folder", "Status"
        - These resolver provide drop down list for user to select
    
    2. Added NameConvertor to convert user's input to corresponding id and 
saved it in policy
        - volume value will be used to call MapR's REST API to get volume id
        - status code will be resolved to status id
        - file/folder name will be passed to MapR's command line class to get 
its id.
    
    3. Modified UI js file
        - As soon as user input a value for "volume", "file", "status", it will 
fetch user's input and call rest service to get corresponding id
        - Save ids as a new match criteria in the policy
    
    4. Added maprfs resource resolver to provide drop down list for user
    
    PS:how the id converter works: user select "== '/test'" in field "dst", a 
new match criteria "== 234.567.890" will appear automatically under it, and the 
policy will end up as:
          dst == 'test' or dst == '234.567.890'
    Same thing will happen for volume and status input.
    In this way, the policy is human readable and can be used to match the ids 
in maprfsAuditLog.
    
    5. Added missing dependency on "commons-lang3" for module "eagle-jpm-util"


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/DadanielZ/incubator-eagle EG-283

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-eagle/pull/321.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #321
    
----
commit 936fc5a4eff3cd5bea11c1d15935b124b58b3780
Author: Daniel <[email protected]>
Date:   2016-08-09T22:39:31Z

    EAGLE-283: Convert fid,uid in MapR's audit log to FIle/folder name, user 
name
    
    1. Added resolver for user's input of "volume", "file/folder", "Status"
        - These resolver provide drop down list for user to select
    
    2. Added NameConvertor to convert user's input to corresponding id and 
saved it in policy
        - volume value will be used to call MapR's REST API to get volume id
        - status code will be resolved to status id
        - file/folder name will be passed to MapR's command line class to get 
its id.
    
    3. Modified UI js file
        - As soon as user input a value for "volume", "file", "status", it will 
fetch user's input and call rest service to get corresponding id
        - Save ids as a new match criteria in the policy
    
    4. Added maprfs resource resolver to provide drop down list for user
    
    PS:how the id converter works: user select "== '/test'" in field "dst", a 
new match criteria "== 234.567.890" will appear automatically under it, and the 
policy will end up as:
          dst == 'test' or dst == '234.567.890'
    Same thing will happen for volume and status input.
    In this way, the policy is human readable and can be used to match the ids 
in maprfsAuditLog.

commit 1731469effde0aa88693e7d64f100f3a089b90ac
Author: Daniel <[email protected]>
Date:   2016-08-10T04:03:55Z

    Merge pull request #21 from apache/develop
    
    update from Eagle-develop

commit 5cb1a682718835c10135003328bd959004e36cf9
Author: Daniel <[email protected]>
Date:   2016-08-10T04:05:11Z

    Merge remote-tracking branch 'origin/EG-283' into EG-283

commit e2c5717a616f668c8db2c31b12d77120e9a4fff7
Author: Daniel <[email protected]>
Date:   2016-08-10T04:38:33Z

    Added dependency on "commons-lang3" for module eagle-jpm-util
    - mapr build will fail without this dependency

commit f812c4d3b2b9235840c141beb19a3b33743c9720
Author: Daniel <[email protected]>
Date:   2016-08-10T04:46:04Z

    replaced ip address with map sandbox host name

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to