[jira] [Commented] (RANGER-2148) Update Ranger Hive dependency version to 3.0
[ https://issues.apache.org/jira/browse/RANGER-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16779890#comment-16779890 ] Colm O hEigeartaigh commented on RANGER-2148: - The patch for RANGER-1935 should be applied to master soon. > Update Ranger Hive dependency version to 3.0 > - > > Key: RANGER-2148 > URL: https://issues.apache.org/jira/browse/RANGER-2148 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master >Reporter: Ramesh Mani >Assignee: Colm O hEigeartaigh >Priority: Critical > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-2148-Update-Ranger-Hive-dependency-version-to.patch > > > Update Ranger Hive dependency version to 3.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2322) Use "TLS" in SSLContext.getInstance
[
https://issues.apache.org/jira/browse/RANGER-2322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh updated RANGER-2322:
Attachment: RANGER-2322.patch
> Use "TLS" in SSLContext.getInstance
> ---
>
> Key: RANGER-2322
> URL: https://issues.apache.org/jira/browse/RANGER-2322
> Project: Ranger
> Issue Type: Improvement
> Components: plugins, usersync
>Reporter: Colm O hEigeartaigh
>Assignee: Colm O hEigeartaigh
>Priority: Major
> Fix For: 2.0.0
>
> Attachments: RANGER-2322.patch
>
>
> There are a few instances in the code of SSLContext.getInstance("SSL").
> Instead we should use "TLS".
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (RANGER-2322) Use "TLS" in SSLContext.getInstance
Colm O hEigeartaigh created RANGER-2322:
---
Summary: Use "TLS" in SSLContext.getInstance
Key: RANGER-2322
URL: https://issues.apache.org/jira/browse/RANGER-2322
Project: Ranger
Issue Type: Improvement
Components: plugins, usersync
Affects Versions: 2.0.0
Reporter: Colm O hEigeartaigh
Assignee: Colm O hEigeartaigh
There are a few instances in the code of SSLContext.getInstance("SSL"). Instead
we should use "TLS".
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (RANGER-2256) Grammatical error in UI
[ https://issues.apache.org/jira/browse/RANGER-2256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-2256: Attachment: 0001-RANGER-2256-Grammatical-error-in-UI.patch > Grammatical error in UI > --- > > Key: RANGER-2256 > URL: https://issues.apache.org/jira/browse/RANGER-2256 > Project: Ranger > Issue Type: Task > Components: admin >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Trivial > Fix For: 2.0.0 > > Attachments: 0001-RANGER-2256-Grammatical-error-in-UI.patch > > > There's a grammatical error in the UI when looking at the users of an empty > group. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2256) Grammatical error in UI
Colm O hEigeartaigh created RANGER-2256: --- Summary: Grammatical error in UI Key: RANGER-2256 URL: https://issues.apache.org/jira/browse/RANGER-2256 Project: Ranger Issue Type: Task Components: admin Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 2.0.0 There's a grammatical error in the UI when looking at the users of an empty group. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2239) Update to surefire 2.21.0
[ https://issues.apache.org/jira/browse/RANGER-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-2239: Attachment: 0001-RANGER-2239-Update-to-surefire-2.21.0.patch > Update to surefire 2.21.0 > - > > Key: RANGER-2239 > URL: https://issues.apache.org/jira/browse/RANGER-2239 > Project: Ranger > Issue Type: Task > Components: build-infra >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 2.0.0 > > Attachments: 0001-RANGER-2239-Update-to-surefire-2.21.0.patch > > > To support newer Java versions, we need to update surefire. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2239) Update to surefire 2.21.0
Colm O hEigeartaigh created RANGER-2239: --- Summary: Update to surefire 2.21.0 Key: RANGER-2239 URL: https://issues.apache.org/jira/browse/RANGER-2239 Project: Ranger Issue Type: Task Components: build-infra Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 2.0.0 To support newer Java versions, we need to update surefire. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2231) Upgrade to Knox 1.1.0
[ https://issues.apache.org/jira/browse/RANGER-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-2231: Attachment: (was: 0001-RANGER-2231-Upgrade-to-Knox-1.1.0.patch) > Upgrade to Knox 1.1.0 > - > > Key: RANGER-2231 > URL: https://issues.apache.org/jira/browse/RANGER-2231 > Project: Ranger > Issue Type: Task > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 2.0.0 > > Attachments: 0001-RANGER-2231-Upgrade-to-Knox-1.1.0.patch > > > Upgrade to Knox 1.1.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2231) Upgrade to Knox 1.1.0
[ https://issues.apache.org/jira/browse/RANGER-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-2231: Attachment: 0001-RANGER-2231-Upgrade-to-Knox-1.1.0.patch > Upgrade to Knox 1.1.0 > - > > Key: RANGER-2231 > URL: https://issues.apache.org/jira/browse/RANGER-2231 > Project: Ranger > Issue Type: Task > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 2.0.0 > > Attachments: 0001-RANGER-2231-Upgrade-to-Knox-1.1.0.patch > > > Upgrade to Knox 1.1.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2231) Upgrade to Knox 1.1.0
[ https://issues.apache.org/jira/browse/RANGER-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-2231: Attachment: 0001-RANGER-2231-Upgrade-to-Knox-1.1.0.patch > Upgrade to Knox 1.1.0 > - > > Key: RANGER-2231 > URL: https://issues.apache.org/jira/browse/RANGER-2231 > Project: Ranger > Issue Type: Task > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 2.0.0 > > Attachments: 0001-RANGER-2231-Upgrade-to-Knox-1.1.0.patch > > > Upgrade to Knox 1.1.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2231) Upgrade to Knox 1.1.0
Colm O hEigeartaigh created RANGER-2231: --- Summary: Upgrade to Knox 1.1.0 Key: RANGER-2231 URL: https://issues.apache.org/jira/browse/RANGER-2231 Project: Ranger Issue Type: Task Components: plugins Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 2.0.0 Upgrade to Knox 1.1.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2190) Auto populate the relationship ends when relationship type is selected.
[ https://issues.apache.org/jira/browse/RANGER-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-2190: Fix Version/s: (was: 1.1.0) > Auto populate the relationship ends when relationship type is selected. > --- > > Key: RANGER-2190 > URL: https://issues.apache.org/jira/browse/RANGER-2190 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 1.1.0 >Reporter: Ayub Pathan >Priority: Critical > > Currently relationship ends need to be manually populated by user and this > can be auto-populated whenever a relationship type is selected. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2226) Define explicit (test) dependency on json-smart in the Knox agent
[ https://issues.apache.org/jira/browse/RANGER-2226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-2226: Fix Version/s: (was: 1.1.0) > Define explicit (test) dependency on json-smart in the Knox agent > - > > Key: RANGER-2226 > URL: https://issues.apache.org/jira/browse/RANGER-2226 > Project: Ranger > Issue Type: Task > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-2226-Define-explicit-test-dependency-on-json-.patch > > > The build is currently failing for me with: > Failed to read artifact descriptor for > net.minidev:json-smart:jar:2.3-SNAPSHOT: Could not transfer artifact > net.minidev:json-smart:pom:2.3-SNAPSHOT from/to dynamodb-local-oregon > (https://s3-us-west-2.amazonaws.com/dynamodb-local/release): Access denied > to: > https://s3-us-west-2.amazonaws.com/dynamodb-local/release/net/minidev/json-smart/2.3-SNAPSHOT/json-smart-2.3-SNAPSHOT.pom > , ReasonPhrase:Forbidden. -> [Help 1] > The fix is to declare an explicit (test) dependency on json-smart in the Knox > module. > See: https://issues.apache.org/jira/browse/KNOX-1275 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2226) Define explicit (test) dependency on json-smart in the Knox agent
[ https://issues.apache.org/jira/browse/RANGER-2226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-2226: Attachment: 0001-RANGER-2226-Define-explicit-test-dependency-on-json-.patch > Define explicit (test) dependency on json-smart in the Knox agent > - > > Key: RANGER-2226 > URL: https://issues.apache.org/jira/browse/RANGER-2226 > Project: Ranger > Issue Type: Task > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 1.1.0, 2.0.0 > > Attachments: > 0001-RANGER-2226-Define-explicit-test-dependency-on-json-.patch > > > The build is currently failing for me with: > Failed to read artifact descriptor for > net.minidev:json-smart:jar:2.3-SNAPSHOT: Could not transfer artifact > net.minidev:json-smart:pom:2.3-SNAPSHOT from/to dynamodb-local-oregon > (https://s3-us-west-2.amazonaws.com/dynamodb-local/release): Access denied > to: > https://s3-us-west-2.amazonaws.com/dynamodb-local/release/net/minidev/json-smart/2.3-SNAPSHOT/json-smart-2.3-SNAPSHOT.pom > , ReasonPhrase:Forbidden. -> [Help 1] > The fix is to declare an explicit (test) dependency on json-smart in the Knox > module. > See: https://issues.apache.org/jira/browse/KNOX-1275 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2226) Define explicit (test) dependency on json-smart in the Knox agent
Colm O hEigeartaigh created RANGER-2226: --- Summary: Define explicit (test) dependency on json-smart in the Knox agent Key: RANGER-2226 URL: https://issues.apache.org/jira/browse/RANGER-2226 Project: Ranger Issue Type: Task Components: plugins Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 2.0.0, 1.1.0 The build is currently failing for me with: Failed to read artifact descriptor for net.minidev:json-smart:jar:2.3-SNAPSHOT: Could not transfer artifact net.minidev:json-smart:pom:2.3-SNAPSHOT from/to dynamodb-local-oregon (https://s3-us-west-2.amazonaws.com/dynamodb-local/release): Access denied to: https://s3-us-west-2.amazonaws.com/dynamodb-local/release/net/minidev/json-smart/2.3-SNAPSHOT/json-smart-2.3-SNAPSHOT.pom , ReasonPhrase:Forbidden. -> [Help 1] The fix is to declare an explicit (test) dependency on json-smart in the Knox module. See: https://issues.apache.org/jira/browse/KNOX-1275 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-1935) Upgrade Ranger to support Apache Hadoop 3.0.0
[ https://issues.apache.org/jira/browse/RANGER-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1935: Attachment: 0001-RANGER-1935-Upgrade-Ranger-to-support-Apache-Hadoop-.patch > Upgrade Ranger to support Apache Hadoop 3.0.0 > - > > Key: RANGER-1935 > URL: https://issues.apache.org/jira/browse/RANGER-1935 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-1935-Upgrade-Ranger-to-support-Apache-Hadoop-.patch > > > This task is to upgrade Ranger to support Apache Hadoop 3.0.0. Here are some > notes about the upgrade: > a) The Hive plugin needs the Hadoop 3.0.0 jars to run the tests properly, as > Hive only supports the older Hadoop version, so an exclusion and some > additional 3.0.0 dependencies need to be added. > b) The Storm plugin bundles the hadoop-auth jars in storm-core (although they > really should be renamed here). Therefore, we have no option but to package > Storm with the Hadoop 2.7.x jars, until such time that Storm upgrades the > Hadoop dependency. > This is an initial patch to get some feedback. If there is broad agreement on > the upgrade I will test the distributions properly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-1935) Upgrade Ranger to support Apache Hadoop 3.0.0
[ https://issues.apache.org/jira/browse/RANGER-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1935: Attachment: (was: 0001-RANGER-1935-Upgrade-Ranger-to-support-Apache-Hadoop-.patch) > Upgrade Ranger to support Apache Hadoop 3.0.0 > - > > Key: RANGER-1935 > URL: https://issues.apache.org/jira/browse/RANGER-1935 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 2.0.0 > > > This task is to upgrade Ranger to support Apache Hadoop 3.0.0. Here are some > notes about the upgrade: > a) The Hive plugin needs the Hadoop 3.0.0 jars to run the tests properly, as > Hive only supports the older Hadoop version, so an exclusion and some > additional 3.0.0 dependencies need to be added. > b) The Storm plugin bundles the hadoop-auth jars in storm-core (although they > really should be renamed here). Therefore, we have no option but to package > Storm with the Hadoop 2.7.x jars, until such time that Storm upgrades the > Hadoop dependency. > This is an initial patch to get some feedback. If there is broad agreement on > the upgrade I will test the distributions properly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-1935) Upgrade Ranger to support Apache Hadoop 3.0.0
[ https://issues.apache.org/jira/browse/RANGER-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1935: Attachment: (was: 0001-RANGER-1935-Upgrade-Ranger-to-support-Apache-Hadoop-.patch) > Upgrade Ranger to support Apache Hadoop 3.0.0 > - > > Key: RANGER-1935 > URL: https://issues.apache.org/jira/browse/RANGER-1935 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-1935-Upgrade-Ranger-to-support-Apache-Hadoop-.patch > > > This task is to upgrade Ranger to support Apache Hadoop 3.0.0. Here are some > notes about the upgrade: > a) The Hive plugin needs the Hadoop 3.0.0 jars to run the tests properly, as > Hive only supports the older Hadoop version, so an exclusion and some > additional 3.0.0 dependencies need to be added. > b) The Storm plugin bundles the hadoop-auth jars in storm-core (although they > really should be renamed here). Therefore, we have no option but to package > Storm with the Hadoop 2.7.x jars, until such time that Storm upgrades the > Hadoop dependency. > This is an initial patch to get some feedback. If there is broad agreement on > the upgrade I will test the distributions properly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-1935) Upgrade Ranger to support Apache Hadoop 3.0.0
[ https://issues.apache.org/jira/browse/RANGER-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1935: Attachment: 0001-RANGER-1935-Upgrade-Ranger-to-support-Apache-Hadoop-.patch > Upgrade Ranger to support Apache Hadoop 3.0.0 > - > > Key: RANGER-1935 > URL: https://issues.apache.org/jira/browse/RANGER-1935 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-1935-Upgrade-Ranger-to-support-Apache-Hadoop-.patch > > > This task is to upgrade Ranger to support Apache Hadoop 3.0.0. Here are some > notes about the upgrade: > a) The Hive plugin needs the Hadoop 3.0.0 jars to run the tests properly, as > Hive only supports the older Hadoop version, so an exclusion and some > additional 3.0.0 dependencies need to be added. > b) The Storm plugin bundles the hadoop-auth jars in storm-core (although they > really should be renamed here). Therefore, we have no option but to package > Storm with the Hadoop 2.7.x jars, until such time that Storm upgrades the > Hadoop dependency. > This is an initial patch to get some feedback. If there is broad agreement on > the upgrade I will test the distributions properly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2198) Remove deprecated client API from HBase plugin
[ https://issues.apache.org/jira/browse/RANGER-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-2198: Attachment: 0001-RANGER-2198-Remove-deprecated-client-API-from-HBase-.patch > Remove deprecated client API from HBase plugin > -- > > Key: RANGER-2198 > URL: https://issues.apache.org/jira/browse/RANGER-2198 > Project: Ranger > Issue Type: Task > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-2198-Remove-deprecated-client-API-from-HBase-.patch > > > This task is to replace the deprecated client API from the HBase plugin. This > will make migrating to HBase 2.0.0 a bit easier. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2198) Remove deprecated client API from HBase plugin
Colm O hEigeartaigh created RANGER-2198: --- Summary: Remove deprecated client API from HBase plugin Key: RANGER-2198 URL: https://issues.apache.org/jira/browse/RANGER-2198 Project: Ranger Issue Type: Task Components: plugins Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 2.0.0 This task is to replace the deprecated client API from the HBase plugin. This will make migrating to HBase 2.0.0 a bit easier. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2148) Update Ranger Hive dependency version to 3.0
[ https://issues.apache.org/jira/browse/RANGER-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16590502#comment-16590502 ] Colm O hEigeartaigh commented on RANGER-2148: - Patch included. It depends on the Hadoop 3.0.0 patch in RANGER-1935. Tested with Hadoop 3.0.0 + Hive 3.0.0. > Update Ranger Hive dependency version to 3.0 > - > > Key: RANGER-2148 > URL: https://issues.apache.org/jira/browse/RANGER-2148 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master >Reporter: Ramesh Mani >Assignee: Colm O hEigeartaigh >Priority: Critical > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-2148-Update-Ranger-Hive-dependency-version-to.patch > > > Update Ranger Hive dependency version to 3.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2148) Update Ranger Hive dependency version to 3.0
[ https://issues.apache.org/jira/browse/RANGER-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-2148: Attachment: 0001-RANGER-2148-Update-Ranger-Hive-dependency-version-to.patch > Update Ranger Hive dependency version to 3.0 > - > > Key: RANGER-2148 > URL: https://issues.apache.org/jira/browse/RANGER-2148 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master >Reporter: Ramesh Mani >Assignee: Colm O hEigeartaigh >Priority: Critical > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-2148-Update-Ranger-Hive-dependency-version-to.patch > > > Update Ranger Hive dependency version to 3.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-1935) Upgrade Ranger to support Apache Hadoop 3.0.0
[ https://issues.apache.org/jira/browse/RANGER-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1935: Attachment: 0001-RANGER-1935-Upgrade-Ranger-to-support-Apache-Hadoop-.patch > Upgrade Ranger to support Apache Hadoop 3.0.0 > - > > Key: RANGER-1935 > URL: https://issues.apache.org/jira/browse/RANGER-1935 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-1935-Upgrade-Ranger-to-support-Apache-Hadoop-.patch, > 0001-RANGER-1935-Upgrade-Ranger-to-support-Apache-Hadoop-.patch > > > This task is to upgrade Ranger to support Apache Hadoop 3.0.0. Here are some > notes about the upgrade: > a) The Hive plugin needs the Hadoop 3.0.0 jars to run the tests properly, as > Hive only supports the older Hadoop version, so an exclusion and some > additional 3.0.0 dependencies need to be added. > b) The Storm plugin bundles the hadoop-auth jars in storm-core (although they > really should be renamed here). Therefore, we have no option but to package > Storm with the Hadoop 2.7.x jars, until such time that Storm upgrades the > Hadoop dependency. > This is an initial patch to get some feedback. If there is broad agreement on > the upgrade I will test the distributions properly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2167) Upgrade to Apache parent pom version 20
[ https://issues.apache.org/jira/browse/RANGER-2167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-2167: Attachment: 0001-RANGER-2167-Upgrade-to-Apache-parent-pom-version-20.patch > Upgrade to Apache parent pom version 20 > --- > > Key: RANGER-2167 > URL: https://issues.apache.org/jira/browse/RANGER-2167 > Project: Ranger > Issue Type: Task > Components: admin, plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Minor > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-2167-Upgrade-to-Apache-parent-pom-version-20.patch > > > This task is to upgrade to the Apache parent pom version 20. This > necessitates a PMD upgrade and quite a few fixes are required as a result. > One notable change is to switch the KMS Keystore implementation to use > ConcurrentHashMap instead of HashTable. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-1935) Upgrade Ranger to support Apache Hadoop 3.0.0
[ https://issues.apache.org/jira/browse/RANGER-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16539735#comment-16539735 ] Colm O hEigeartaigh commented on RANGER-1935: - Yes, working on it at the moment. > Upgrade Ranger to support Apache Hadoop 3.0.0 > - > > Key: RANGER-1935 > URL: https://issues.apache.org/jira/browse/RANGER-1935 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 2.0.0 > > Attachments: > 0001-RANGER-1935-Upgrade-Ranger-to-support-Apache-Hadoop-.patch > > > This task is to upgrade Ranger to support Apache Hadoop 3.0.0. Here are some > notes about the upgrade: > a) The Hive plugin needs the Hadoop 3.0.0 jars to run the tests properly, as > Hive only supports the older Hadoop version, so an exclusion and some > additional 3.0.0 dependencies need to be added. > b) The Storm plugin bundles the hadoop-auth jars in storm-core (although they > really should be renamed here). Therefore, we have no option but to package > Storm with the Hadoop 2.7.x jars, until such time that Storm upgrades the > Hadoop dependency. > This is an initial patch to get some feedback. If there is broad agreement on > the upgrade I will test the distributions properly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-2148) Update Ranger Hive dependency version to 3.0
[ https://issues.apache.org/jira/browse/RANGER-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16532398#comment-16532398 ] Colm O hEigeartaigh commented on RANGER-2148: - Is this targeted for 2.0.0? I have some work done on this already - in conjunction with the upgrade to Hadoop 3.x > Update Ranger Hive dependency version to 3.0 > - > > Key: RANGER-2148 > URL: https://issues.apache.org/jira/browse/RANGER-2148 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: master >Reporter: Ramesh Mani >Assignee: Ramesh Mani >Priority: Critical > Fix For: master > > > Update Ranger Hive dependency version to 3.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2136) Upgrade to the released version of Atlas 1.0.0
[ https://issues.apache.org/jira/browse/RANGER-2136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-2136: Attachment: 0001-RANGER-2136-Upgrade-to-the-released-version-of-Atlas.patch > Upgrade to the released version of Atlas 1.0.0 > -- > > Key: RANGER-2136 > URL: https://issues.apache.org/jira/browse/RANGER-2136 > Project: Ranger > Issue Type: Task > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Minor > Fix For: 1.1.0 > > Attachments: > 0001-RANGER-2136-Upgrade-to-the-released-version-of-Atlas.patch > > > We should update to the released version of Atlas 1.0.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2136) Upgrade to the released version of Atlas 1.0.0
Colm O hEigeartaigh created RANGER-2136: --- Summary: Upgrade to the released version of Atlas 1.0.0 Key: RANGER-2136 URL: https://issues.apache.org/jira/browse/RANGER-2136 Project: Ranger Issue Type: Task Components: plugins Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 1.1.0 We should update to the released version of Atlas 1.0.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2072) Update HBase to 1.3.2
[ https://issues.apache.org/jira/browse/RANGER-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-2072: Attachment: 0001-RANGER-2072-Update-HBase-to-1.3.2.patch > Update HBase to 1.3.2 > - > > Key: RANGER-2072 > URL: https://issues.apache.org/jira/browse/RANGER-2072 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 1.1.0 > > Attachments: 0001-RANGER-2072-Update-HBase-to-1.3.2.patch > > > This task is to upgrade the HBase dependency to 1.3.2. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2072) Update HBase to 1.3.2
Colm O hEigeartaigh created RANGER-2072: --- Summary: Update HBase to 1.3.2 Key: RANGER-2072 URL: https://issues.apache.org/jira/browse/RANGER-2072 Project: Ranger Issue Type: Improvement Components: plugins Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 1.1.0 This task is to upgrade the HBase dependency to 1.3.2. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-1808) Write unit test for RANGER-1672
[ https://issues.apache.org/jira/browse/RANGER-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1808: Fix Version/s: 1.1.0 > Write unit test for RANGER-1672 > --- > > Key: RANGER-1808 > URL: https://issues.apache.org/jira/browse/RANGER-1808 > Project: Ranger > Issue Type: Sub-task > Components: plugins >Affects Versions: master, 1.1.0 >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: newbie, patch > Fix For: 1.1.0 > > Attachments: > 0001-RANGER-1808-Write-unit-test-for-RANGER-1672-kylin-pl.patch, > kylin-policies.json > > > Write unit test for RANGER-1672 kylin plugin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2022) Atlas plugin install.properties is missing component location
[ https://issues.apache.org/jira/browse/RANGER-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-2022: Attachment: 0001-RANGER-2022-Atlas-plugin-install.properties-is-missi.patch > Atlas plugin install.properties is missing component location > - > > Key: RANGER-2022 > URL: https://issues.apache.org/jira/browse/RANGER-2022 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Minor > Fix For: 1.1.0 > > Attachments: > 0001-RANGER-2022-Atlas-plugin-install.properties-is-missi.patch > > > The Atlas plugin install.properties is missing the component location. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2022) Atlas plugin install.properties is missing component location
Colm O hEigeartaigh created RANGER-2022: --- Summary: Atlas plugin install.properties is missing component location Key: RANGER-2022 URL: https://issues.apache.org/jira/browse/RANGER-2022 Project: Ranger Issue Type: Improvement Components: plugins Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 1.1.0 The Atlas plugin install.properties is missing the component location. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-1326) Fix remaining licensing issues
[ https://issues.apache.org/jira/browse/RANGER-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16390964#comment-16390964 ] Colm O hEigeartaigh commented on RANGER-1326: - Hi [~vperiasamy], we really need to get this done for 1.0.0 - we can't ship a 1.0.0 product with licensing concerns IMO. > Fix remaining licensing issues > -- > > Key: RANGER-1326 > URL: https://issues.apache.org/jira/browse/RANGER-1326 > Project: Ranger > Issue Type: Bug >Affects Versions: 0.6.2 >Reporter: Colm O hEigeartaigh >Priority: Major > Fix For: 1.1.0 > > > We need to fix the remaining licensing issues as raised by Jusin: > For items not fixed please see [1][2][3]. > Also note that with json2.js license it seems a little unclear to me and may > be under the JSON license. It does have “public domain” in the code so it may > be OK, it still however needs to be added to LICENSE. Just be careful as the > JSON license no longer allowed in Apache software and it is considered > category X. [4] In this case you do have a few months grace to remove this > [5] but you need to call it out in NOTICE and it still needs to be removed by > end of April. [5] > 1. > https://lists.apache.org/thread.html/6949e2f048b07478c861a675ad8e98d750e0f786b272a6afc69df78e@%3Cgeneral.incubator.apache.org%3E > 2. > https://lists.apache.org/thread.html/9552c63b71a38ed75cd252463e788408aa4a9a05abeba36168df5a12@%3Cgeneral.incubator.apache.org%3E > 3. > https://lists.apache.org/thread.html/de169a09f7527fbc3549518f0227ba40ee8524c6e60ba8105d82479b@%3Cgeneral.incubator.apache.org%3E > 4. https://www.apache.org/legal/resolved#category-x > 5. > https://lists.apache.org/thread.html/bb18f942ce7eb83c11438303c818b885810fb76385979490366720d5@%3Clegal-discuss.apache.org%3E -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2012) Update Apache parent pom version
[ https://issues.apache.org/jira/browse/RANGER-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-2012: Priority: Trivial (was: Major) > Update Apache parent pom version > > > Key: RANGER-2012 > URL: https://issues.apache.org/jira/browse/RANGER-2012 > Project: Ranger > Issue Type: Improvement > Components: build-infra >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Trivial > Fix For: 1.1.0 > > Attachments: 0001-RANGER-2012-Update-Apache-parent-pom-version.patch > > > This task is to update the Apache parent pom version - see for example > https://issues.apache.org/jira/browse/MPOM-118 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-2012) Update Apache parent pom version
[ https://issues.apache.org/jira/browse/RANGER-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-2012: Attachment: 0001-RANGER-2012-Update-Apache-parent-pom-version.patch > Update Apache parent pom version > > > Key: RANGER-2012 > URL: https://issues.apache.org/jira/browse/RANGER-2012 > Project: Ranger > Issue Type: Improvement > Components: build-infra >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 1.1.0 > > Attachments: 0001-RANGER-2012-Update-Apache-parent-pom-version.patch > > > This task is to update the Apache parent pom version - see for example > https://issues.apache.org/jira/browse/MPOM-118 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-2012) Update Apache parent pom version
Colm O hEigeartaigh created RANGER-2012: --- Summary: Update Apache parent pom version Key: RANGER-2012 URL: https://issues.apache.org/jira/browse/RANGER-2012 Project: Ranger Issue Type: Improvement Components: build-infra Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 1.1.0 This task is to update the Apache parent pom version - see for example https://issues.apache.org/jira/browse/MPOM-118 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-1824) Upgrade Spring Framework to 3.2.18
[ https://issues.apache.org/jira/browse/RANGER-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1824: Fix Version/s: (was: 1.0.0) > Upgrade Spring Framework to 3.2.18 > -- > > Key: RANGER-1824 > URL: https://issues.apache.org/jira/browse/RANGER-1824 > Project: Ranger > Issue Type: Improvement > Components: admin >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Minor > Attachments: 0001-RANGER-1824-Upgrade-Spring-Framework-to-3.2.18.patch > > > When starting the Admin console, the following appears in the logs: > 2017-10-02 10:00:35,651 [localhost-startStop-1] WARN > org.springframework.security.core.SpringSecurityCoreVersion > (SpringSecurityCoreVersion.java:60) - You are advised to use Spring > 3.2.18.RELEASE or later with this version. You are running: 3.2.10.RELEASE > We should update Spring to 3.2.18 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-1935) Upgrade Ranger to support Apache Hadoop 3.0.0
[ https://issues.apache.org/jira/browse/RANGER-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1935: Fix Version/s: (was: 1.0.0) > Upgrade Ranger to support Apache Hadoop 3.0.0 > - > > Key: RANGER-1935 > URL: https://issues.apache.org/jira/browse/RANGER-1935 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Attachments: > 0001-RANGER-1935-Upgrade-Ranger-to-support-Apache-Hadoop-.patch > > > This task is to upgrade Ranger to support Apache Hadoop 3.0.0. Here are some > notes about the upgrade: > a) The Hive plugin needs the Hadoop 3.0.0 jars to run the tests properly, as > Hive only supports the older Hadoop version, so an exclusion and some > additional 3.0.0 dependencies need to be added. > b) The Storm plugin bundles the hadoop-auth jars in storm-core (although they > really should be renamed here). Therefore, we have no option but to package > Storm with the Hadoop 2.7.x jars, until such time that Storm upgrades the > Hadoop dependency. > This is an initial patch to get some feedback. If there is broad agreement on > the upgrade I will test the distributions properly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-1738) RangerYarnAuthorizer not compatible with Hadoop-3.0.0
[
https://issues.apache.org/jira/browse/RANGER-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh updated RANGER-1738:
Fix Version/s: (was: 1.0.0)
> RangerYarnAuthorizer not compatible with Hadoop-3.0.0
> -
>
> Key: RANGER-1738
> URL: https://issues.apache.org/jira/browse/RANGER-1738
> Project: Ranger
> Issue Type: Bug
> Components: plugins
>Affects Versions: 0.7.1
>Reporter: Hong Shen
>Assignee: Colm O hEigeartaigh
>Priority: Major
> Attachments:
> 0001-RANGER-1738-RangerYarnAuthorizer-not-compatible-with.patch
>
>
> In the newest hadoop version 3.0.0, YarnAuthorizationProvider has changed.
> The new YarnAuthorizationProvider.java has change the methods checkPermission
> and setPermission,
> {code:title=YarnAuthorizationProvider.java|borderStyle=solid}
> /**
>* Check if user has the permission to access the target object.
>*
>* @param accessRequest
>* the request object which contains all the access context info.
>* @return true if user can access the object, otherwise false.
>*/
> public abstract boolean checkPermission(AccessRequest accessRequest);
> /**
>* Set permissions for the target object.
>*
>* @param permissions
>*A list of permissions on the target object.
>* @param ugi User who sets the permissions.
>*/
> public abstract void setPermission(List permissions,
> UserGroupInformation ugi);
> {code}
> But the RangerYarnAuthorizer extends YarnAuthorizationProvider impletement
> the old method.
> {code:title=RangerYarnAuthorizer.java|borderStyle=solid}
> @Override
> public void setPermission(PrivilegedEntity entity, Map AccessControlList> permission, UserGroupInformation ugi) {
>...
> @Override
> public boolean checkPermission(AccessType accessType, PrivilegedEntity
> entity, UserGroupInformation ugi) {
> {code}
> I think yarn plugin should also impletement the new method. I will add a
> patch for it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (RANGER-1935) Upgrade Ranger to support Apache Hadoop 3.0.0
[ https://issues.apache.org/jira/browse/RANGER-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16381698#comment-16381698 ] Colm O hEigeartaigh commented on RANGER-1935: - Yes, can we add a 1.1.0 version that I can move it to? > Upgrade Ranger to support Apache Hadoop 3.0.0 > - > > Key: RANGER-1935 > URL: https://issues.apache.org/jira/browse/RANGER-1935 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1935-Upgrade-Ranger-to-support-Apache-Hadoop-.patch > > > This task is to upgrade Ranger to support Apache Hadoop 3.0.0. Here are some > notes about the upgrade: > a) The Hive plugin needs the Hadoop 3.0.0 jars to run the tests properly, as > Hive only supports the older Hadoop version, so an exclusion and some > additional 3.0.0 dependencies need to be added. > b) The Storm plugin bundles the hadoop-auth jars in storm-core (although they > really should be renamed here). Therefore, we have no option but to package > Storm with the Hadoop 2.7.x jars, until such time that Storm upgrades the > Hadoop dependency. > This is an initial patch to get some feedback. If there is broad agreement on > the upgrade I will test the distributions properly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-1967) The Ranger support the Kafka 1.0.0
[ https://issues.apache.org/jira/browse/RANGER-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16376690#comment-16376690 ] Colm O hEigeartaigh commented on RANGER-1967: - Hi [~zhangqiang2], We (the Ranger team) discussed a similar issue for Hadoop (where upgrading to Hadoop 3.0.0 meant that support was dropped for 2.x). It was felt that we should not have multiple plugin versions but instead users who want support for an older plugin version can just get it from an older Ranger release. If users want support for Kafka 0.10.x they can just get the plugin from Ranger 0.7.1. Colm. > The Ranger support the Kafka 1.0.0 > -- > > Key: RANGER-1967 > URL: https://issues.apache.org/jira/browse/RANGER-1967 > Project: Ranger > Issue Type: New Feature > Components: plugins >Reporter: Qiang Zhang >Assignee: Zsombor Gegesy >Priority: Major > Labels: newbie, patch > Attachments: RANGER-1967-2.patch, RANGER-1967.patch > > > Now the Ranger don't support the Kafka 1.0.0. We should support the Kafka > 1.0.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-1967) The Ranger support the Kafka 1.0.0
[ https://issues.apache.org/jira/browse/RANGER-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16371143#comment-16371143 ] Colm O hEigeartaigh commented on RANGER-1967: - [~zhangqiang2] any update on this? > The Ranger support the Kafka 1.0.0 > -- > > Key: RANGER-1967 > URL: https://issues.apache.org/jira/browse/RANGER-1967 > Project: Ranger > Issue Type: New Feature > Components: plugins >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: newbie, patch > > Now the Ranger don't support the Kafka 1.0.0. We should support the Kafka > 1.0.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-1987) Upgrade to Storm 1.2.0
[ https://issues.apache.org/jira/browse/RANGER-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1987: Attachment: 0001-RANGER-1987-Upgrade-to-Storm-1.2.0.patch > Upgrade to Storm 1.2.0 > -- > > Key: RANGER-1987 > URL: https://issues.apache.org/jira/browse/RANGER-1987 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 1.0.0 > > Attachments: 0001-RANGER-1987-Upgrade-to-Storm-1.2.0.patch > > > > We should upgrade to the recently release Apache Storm 1.2.0. No code changes > are required. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-1987) Upgrade to Storm 1.2.0
Colm O hEigeartaigh created RANGER-1987: --- Summary: Upgrade to Storm 1.2.0 Key: RANGER-1987 URL: https://issues.apache.org/jira/browse/RANGER-1987 Project: Ranger Issue Type: Improvement Components: plugins Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 1.0.0 We should upgrade to the recently release Apache Storm 1.2.0. No code changes are required. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-1980) Build failure for Ranger 0.7 branch
[ https://issues.apache.org/jira/browse/RANGER-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360778#comment-16360778 ] Colm O hEigeartaigh commented on RANGER-1980: - Any reason we can't just upgrade both master + 0.7.x with Atlas 0.8.2? > Build failure for Ranger 0.7 branch > --- > > Key: RANGER-1980 > URL: https://issues.apache.org/jira/browse/RANGER-1980 > Project: Ranger > Issue Type: Bug > Components: build-infra >Affects Versions: 0.7.2 >Reporter: Don Bosco Durai >Assignee: Pradeep Agrawal >Priority: Major > Fix For: 0.7.2 > > Attachments: > 0001-RANGER-1980-Build-failure-for-Ranger-0.7-branch.patch > > Original Estimate: 48h > Remaining Estimate: 48h > > Ranger 0.7 compilation is failing with the following error. > > > [ERROR] Failed to execute goal on project ranger-tagsync: Could not resolve > dependencies for project org.apache.ranger:ranger-tagsync:jar:0.7.0.3.1.0: > The following artifacts could not be resolved: > org.apache.atlas:atlas-notification:jar:0.8.2-SNAPSHOT, > org.apache.atlas:atlas-typesystem:jar:0.8.2-SNAPSHOT, > org.apache.atlas:atlas-client-v1:jar:0.8.2-SNAPSHOT, > org.apache.atlas:atlas-client-common:jar:0.8.2-SNAPSHOT, > org.apache.atlas:atlas-client-v2:jar:0.8.2-SNAPSHOT, > org.apache.atlas:atlas-common:jar:0.8.2-SNAPSHOT, > org.apache.atlas:atlas-intg:jar:0.8.2-SNAPSHOT: Could not find artifact > org.apache.atlas:atlas-notification:jar:0.8.2-SNAPSHOT in > apache.snapshots.https > ([https://repository.apache.org/content/repositories/snapshots]) -> [Help 1] > > > > > Seems, Atlas snapshot jars are not found -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (RANGER-1940) Upgrade to Knox 1.0.0
[ https://issues.apache.org/jira/browse/RANGER-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved RANGER-1940. - Resolution: Fixed > Upgrade to Knox 1.0.0 > - > > Key: RANGER-1940 > URL: https://issues.apache.org/jira/browse/RANGER-1940 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 1.0.0 > > Attachments: 0001-RANGER-1940-Upgrade-to-Knox-1.0.0.patch > > > This task is to upgrade to Knox 1.0.0. We can take advantage of the changes > made to the GatewayTestDriver to simplify the test configuration as a result. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-1940) Upgrade to Knox 1.0.0
[ https://issues.apache.org/jira/browse/RANGER-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1940: Attachment: 0001-RANGER-1940-Upgrade-to-Knox-1.0.0.patch > Upgrade to Knox 1.0.0 > - > > Key: RANGER-1940 > URL: https://issues.apache.org/jira/browse/RANGER-1940 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 1.0.0 > > Attachments: 0001-RANGER-1940-Upgrade-to-Knox-1.0.0.patch > > > This task is to upgrade to Knox 1.0.0. We can take advantage of the changes > made to the GatewayTestDriver to simplify the test configuration as a result. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-1940) Upgrade to Knox 1.0.0
[ https://issues.apache.org/jira/browse/RANGER-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1940: Description: This task is to upgrade to Knox 1.0.0. We can take advantage of the changes made to the GatewayTestDriver to simplify the test configuration as a result. (was: This task is to upgrade to Knox 0.14.0. We can take advantage of the changes made to the GatewayTestDriver to simplify the test configuration as a result.) > Upgrade to Knox 1.0.0 > - > > Key: RANGER-1940 > URL: https://issues.apache.org/jira/browse/RANGER-1940 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 1.0.0 > > > This task is to upgrade to Knox 1.0.0. We can take advantage of the changes > made to the GatewayTestDriver to simplify the test configuration as a result. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-1940) Upgrade to Knox 1.0.0
[ https://issues.apache.org/jira/browse/RANGER-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1940: Summary: Upgrade to Knox 1.0.0 (was: Upgrade to Knox 0.14.0) > Upgrade to Knox 1.0.0 > - > > Key: RANGER-1940 > URL: https://issues.apache.org/jira/browse/RANGER-1940 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 1.0.0 > > > This task is to upgrade to Knox 0.14.0. We can take advantage of the changes > made to the GatewayTestDriver to simplify the test configuration as a result. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-1940) Upgrade to Knox 1.0.0
[ https://issues.apache.org/jira/browse/RANGER-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1940: Attachment: (was: 0001-RANGER-1940-Upgrade-to-Knox-0.14.0.patch) > Upgrade to Knox 1.0.0 > - > > Key: RANGER-1940 > URL: https://issues.apache.org/jira/browse/RANGER-1940 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 1.0.0 > > > This task is to upgrade to Knox 1.0.0. We can take advantage of the changes > made to the GatewayTestDriver to simplify the test configuration as a result. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-1970) Build fails - rat issues with storm-agent
[ https://issues.apache.org/jira/browse/RANGER-1970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16350743#comment-16350743 ] Colm O hEigeartaigh commented on RANGER-1970: - Could you try deleting those files + apply this patch locally? It should fix the problem... > Build fails - rat issues with storm-agent > - > > Key: RANGER-1970 > URL: https://issues.apache.org/jira/browse/RANGER-1970 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Nigel Jones >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 1.0.0 > > Attachments: RANGER-1970.patch > > > Cloned ranger source into a clean directory (java is 8 u162 (oracle), OS is > MacOS, maven is 3.5.2), , tried to build using the incantation recommended in > the ranger docs: > -DskipTests=false clean compile package install assembly:assembly > Version info: > 5:23 $ mvn --version > Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d; > 2017-10-18T08:58:13+01:00) > Maven home: /usr/local/Cellar/maven/3.5.2/libexec > Java version: 1.8.0_162, vendor: Oracle Corporation > Java home: > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre > Default locale: en_GB, platform encoding: UTF-8 > OS name: "mac os x", version: "10.13.3", arch: "x86_64", family: "mac" > When doing this the build fails in > [INFO] Rat check: Summary of files. Unapproved: 2 unknown: 2 generated: 0 > approved: 24 licence. > > [INFO] Knox Security Plugin ... SUCCESS [04:50 > min] > [INFO] Storm Security Plugin .. FAILURE [ 18.102 > s] > [INFO] YARN Security Plugin ... SKIPPED > ... > [ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check > (default) on project ranger-storm-plugin: Too many files with unapproved > license: 2 See RAT report in: > /Users/jonesn/IdeaProjects/ranger/storm-agent/target/rat.txt -> [Help 1] > > Looking at the cause I see in the rat.txt: > Unapproved licenses: > /Users/jonesn/IdeaProjects/ranger/storm-agent/logs/workers-artifacts/word-count-1-1517582937/1024/worker.yaml > > /Users/jonesn/IdeaProjects/ranger/storm-agent/logs/workers-artifacts/stormdev-2-1517582937/1027/worker.yaml > > And the files have indeed just been created: > 4:53 $ cd /Users/jonesn/IdeaProjects/ranger/storm-agent/logs/workers-artifacts > ✔ ~/IdeaProjects/ranger/storm-agent/logs/workers-artifacts [master|…3] > 14:53 $ ls > stormdev-2-1517582937 word-count-1-1517582937 > ✔ ~/IdeaProjects/ranger/storm-agent/logs/workers-artifacts [master|…3] > 14:53 $ ls -a > . stormdev-2-1517582937 > .. word-count-1-1517582937 > ✔ ~/IdeaProjects/ranger/storm-agent/logs/workers-artifacts [master|…3] > > So this looks like a build oversight with storm agent - either this needs > clearing up, or ignoring in rat config? > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-1970) Build fails - rat issues with storm-agent
[ https://issues.apache.org/jira/browse/RANGER-1970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1970: Attachment: RANGER-1970.patch > Build fails - rat issues with storm-agent > - > > Key: RANGER-1970 > URL: https://issues.apache.org/jira/browse/RANGER-1970 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Nigel Jones >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 1.0.0 > > Attachments: RANGER-1970.patch > > > Cloned ranger source into a clean directory (java is 8 u162 (oracle), OS is > MacOS, maven is 3.5.2), , tried to build using the incantation recommended in > the ranger docs: > -DskipTests=false clean compile package install assembly:assembly > Version info: > 5:23 $ mvn --version > Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d; > 2017-10-18T08:58:13+01:00) > Maven home: /usr/local/Cellar/maven/3.5.2/libexec > Java version: 1.8.0_162, vendor: Oracle Corporation > Java home: > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre > Default locale: en_GB, platform encoding: UTF-8 > OS name: "mac os x", version: "10.13.3", arch: "x86_64", family: "mac" > When doing this the build fails in > [INFO] Rat check: Summary of files. Unapproved: 2 unknown: 2 generated: 0 > approved: 24 licence. > > [INFO] Knox Security Plugin ... SUCCESS [04:50 > min] > [INFO] Storm Security Plugin .. FAILURE [ 18.102 > s] > [INFO] YARN Security Plugin ... SKIPPED > ... > [ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check > (default) on project ranger-storm-plugin: Too many files with unapproved > license: 2 See RAT report in: > /Users/jonesn/IdeaProjects/ranger/storm-agent/target/rat.txt -> [Help 1] > > Looking at the cause I see in the rat.txt: > Unapproved licenses: > /Users/jonesn/IdeaProjects/ranger/storm-agent/logs/workers-artifacts/word-count-1-1517582937/1024/worker.yaml > > /Users/jonesn/IdeaProjects/ranger/storm-agent/logs/workers-artifacts/stormdev-2-1517582937/1027/worker.yaml > > And the files have indeed just been created: > 4:53 $ cd /Users/jonesn/IdeaProjects/ranger/storm-agent/logs/workers-artifacts > ✔ ~/IdeaProjects/ranger/storm-agent/logs/workers-artifacts [master|…3] > 14:53 $ ls > stormdev-2-1517582937 word-count-1-1517582937 > ✔ ~/IdeaProjects/ranger/storm-agent/logs/workers-artifacts [master|…3] > 14:53 $ ls -a > . stormdev-2-1517582937 > .. word-count-1-1517582937 > ✔ ~/IdeaProjects/ranger/storm-agent/logs/workers-artifacts [master|…3] > > So this looks like a build oversight with storm agent - either this needs > clearing up, or ignoring in rat config? > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (RANGER-1970) Build fails - rat issues with storm-agent
[ https://issues.apache.org/jira/browse/RANGER-1970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh reassigned RANGER-1970: --- Assignee: Colm O hEigeartaigh > Build fails - rat issues with storm-agent > - > > Key: RANGER-1970 > URL: https://issues.apache.org/jira/browse/RANGER-1970 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Nigel Jones >Assignee: Colm O hEigeartaigh >Priority: Major > > Cloned ranger source into a clean directory (java is 8 u162 (oracle), OS is > MacOS, maven is 3.5.2), , tried to build using the incantation recommended in > the ranger docs: > -DskipTests=false clean compile package install assembly:assembly > Version info: > 5:23 $ mvn --version > Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d; > 2017-10-18T08:58:13+01:00) > Maven home: /usr/local/Cellar/maven/3.5.2/libexec > Java version: 1.8.0_162, vendor: Oracle Corporation > Java home: > /Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre > Default locale: en_GB, platform encoding: UTF-8 > OS name: "mac os x", version: "10.13.3", arch: "x86_64", family: "mac" > When doing this the build fails in > [INFO] Rat check: Summary of files. Unapproved: 2 unknown: 2 generated: 0 > approved: 24 licence. > > [INFO] Knox Security Plugin ... SUCCESS [04:50 > min] > [INFO] Storm Security Plugin .. FAILURE [ 18.102 > s] > [INFO] YARN Security Plugin ... SKIPPED > ... > [ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check > (default) on project ranger-storm-plugin: Too many files with unapproved > license: 2 See RAT report in: > /Users/jonesn/IdeaProjects/ranger/storm-agent/target/rat.txt -> [Help 1] > > Looking at the cause I see in the rat.txt: > Unapproved licenses: > /Users/jonesn/IdeaProjects/ranger/storm-agent/logs/workers-artifacts/word-count-1-1517582937/1024/worker.yaml > > /Users/jonesn/IdeaProjects/ranger/storm-agent/logs/workers-artifacts/stormdev-2-1517582937/1027/worker.yaml > > And the files have indeed just been created: > 4:53 $ cd /Users/jonesn/IdeaProjects/ranger/storm-agent/logs/workers-artifacts > ✔ ~/IdeaProjects/ranger/storm-agent/logs/workers-artifacts [master|…3] > 14:53 $ ls > stormdev-2-1517582937 word-count-1-1517582937 > ✔ ~/IdeaProjects/ranger/storm-agent/logs/workers-artifacts [master|…3] > 14:53 $ ls -a > . stormdev-2-1517582937 > .. word-count-1-1517582937 > ✔ ~/IdeaProjects/ranger/storm-agent/logs/workers-artifacts [master|…3] > > So this looks like a build oversight with storm agent - either this needs > clearing up, or ignoring in rat config? > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-1971) Switch to use for-each loops
[ https://issues.apache.org/jira/browse/RANGER-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1971: Attachment: 0001-RANGER-1971-Switch-to-use-for-each-loops.patch > Switch to use for-each loops > > > Key: RANGER-1971 > URL: https://issues.apache.org/jira/browse/RANGER-1971 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Minor > Fix For: 1.0.0 > > Attachments: 0001-RANGER-1971-Switch-to-use-for-each-loops.patch > > > We should switch to use for-each loops in the code, as it is more readable > and concise than using an index. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-1971) Switch to use for-each loops
Colm O hEigeartaigh created RANGER-1971: --- Summary: Switch to use for-each loops Key: RANGER-1971 URL: https://issues.apache.org/jira/browse/RANGER-1971 Project: Ranger Issue Type: Improvement Components: plugins Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 1.0.0 We should switch to use for-each loops in the code, as it is more readable and concise than using an index. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-1969) Fix failing Kafka tests with latest maven/JVM
[ https://issues.apache.org/jira/browse/RANGER-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1969: Attachment: 0001-RANGER-1969-Fix-failing-Kafka-tests-with-latest-mave.patch > Fix failing Kafka tests with latest maven/JVM > - > > Key: RANGER-1969 > URL: https://issues.apache.org/jira/browse/RANGER-1969 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1969-Fix-failing-Kafka-tests-with-latest-mave.patch > > > The Kafka SASL/SSL test is crashing for me with the latest Maven/JVM. > Upgrading the surefire plugin solves the problem. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (RANGER-1969) Fix failing Kafka tests with latest maven/JVM
Colm O hEigeartaigh created RANGER-1969: --- Summary: Fix failing Kafka tests with latest maven/JVM Key: RANGER-1969 URL: https://issues.apache.org/jira/browse/RANGER-1969 Project: Ranger Issue Type: Improvement Components: plugins Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 1.0.0 The Kafka SASL/SSL test is crashing for me with the latest Maven/JVM. Upgrading the surefire plugin solves the problem. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-1967) The Ranger support the Kafka 1.0.0
[ https://issues.apache.org/jira/browse/RANGER-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16344768#comment-16344768 ] Colm O hEigeartaigh commented on RANGER-1967: - Ranger 1.0.0 is coming pretty soon, do you think this feature will be ready for it, or for a future release? > The Ranger support the Kafka 1.0.0 > -- > > Key: RANGER-1967 > URL: https://issues.apache.org/jira/browse/RANGER-1967 > Project: Ranger > Issue Type: New Feature > Components: plugins >Reporter: Qiang Zhang >Assignee: Qiang Zhang >Priority: Major > Labels: newbie, patch > > Now the Ranger don't support the Kafka 1.0.0. We should support the Kafka > 1.0.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RANGER-1964) java.lang.NoClassDefFoundError: org/apache/kafka/common/network/LoginType
[ https://issues.apache.org/jira/browse/RANGER-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16343576#comment-16343576 ] Colm O hEigeartaigh commented on RANGER-1964: - As of right now, Ranger does not support Kafka 1.0.0 (the current version that us supported is 0.10.0.0). > java.lang.NoClassDefFoundError: org/apache/kafka/common/network/LoginType > - > > Key: RANGER-1964 > URL: https://issues.apache.org/jira/browse/RANGER-1964 > Project: Ranger > Issue Type: Wish > Components: Ranger >Reporter: Ronald van de Kuil >Priority: Trivial > Fix For: 0.7.1 > > > Hi, I have Kafka nicely working with Ranger and I noticed that there is an > warning during startup. It does not impact the functioning of Kafka as far as > I can see. I would like to keep the logs tidy, ... so, that, ... amaze, > amaze, nobody ever haves to worry unnecessarily. For this I raised > KAFKA-6338. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-1965) Prevent NPE on decrypting a null password
[ https://issues.apache.org/jira/browse/RANGER-1965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1965: Attachment: 0001-RANGER-1965-Prevent-NPE-on-decrypting-a-null-passwor.patch > Prevent NPE on decrypting a null password > - > > Key: RANGER-1965 > URL: https://issues.apache.org/jira/browse/RANGER-1965 > Project: Ranger > Issue Type: Bug > Components: admin >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Minor > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1965-Prevent-NPE-on-decrypting-a-null-passwor.patch > > > If no password is specified, the logs show a NPE: > java.lang.NullPointerException > at com.sun.jersey.core.util.Base64.decode(Base64.java:324) > at > org.apache.ranger.plugin.util.PasswordUtils.decrypt(PasswordUtils.java:126) > at > org.apache.ranger.plugin.util.PasswordUtils.decryptPassword(PasswordUtils.java:120) > at org.apache.ranger.plugin.client.BaseClient.login(BaseClient.java:108) > at org.apache.ranger.plugin.client.BaseClient.(BaseClient.java:61) > at > org.apache.ranger.services.sqoop.client.SqoopClient.(SqoopClient.java:74) > at > org.apache.ranger.services.sqoop.client.SqoopClient.getSqoopClient(SqoopClient.java:357) > at > org.apache.ranger.services.sqoop.client.SqoopClient.connectionTest(SqoopClient.java:321) > Instead, we should only try to decrypt the password if it's not null. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (RANGER-1954) Specify a version for the native-maven-plugin
[ https://issues.apache.org/jira/browse/RANGER-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1954: Attachment: 0001-RANGER-1954-Specify-a-version-for-the-native-maven-p.patch > Specify a version for the native-maven-plugin > - > > Key: RANGER-1954 > URL: https://issues.apache.org/jira/browse/RANGER-1954 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Trivial > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1954-Specify-a-version-for-the-native-maven-p.patch > > > As we don't specify a version for the native-maven-plugin, the following > warning appears in the console: > [WARNING] Some problems were encountered while building the effective model > for org.apache.ranger:credValidator:uexe:1.0.0-SNAPSHOT > [WARNING] 'build.plugins.plugin.version' for > org.codehaus.mojo:native-maven-plugin is missing. @ > org.apache.ranger:credValidator:[unknown-version], > /ranger/unixauthnative/pom.xml, line 32, column 21 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (RANGER-1954) Specify a version for the native-maven-plugin
Colm O hEigeartaigh created RANGER-1954: --- Summary: Specify a version for the native-maven-plugin Key: RANGER-1954 URL: https://issues.apache.org/jira/browse/RANGER-1954 Project: Ranger Issue Type: Improvement Components: Ranger Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Priority: Trivial Fix For: 1.0.0 As we don't specify a version for the native-maven-plugin, the following warning appears in the console: [WARNING] Some problems were encountered while building the effective model for org.apache.ranger:credValidator:uexe:1.0.0-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.codehaus.mojo:native-maven-plugin is missing. @ org.apache.ranger:credValidator:[unknown-version], /ranger/unixauthnative/pom.xml, line 32, column 21 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (RANGER-689) For Solr plugin, use resources folders for adding Ranger properties
[ https://issues.apache.org/jira/browse/RANGER-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16316651#comment-16316651 ] Colm O hEigeartaigh commented on RANGER-689: Thanks for the testing the patch...I still need a +1 from a Ranger committer though. > For Solr plugin, use resources folders for adding Ranger properties > --- > > Key: RANGER-689 > URL: https://issues.apache.org/jira/browse/RANGER-689 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: 0.5.0 >Reporter: Don Bosco Durai >Assignee: Colm O hEigeartaigh > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-689-For-Solr-plugin-use-resources-folders-for.patch > > > Currently, the jars required by Ranger are added to WEB-INF/lib and > WEB-INF/classes folders. However, Solr recommends to put all extension jars > in server/lib/ext and properties in server/resources > We should update out plugin installer code to use the new location. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1940) Upgrade to Knox 0.14.0
[ https://issues.apache.org/jira/browse/RANGER-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1940: Attachment: 0001-RANGER-1940-Upgrade-to-Knox-0.14.0.patch > Upgrade to Knox 0.14.0 > -- > > Key: RANGER-1940 > URL: https://issues.apache.org/jira/browse/RANGER-1940 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh > Fix For: 1.0.0 > > Attachments: 0001-RANGER-1940-Upgrade-to-Knox-0.14.0.patch > > > This task is to upgrade to Knox 0.14.0. We can take advantage of the changes > made to the GatewayTestDriver to simplify the test configuration as a result. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (RANGER-1940) Upgrade to Knox 0.14.0
Colm O hEigeartaigh created RANGER-1940: --- Summary: Upgrade to Knox 0.14.0 Key: RANGER-1940 URL: https://issues.apache.org/jira/browse/RANGER-1940 Project: Ranger Issue Type: Improvement Components: plugins Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 1.0.0 This task is to upgrade to Knox 0.14.0. We can take advantage of the changes made to the GatewayTestDriver to simplify the test configuration as a result. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1936) Upgrade Ranger to use Java 1.8
[ https://issues.apache.org/jira/browse/RANGER-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1936: Attachment: 0001-RANGER-1936-Upgrade-Ranger-to-use-Java-1.8.patch > Upgrade Ranger to use Java 1.8 > -- > > Key: RANGER-1936 > URL: https://issues.apache.org/jira/browse/RANGER-1936 > Project: Ranger > Issue Type: Improvement > Components: admin, plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh > Fix For: 1.0.0 > > Attachments: 0001-RANGER-1936-Upgrade-Ranger-to-use-Java-1.8.patch > > > As discussed on the mailing list, this task is to upgrade Ranger to use Java > 1.8. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (RANGER-1936) Upgrade Ranger to use Java 1.8
Colm O hEigeartaigh created RANGER-1936: --- Summary: Upgrade Ranger to use Java 1.8 Key: RANGER-1936 URL: https://issues.apache.org/jira/browse/RANGER-1936 Project: Ranger Issue Type: Improvement Components: admin, plugins Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 1.0.0 As discussed on the mailing list, this task is to upgrade Ranger to use Java 1.8. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1935) Upgrade Ranger to support Apache Hadoop 3.0.0
[ https://issues.apache.org/jira/browse/RANGER-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1935: Attachment: 0001-RANGER-1935-Upgrade-Ranger-to-support-Apache-Hadoop-.patch > Upgrade Ranger to support Apache Hadoop 3.0.0 > - > > Key: RANGER-1935 > URL: https://issues.apache.org/jira/browse/RANGER-1935 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1935-Upgrade-Ranger-to-support-Apache-Hadoop-.patch > > > This task is to upgrade Ranger to support Apache Hadoop 3.0.0. Here are some > notes about the upgrade: > a) The Hive plugin needs the Hadoop 3.0.0 jars to run the tests properly, as > Hive only supports the older Hadoop version, so an exclusion and some > additional 3.0.0 dependencies need to be added. > b) The Storm plugin bundles the hadoop-auth jars in storm-core (although they > really should be renamed here). Therefore, we have no option but to package > Storm with the Hadoop 2.7.x jars, until such time that Storm upgrades the > Hadoop dependency. > This is an initial patch to get some feedback. If there is broad agreement on > the upgrade I will test the distributions properly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (RANGER-1935) Upgrade Ranger to support Apache Hadoop 3.0.0
Colm O hEigeartaigh created RANGER-1935: --- Summary: Upgrade Ranger to support Apache Hadoop 3.0.0 Key: RANGER-1935 URL: https://issues.apache.org/jira/browse/RANGER-1935 Project: Ranger Issue Type: Improvement Components: plugins Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 1.0.0 This task is to upgrade Ranger to support Apache Hadoop 3.0.0. Here are some notes about the upgrade: a) The Hive plugin needs the Hadoop 3.0.0 jars to run the tests properly, as Hive only supports the older Hadoop version, so an exclusion and some additional 3.0.0 dependencies need to be added. b) The Storm plugin bundles the hadoop-auth jars in storm-core (although they really should be renamed here). Therefore, we have no option but to package Storm with the Hadoop 2.7.x jars, until such time that Storm upgrades the Hadoop dependency. This is an initial patch to get some feedback. If there is broad agreement on the upgrade I will test the distributions properly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1927) Upgrade Hive to 2.3.2
[ https://issues.apache.org/jira/browse/RANGER-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1927: Attachment: 0001-RANGER-1927-Upgrade-Hive-to-2.3.2.patch > Upgrade Hive to 2.3.2 > - > > Key: RANGER-1927 > URL: https://issues.apache.org/jira/browse/RANGER-1927 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Minor > Fix For: 1.0.0 > > Attachments: 0001-RANGER-1927-Upgrade-Hive-to-2.3.2.patch > > > We should upgrade Hive to a more recent release. Hive 2.3.2 is backwards > compatible to 2.1.0 as far as Ranger is concerned, so no other changes are > required. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (RANGER-1927) Upgrade Hive to 2.3.2
Colm O hEigeartaigh created RANGER-1927: --- Summary: Upgrade Hive to 2.3.2 Key: RANGER-1927 URL: https://issues.apache.org/jira/browse/RANGER-1927 Project: Ranger Issue Type: Improvement Components: plugins Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Priority: Minor Fix For: 1.0.0 We should upgrade Hive to a more recent release. Hive 2.3.2 is backwards compatible to 2.1.0 as far as Ranger is concerned, so no other changes are required. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1926) Upgrade Storm dependency to 1.1.1
[ https://issues.apache.org/jira/browse/RANGER-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1926: Attachment: 0001-RANGER-1926-Upgrade-Storm-dependency-to-1.1.1.patch > Upgrade Storm dependency to 1.1.1 > - > > Key: RANGER-1926 > URL: https://issues.apache.org/jira/browse/RANGER-1926 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Minor > Fix For: 1.0.0 > > Attachments: 0001-RANGER-1926-Upgrade-Storm-dependency-to-1.1.1.patch > > > This task is to upgrade the Storm dependency to 1.1.1. No further changes are > required, as it's backwards compatible with 1.0.x. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (RANGER-1926) Upgrade Storm dependency to 1.1.1
Colm O hEigeartaigh created RANGER-1926: --- Summary: Upgrade Storm dependency to 1.1.1 Key: RANGER-1926 URL: https://issues.apache.org/jira/browse/RANGER-1926 Project: Ranger Issue Type: Improvement Components: plugins Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Priority: Minor Fix For: 1.0.0 This task is to upgrade the Storm dependency to 1.1.1. No further changes are required, as it's backwards compatible with 1.0.x. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1923) Simplify Hive dependencies
[ https://issues.apache.org/jira/browse/RANGER-1923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1923: Attachment: 0001-RANGER-1923-Simplify-Hive-dependencies.patch > Simplify Hive dependencies > -- > > Key: RANGER-1923 > URL: https://issues.apache.org/jira/browse/RANGER-1923 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Minor > Fix For: 1.0.0 > > Attachments: 0001-RANGER-1923-Simplify-Hive-dependencies.patch > > > This task is to simplify the Hive plugin dependencies. The plugin itself has > a dependency on the Hadoop HDFS jar that is not required, similarly the Shim > has some dependencies on other Hadoop jars. > With Hive, we pick up the relevant jars from the Hadoop distribution, so > Ranger does not have to ship any Hadoop jars. > No changes are made to the jars shipped in the plugin distribution. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (RANGER-1923) Simplify Hive dependencies
Colm O hEigeartaigh created RANGER-1923: --- Summary: Simplify Hive dependencies Key: RANGER-1923 URL: https://issues.apache.org/jira/browse/RANGER-1923 Project: Ranger Issue Type: Improvement Components: plugins Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Priority: Minor Fix For: 1.0.0 This task is to simplify the Hive plugin dependencies. The plugin itself has a dependency on the Hadoop HDFS jar that is not required, similarly the Shim has some dependencies on other Hadoop jars. With Hive, we pick up the relevant jars from the Hadoop distribution, so Ranger does not have to ship any Hadoop jars. No changes are made to the jars shipped in the plugin distribution. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1922) Simplify HBase dependencies
[ https://issues.apache.org/jira/browse/RANGER-1922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1922: Attachment: 0001-RANGER-1922-Simplify-HBase-dependencies.patch > Simplify HBase dependencies > --- > > Key: RANGER-1922 > URL: https://issues.apache.org/jira/browse/RANGER-1922 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh > Fix For: 1.0.0 > > Attachments: 0001-RANGER-1922-Simplify-HBase-dependencies.patch > > > This task is to simplify the HBase dependencies: > a) We don't need to specify the Solr jar as it gets picked up from the audit > module. > b) We don't need to specify the HDFS jar as we don't bundle it in the > distribution - the jar is picked up from HBase itself. > c) The 2.7.1 Hadoop dependencies in the HBase pom should be removed - instead > we should just pick up the Hadoop dependencies required for testing from the > Hadoop version that ships with HBase. > This work means that the HBase module compiles + tests work correctly when we > upgrade to Hadoop 3.0.0. > No changes to the distribution jars. Tested HDFS + Solr auditing still works > as expected with the plugin. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (RANGER-1922) Simplify HBase dependencies
Colm O hEigeartaigh created RANGER-1922: --- Summary: Simplify HBase dependencies Key: RANGER-1922 URL: https://issues.apache.org/jira/browse/RANGER-1922 Project: Ranger Issue Type: Improvement Components: plugins Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 1.0.0 This task is to simplify the HBase dependencies: a) We don't need to specify the Solr jar as it gets picked up from the audit module. b) We don't need to specify the HDFS jar as we don't bundle it in the distribution - the jar is picked up from HBase itself. c) The 2.7.1 Hadoop dependencies in the HBase pom should be removed - instead we should just pick up the Hadoop dependencies required for testing from the Hadoop version that ships with HBase. This work means that the HBase module compiles + tests work correctly when we upgrade to Hadoop 3.0.0. No changes to the distribution jars. Tested HDFS + Solr auditing still works as expected with the plugin. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1920) Remove SOLR dependencies from the KMS service + plugins
[ https://issues.apache.org/jira/browse/RANGER-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1920: Attachment: 0001-RANGER-1920-Remove-SOLR-dependencies-from-the-KMS-se.patch > Remove SOLR dependencies from the KMS service + plugins > --- > > Key: RANGER-1920 > URL: https://issues.apache.org/jira/browse/RANGER-1920 > Project: Ranger > Issue Type: Improvement > Components: kms, plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1920-Remove-SOLR-dependencies-from-the-KMS-se.patch > > > The SOLR dependencies are not required in the KMS service, or the KMS > plugins, as the jar is instead on the classpath via plugins-audit. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1893) Update HBase dependency to 1.2.6
[ https://issues.apache.org/jira/browse/RANGER-1893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1893: Attachment: 0001-RANGER-1893-Update-HBase-dependency-to-1.2.6.patch > Update HBase dependency to 1.2.6 > > > Key: RANGER-1893 > URL: https://issues.apache.org/jira/browse/RANGER-1893 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh > Fix For: 1.0.0 > > Attachments: 0001-RANGER-1893-Update-HBase-dependency-to-1.2.6.patch > > > We currently rely on an old HBase dependency (1.1.3). This task is to upgrade > it to 1.2.6. The plugin works correctly with no changes since 1.1.x. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1893) Update HBase dependency to 1.2.6
[ https://issues.apache.org/jira/browse/RANGER-1893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1893: Attachment: (was: 0001-RANGER-1893-Update-HBase-dependency-to-1.2.6.patch) > Update HBase dependency to 1.2.6 > > > Key: RANGER-1893 > URL: https://issues.apache.org/jira/browse/RANGER-1893 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh > Fix For: 1.0.0 > > > We currently rely on an old HBase dependency (1.1.3). This task is to upgrade > it to 1.2.6. The plugin works correctly with no changes since 1.1.x. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1917) Remove solr dependency from Kafka + Sqoop modules
[ https://issues.apache.org/jira/browse/RANGER-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1917: Attachment: 0001-RANGER-1917-Remove-solr-dependency-from-Kafka-Sqoop-.patch > Remove solr dependency from Kafka + Sqoop modules > - > > Key: RANGER-1917 > URL: https://issues.apache.org/jira/browse/RANGER-1917 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1917-Remove-solr-dependency-from-Kafka-Sqoop-.patch > > > This task is to remove the solr dependency from the Kafka + Sqoop modules, > as it is picked up on the classpath from the audit module instead. No changes > to the distribution jars - also tested Solr auditing as a sanity test for > both. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (RANGER-1917) Remove solr dependency from Kafka + Sqoop modules
Colm O hEigeartaigh created RANGER-1917: --- Summary: Remove solr dependency from Kafka + Sqoop modules Key: RANGER-1917 URL: https://issues.apache.org/jira/browse/RANGER-1917 Project: Ranger Issue Type: Improvement Components: plugins Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 1.0.0 This task is to remove the solr dependency from the Kafka + Sqoop modules, as it is picked up on the classpath from the audit module instead. No changes to the distribution jars - also tested Solr auditing as a sanity test for both. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (RANGER-1913) build fail with JDK 9
[ https://issues.apache.org/jira/browse/RANGER-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16276559#comment-16276559 ] Colm O hEigeartaigh commented on RANGER-1913: - Ranger doesn't currently build with JDK9. Either JDK 8 or 7 should be fine. > build fail with JDK 9 > - > > Key: RANGER-1913 > URL: https://issues.apache.org/jira/browse/RANGER-1913 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: 0.7.1 > Environment: Ubuntu 16.04 > mvn -version > Apache Maven 3.3.9 > Maven home: /usr/share/maven > Java version: 9.0.1, vendor: Oracle Corporation > Java home: /usr/lib/jvm/java-9-oracle > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "4.10.0-40-generic", arch: "amd64", family: "unix" >Reporter: Ronald van de Kuil >Priority: Minor > > [ERROR] Failed to execute goal on project ranger-hbase-plugin-shim: Could not > resolve dependencies for project > org.apache.ranger:ranger-hbase-plugin-shim:jar:0.7.1: Could not find artifact > jdk.tools:jdk.tools:jar:1.7 at specified path > /usr/lib/jvm/java-9-oracle/../lib/tools.jar -> [Help 1 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (RANGER-1882) Compilation error in kms module with Hadoop 2.8.x
[ https://issues.apache.org/jira/browse/RANGER-1882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed RANGER-1882. --- > Compilation error in kms module with Hadoop 2.8.x > - > > Key: RANGER-1882 > URL: https://issues.apache.org/jira/browse/RANGER-1882 > Project: Ranger > Issue Type: Improvement > Components: kms >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Minor > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1882-Compilation-error-in-kms-module-with-Had.patch > > > There is a compilation failure in the KMS module when compiled with Hadoop > 2.8.x. The fix is just to use a constant String which works with both Hadoop > 2.7.x, 2.8.x. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1906) Simplify Atlas plugin dependency management
[ https://issues.apache.org/jira/browse/RANGER-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1906: Attachment: 0001-RANGER-1906-Simplify-Atlas-plugin-dependency-managem.patch > Simplify Atlas plugin dependency management > --- > > Key: RANGER-1906 > URL: https://issues.apache.org/jira/browse/RANGER-1906 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Minor > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1906-Simplify-Atlas-plugin-dependency-managem.patch > > > This task is to simplify the dependency management for the Atlas plugin. In > particular, the hadoop/solr dependencies should just be imported via the > ranger-plugin-commons dependency. > No changes are made to the resulting jars for the Atlas distribution. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1906) Simplify Atlas plugin dependency management
[ https://issues.apache.org/jira/browse/RANGER-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1906: Attachment: (was: 0001-RANGER-1906-Simplify-Atlas-plugin-dependency-managem.patch) > Simplify Atlas plugin dependency management > --- > > Key: RANGER-1906 > URL: https://issues.apache.org/jira/browse/RANGER-1906 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Minor > Fix For: 1.0.0 > > > This task is to simplify the dependency management for the Atlas plugin. In > particular, the hadoop/solr dependencies should just be imported via the > ranger-plugin-commons dependency. > No changes are made to the resulting jars for the Atlas distribution. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1898) Simplify Knox plugin dependency management
[ https://issues.apache.org/jira/browse/RANGER-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1898: Attachment: 0001-RANGER-1898-Simplify-Knox-plugin-dependency-manageme.patch > Simplify Knox plugin dependency management > -- > > Key: RANGER-1898 > URL: https://issues.apache.org/jira/browse/RANGER-1898 > Project: Ranger > Issue Type: Bug > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Minor > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1898-Simplify-Knox-plugin-dependency-manageme.patch > > > This task is to simplify the dependency management for the Knox plugin for > Ranger. > Tested that the distribution ships the same jars as before. Also tested a > use-case involving Ranger + Knox. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1898) Simplify Knox plugin dependency management
[ https://issues.apache.org/jira/browse/RANGER-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1898: Attachment: (was: 0001-RANGER-1898-Simplify-Knox-plugin-dependency-manageme.patch) > Simplify Knox plugin dependency management > -- > > Key: RANGER-1898 > URL: https://issues.apache.org/jira/browse/RANGER-1898 > Project: Ranger > Issue Type: Bug > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Minor > Fix For: 1.0.0 > > > This task is to simplify the dependency management for the Knox plugin for > Ranger. > Tested that the distribution ships the same jars as before. Also tested a > use-case involving Ranger + Knox. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1898) Simplify Knox plugin dependency management
[ https://issues.apache.org/jira/browse/RANGER-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1898: Attachment: 0001-RANGER-1898-Simplify-Knox-plugin-dependency-manageme.patch > Simplify Knox plugin dependency management > -- > > Key: RANGER-1898 > URL: https://issues.apache.org/jira/browse/RANGER-1898 > Project: Ranger > Issue Type: Bug > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Minor > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1898-Simplify-Knox-plugin-dependency-manageme.patch > > > This task is to simplify the dependency management for the Knox plugin for > Ranger. > Tested that the distribution ships the same jars as before. Also tested a > use-case involving Ranger + Knox. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1898) Simplify Knox plugin dependency management
[ https://issues.apache.org/jira/browse/RANGER-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1898: Attachment: (was: 0001-RANGER-1898-Simplify-Knox-plugin-dependency-manageme.patch) > Simplify Knox plugin dependency management > -- > > Key: RANGER-1898 > URL: https://issues.apache.org/jira/browse/RANGER-1898 > Project: Ranger > Issue Type: Bug > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Minor > Fix For: 1.0.0 > > > This task is to simplify the dependency management for the Knox plugin for > Ranger. > Tested that the distribution ships the same jars as before. Also tested a > use-case involving Ranger + Knox. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1898) Simplify Knox plugin dependency management
[ https://issues.apache.org/jira/browse/RANGER-1898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1898: Description: This task is to simplify the dependency management for the Knox plugin for Ranger. Tested that the distribution ships the same jars as before. Also tested a use-case involving Ranger + Knox. was: This task is to simplify the dependency management for the Knox plugin for Ranger. In addition, the hadoop-hdfs jar is removed from the distribution, as it is not required. Tested that the distribution ships the same jars as before, apart from hadoop-hdfs. Also tested a use-case involving Ranger + Knox. > Simplify Knox plugin dependency management > -- > > Key: RANGER-1898 > URL: https://issues.apache.org/jira/browse/RANGER-1898 > Project: Ranger > Issue Type: Bug > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Minor > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1898-Simplify-Knox-plugin-dependency-manageme.patch > > > This task is to simplify the dependency management for the Knox plugin for > Ranger. > Tested that the distribution ships the same jars as before. Also tested a > use-case involving Ranger + Knox. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1895) Simplify Storm dependencies
[ https://issues.apache.org/jira/browse/RANGER-1895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1895: Attachment: 0001-RANGER-1895-Simplify-Storm-dependencies.patch > Simplify Storm dependencies > --- > > Key: RANGER-1895 > URL: https://issues.apache.org/jira/browse/RANGER-1895 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Minor > Fix For: 1.0.0 > > Attachments: 0001-RANGER-1895-Simplify-Storm-dependencies.patch > > > This task is to simplify the Apache Storm dependencies for Ranger. We can > avoid explicitly listing some of the dependencies, as they get pulled in via > other dependencies. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1895) Simplify Storm dependencies
[ https://issues.apache.org/jira/browse/RANGER-1895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1895: Attachment: (was: 0001-RANGER-1895-Simplify-Storm-dependencies.patch) > Simplify Storm dependencies > --- > > Key: RANGER-1895 > URL: https://issues.apache.org/jira/browse/RANGER-1895 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Minor > Fix For: 1.0.0 > > > This task is to simplify the Apache Storm dependencies for Ranger. We can > avoid explicitly listing some of the dependencies, as they get pulled in via > other dependencies. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1895) Simplify Storm dependencies
[ https://issues.apache.org/jira/browse/RANGER-1895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1895: Description: This task is to simplify the Apache Storm dependencies for Ranger. We can avoid explicitly listing some of the dependencies, as they get pulled in via other dependencies. (was: This task is to simplify the Apache Storm dependencies for Ranger. We are shipping the hadoop-hdfs jar, which is not required. Secondly, we can avoid explicitly listing some of the dependencies, as they get pulled in via other dependencies.) > Simplify Storm dependencies > --- > > Key: RANGER-1895 > URL: https://issues.apache.org/jira/browse/RANGER-1895 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Minor > Fix For: 1.0.0 > > > This task is to simplify the Apache Storm dependencies for Ranger. We can > avoid explicitly listing some of the dependencies, as they get pulled in via > other dependencies. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (RANGER-1908) Build (unit tests) failed in HBase Security Plugin
[ https://issues.apache.org/jira/browse/RANGER-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16266633#comment-16266633 ] Colm O hEigeartaigh commented on RANGER-1908: - Hi Nigel, Could you try applying this patch locally and see if you still see the test failure? https://issues.apache.org/jira/browse/RANGER-1893 The admin.disableTable is synchronous, and so the table should be disabled after the call returns, so this looks to me like a bug possibly in the old version of HBase we are using. > Build (unit tests) failed in HBase Security Plugin > -- > > Key: RANGER-1908 > URL: https://issues.apache.org/jira/browse/RANGER-1908 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Nigel Jones > Attachments: ranger-20171124a.log > > > MacOS > Java 1.8 (152, oracle) > Maven 3.5.0 > Build fails at > [INFO] HBase Security Plugin .. FAILURE [11:36 > min] > The failing test is: > [INFO] Running > org.apache.ranger.authorization.hbase.HBaseRangerAuthorizationTest > Formatting using clusterid: testClusterID > [ERROR] Tests run: 20, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: > 689.962 s <<< FAILURE! - in > org.apache.ranger.authorization.hbase.HBaseRangerAuthorizationTest > [ERROR] > testTagBasedTablePolicy(org.apache.ranger.authorization.hbase.HBaseRangerAuthorizationTest) > Time elapsed: 611.879 s <<< ERROR! > org.apache.hadoop.hbase.exceptions.TimeoutIOException: > java.util.concurrent.TimeoutException: The procedure 18 is still running > at > org.apache.ranger.authorization.hbase.HBaseRangerAuthorizationTest.testTagBasedTablePolicy(HBaseRangerAuthorizationTest.java:780) > Caused by: java.util.concurrent.TimeoutException: The procedure 18 is still > running > at > org.apache.ranger.authorization.hbase.HBaseRangerAuthorizationTest.testTagBasedTablePolicy(HBaseRangerAuthorizationTest.java:780) > The next part of the test is ok: > [INFO] Running > org.apache.ranger.authorization.hbase.RangerAuthorizationFilterTest > [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.505 > s - in org.apache.ranger.authorization.hbase.RangerAuthorizationFilterTest -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1906) Simplify Atlas plugin dependency management
[ https://issues.apache.org/jira/browse/RANGER-1906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1906: Attachment: 0001-RANGER-1906-Simplify-Atlas-plugin-dependency-managem.patch > Simplify Atlas plugin dependency management > --- > > Key: RANGER-1906 > URL: https://issues.apache.org/jira/browse/RANGER-1906 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Minor > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1906-Simplify-Atlas-plugin-dependency-managem.patch > > > This task is to simplify the dependency management for the Atlas plugin. In > particular, the hadoop/solr dependencies should just be imported via the > ranger-plugin-commons dependency. > No changes are made to the resulting jars for the Atlas distribution. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (RANGER-1906) Simplify Atlas plugin dependency management
Colm O hEigeartaigh created RANGER-1906: --- Summary: Simplify Atlas plugin dependency management Key: RANGER-1906 URL: https://issues.apache.org/jira/browse/RANGER-1906 Project: Ranger Issue Type: Improvement Components: plugins Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Priority: Minor Fix For: 1.0.0 This task is to simplify the dependency management for the Atlas plugin. In particular, the hadoop/solr dependencies should just be imported via the ranger-plugin-commons dependency. No changes are made to the resulting jars for the Atlas distribution. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (RANGER-1895) Simplify Storm dependencies
[ https://issues.apache.org/jira/browse/RANGER-1895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1895: Attachment: (was: 0001-RANGER-1895-Simplify-Storm-dependencies.patch) > Simplify Storm dependencies > --- > > Key: RANGER-1895 > URL: https://issues.apache.org/jira/browse/RANGER-1895 > Project: Ranger > Issue Type: Improvement > Components: plugins >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Minor > Fix For: 1.0.0 > > Attachments: 0001-RANGER-1895-Simplify-Storm-dependencies.patch > > > This task is to simplify the Apache Storm dependencies for Ranger. We are > shipping the hadoop-hdfs jar, which is not required. Secondly, we can avoid > explicitly listing some of the dependencies, as they get pulled in via other > dependencies. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
