[ 
https://issues.apache.org/jira/browse/SENTRY-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16422612#comment-16422612
 ] 

Arjun Mishra commented on SENTRY-2194:
--------------------------------------

Tests done locally
{noformat}
$ mvn -f sentry-binding/pom.xml  test

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Sentry Bindings .................................... SUCCESS [  1.391 s]
[INFO] Sentry Binding for Kafka ........................... SUCCESS [ 19.859 s]
[INFO] Sentry Hive Binding Configuration .................. SUCCESS [  3.086 s]
[INFO] Sentry Hive Binding Common ......................... SUCCESS [  2.045 s]
[INFO] Sentry Binding for Solr ............................ SUCCESS [ 17.397 s]
[INFO] Sentry Binding for Sqoop ........................... SUCCESS [  8.079 s]
[INFO] Sentry Binding for HBase Indexer ................... SUCCESS [  3.661 s]
[INFO] Hive follower for Sentry ........................... SUCCESS [  1.996 s]
[INFO] Sentry Binding for Hive ............................ SUCCESS [ 22.422 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:20 min
[INFO] Finished at: 2018-04-02T09:51:16-05:00
[INFO] Final Memory: 71M/931M
[INFO] ------------------------------------------------------------------------
{noformat}
{noformat}
$ mvn -f sentry-provider/pom.xml test

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Sentry Providers ................................... SUCCESS [  1.489 s]
[INFO] Sentry Provider Common ............................. SUCCESS [  3.407 s]
[INFO] Sentry Provider File ............................... SUCCESS [  1.986 s]
[INFO] Sentry Provider DB ................................. SUCCESS [11:09 min]
[INFO] Sentry Provider Cache .............................. SUCCESS [  1.696 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 11:19 min
[INFO] Finished at: 2018-04-02T10:03:12-05:00
[INFO] Final Memory: 53M/805M
[INFO] ------------------------------------------------------------------------
{noformat}
{noformat}
$ mvn -f sentry-hdfs/pom.xml test

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Sentry HDFS ........................................ SUCCESS [  1.390 s]
[INFO] Sentry HDFS Common ................................. SUCCESS [ 19.217 s]
[INFO] Sentry HDFS Service ................................ SUCCESS [07:02 min]
[INFO] Sentry HDFS Namenode Plugin ........................ SUCCESS [  7.064 s]
[INFO] Sentry HDFS Dist ................................... SUCCESS [  1.724 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 07:32 min
[INFO] Finished at: 2018-04-02T10:12:59-05:00
[INFO] Final Memory: 58M/809M
[INFO] ------------------------------------------------------------------------
{noformat}

> Upgrade Sentry hadoop-version dependency to 2.7.5
> -------------------------------------------------
>
>                 Key: SENTRY-2194
>                 URL: https://issues.apache.org/jira/browse/SENTRY-2194
>             Project: Sentry
>          Issue Type: Improvement
>    Affects Versions: 2.1.0
>            Reporter: Arjun Mishra
>            Assignee: Arjun Mishra
>            Priority: Major
>         Attachments: SENTRY-2194.01.patch
>
>
> Hadoop 2.7.5 version has many new features and bug fixes that Sentry can take 
> advantage of. Currently Sentry is using 2.7.2 hadoop-version. We should bump 
> this to 2.7.5



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to