[jira] [Resolved] (RANGER-1322) A tag source file has wrong service name for Hive resources
[ https://issues.apache.org/jira/browse/RANGER-1322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved RANGER-1322. - Resolution: Won't Fix Marking this as "Won't fix" as per Abhay's comment on the reviewboard. > A tag source file has wrong service name for Hive resources > --- > > Key: RANGER-1322 > URL: https://issues.apache.org/jira/browse/RANGER-1322 > Project: Ranger > Issue Type: Bug > Components: tagsync >Affects Versions: 0.7.0, 0.6.2 >Reporter: Yan >Priority: Trivial > > In tagsync/src/main/resources/etc/ranger/data/tags.json, the service name for > the "serviceResources" should be "hivedev" instead of "cl1_hive" which is the > tag service name. This has caused the tag sync using the file to fail to be > imported to the Ranger Admin. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (RANGER-1514) Remove EasyMock dependency
Colm O hEigeartaigh created RANGER-1514: --- Summary: Remove EasyMock dependency Key: RANGER-1514 URL: https://issues.apache.org/jira/browse/RANGER-1514 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 EasyMock dependency and replace it with Mockito. There are two reasons for doing this: a) We have a single mock framework across the entire project. b) EasyMock does not seem to be actively maintained any more, and currently does not support Java 9. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1514) Remove EasyMock dependency
[ https://issues.apache.org/jira/browse/RANGER-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1514: Attachment: 0001-RANGER-1514-Remove-EasyMock-dependency.patch > Remove EasyMock dependency > -- > > Key: RANGER-1514 > URL: https://issues.apache.org/jira/browse/RANGER-1514 > Project: Ranger > Issue Type: Improvement > Components: plugins > Reporter: Colm O hEigeartaigh > Assignee: Colm O hEigeartaigh > Fix For: 1.0.0 > > Attachments: 0001-RANGER-1514-Remove-EasyMock-dependency.patch > > > This task is to remove the EasyMock dependency and replace it with Mockito. > There are two reasons for doing this: > a) We have a single mock framework across the entire project. > b) EasyMock does not seem to be actively maintained any more, and currently > does not support Java 9. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (RANGER-1516) Remove remaining *-plugin-install.properties
Colm O hEigeartaigh created RANGER-1516: --- Summary: Remove remaining *-plugin-install.properties Key: RANGER-1516 URL: https://issues.apache.org/jira/browse/RANGER-1516 Project: Ranger Issue Type: Improvement Components: plugins Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 1.0.0 RANGER-1457 removed the yarn-plugin-install.properties. We should do the same for the two remaining plugins that use them, namely Kafka + Solr. They are redundant in both cases, as the COMPONENT_INSTALL_DIR_NAME is already in install.properties. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1516) Remove remaining *-plugin-install.properties
[ https://issues.apache.org/jira/browse/RANGER-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1516: Attachment: 0001-RANGER-1516-Remove-remaining-plugin-install.properti.patch > Remove remaining *-plugin-install.properties > > > Key: RANGER-1516 > URL: https://issues.apache.org/jira/browse/RANGER-1516 > Project: Ranger > Issue Type: Improvement > Components: plugins > Reporter: Colm O hEigeartaigh > Assignee: Colm O hEigeartaigh > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1516-Remove-remaining-plugin-install.properti.patch > > > RANGER-1457 removed the yarn-plugin-install.properties. We should do the same > for the two remaining plugins that use them, namely Kafka + Solr. They are > redundant in both cases, as the COMPONENT_INSTALL_DIR_NAME is already in > install.properties. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (RANGER-1523) Add AtlasResourceMapper implementation for Apache Storm
Colm O hEigeartaigh created RANGER-1523: --- Summary: Add AtlasResourceMapper implementation for Apache Storm Key: RANGER-1523 URL: https://issues.apache.org/jira/browse/RANGER-1523 Project: Ranger Issue Type: New Feature Components: tagsync Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 1.0.0 This task is to add a AtlasResourceMapper implementation for Apache Storm. This will allow us to sync tags associated with Storm topologies into Ranger via the REST aproach + to create tag based authorization policies as a result. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1523) Add AtlasResourceMapper implementation for Apache Storm
[ https://issues.apache.org/jira/browse/RANGER-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1523: Attachment: 0001-RANGER-1523-Add-AtlasResourceMapper-implementation-f.patch > Add AtlasResourceMapper implementation for Apache Storm > --- > > Key: RANGER-1523 > URL: https://issues.apache.org/jira/browse/RANGER-1523 > Project: Ranger > Issue Type: New Feature > Components: tagsync > Reporter: Colm O hEigeartaigh > Assignee: Colm O hEigeartaigh > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1523-Add-AtlasResourceMapper-implementation-f.patch > > > This task is to add a AtlasResourceMapper implementation for Apache Storm. > This will allow us to sync tags associated with Storm topologies into Ranger > via the REST aproach + to create tag based authorization policies as a result. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (RANGER-1524) Add tag based authorization tests for Apache Storm
Colm O hEigeartaigh created RANGER-1524: --- Summary: Add tag based authorization tests for Apache Storm Key: RANGER-1524 URL: https://issues.apache.org/jira/browse/RANGER-1524 Project: Ranger Issue Type: Test Components: plugins Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 1.0.0 Similar to RANGER-1421, this task is to add a test for tag based authorization to the Storm component. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1524) Add tag based authorization tests for Apache Storm
[ https://issues.apache.org/jira/browse/RANGER-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1524: Attachment: 0001-RANGER-1524-Add-tag-based-authorization-tests-for-Ap.patch > Add tag based authorization tests for Apache Storm > -- > > Key: RANGER-1524 > URL: https://issues.apache.org/jira/browse/RANGER-1524 > Project: Ranger > Issue Type: Test > Components: plugins > Reporter: Colm O hEigeartaigh > Assignee: Colm O hEigeartaigh > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1524-Add-tag-based-authorization-tests-for-Ap.patch > > > Similar to RANGER-1421, this task is to add a test for tag based > authorization to the Storm component. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1499) Upgrade Tomcat version
[ https://issues.apache.org/jira/browse/RANGER-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15973011#comment-15973011 ] Colm O hEigeartaigh commented on RANGER-1499: - Hi [~vperiasamy], no reason specifically to update to 7.0.77. It's a trade-off between shipping with known bugs versus unknown bugs of a new version. I would always lean to picking up the latest (minor) release + testing it properly, but I'll leave the decision up to you either way here. > Upgrade Tomcat version > -- > > Key: RANGER-1499 > URL: https://issues.apache.org/jira/browse/RANGER-1499 > Project: Ranger > Issue Type: Bug > Components: Ranger >Reporter: Velmurugan Periasamy > Fix For: 0.6.4, 1.0.0, 0.7.1 > > > Tomcat version used by Ranger & Ranger KMS is 7.0.68. > Need to upgrade to 7.0.73 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (RANGER-1497) Improvement of unit test coverage for ranger
[ https://issues.apache.org/jira/browse/RANGER-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved RANGER-1497. - Resolution: Fixed > Improvement of unit test coverage for ranger > - > > Key: RANGER-1497 > URL: https://issues.apache.org/jira/browse/RANGER-1497 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Reporter: Deepak Sharma >Assignee: Deepak Sharma > Fix For: 1.0.0, 0.7.1 > > > Improvement of unit test coverage for ranger by adding the unit tests for > org.apache.ranger.rest.AssetREST. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (RANGER-1527) Make curator dependencies consistent
Colm O hEigeartaigh created RANGER-1527: --- Summary: Make curator dependencies consistent Key: RANGER-1527 URL: https://issues.apache.org/jira/browse/RANGER-1527 Project: Ranger Issue Type: Improvement Components: kms Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 1.0.0 There are some inconsistencies with the curator dependencies. This patch addresses the following issues: a) Remove unneeded "curator-test" test dependency in the KMS module. b) Upgrade curator dependency from 2.7.0 -> 2.7.1 to be consistent with the dependency coming in from Hadoop. c) Remove curator-recipies 2.6.0 dependency in kms - instead curator-recipies 2.7.1 is pulled in from Hadoop. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1527) Make curator dependencies consistent
[ https://issues.apache.org/jira/browse/RANGER-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1527: Attachment: 0001-RANGER-1527-Make-curator-dependencies-consistent.patch > Make curator dependencies consistent > > > Key: RANGER-1527 > URL: https://issues.apache.org/jira/browse/RANGER-1527 > Project: Ranger > Issue Type: Improvement > Components: kms > Reporter: Colm O hEigeartaigh > Assignee: Colm O hEigeartaigh > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1527-Make-curator-dependencies-consistent.patch > > > There are some inconsistencies with the curator dependencies. This patch > addresses the following issues: > a) Remove unneeded "curator-test" test dependency in the KMS module. > b) Upgrade curator dependency from 2.7.0 -> 2.7.1 to be consistent with the > dependency coming in from Hadoop. > c) Remove curator-recipies 2.6.0 dependency in kms - instead curator-recipies > 2.7.1 is pulled in from Hadoop. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (RANGER-1364) MySQLPLRunner take wrong start index when traverse the resultSet metadata
[ https://issues.apache.org/jira/browse/RANGER-1364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved RANGER-1364. - Resolution: Fixed > MySQLPLRunner take wrong start index when traverse the resultSet metadata > - > > Key: RANGER-1364 > URL: https://issues.apache.org/jira/browse/RANGER-1364 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 0.7.0 >Reporter: zhangxiong > Fix For: 1.0.0 > > Attachments: > 0001-change-mysql-ResultSetMetaData-traverse-index-from-0.patch > > Original Estimate: 1h > Remaining Estimate: 1h > > when we install the admin,the dba_script.py would call MySQLRunner to run > some sqls from file or input string.But MySQLRunner take wrong start index > when traverse then resultSet colname.According to jdbc specification,we > should get the rs first column name with index 1 NOT 0. But take 0 as start > index is what ranger does. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (RANGER-1528) Update Maven jar plugin
Colm O hEigeartaigh created RANGER-1528: --- Summary: Update Maven jar plugin Key: RANGER-1528 URL: https://issues.apache.org/jira/browse/RANGER-1528 Project: Ranger Issue Type: Improvement Components: build-infra Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 1.0.0 This task is to update the Maven jar plugin from 2.6 to 3.0.2. 2.6 does not work with Java 9. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1528) Update Maven jar plugin
[ https://issues.apache.org/jira/browse/RANGER-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1528: Attachment: 0001-RANGER-1528-Update-Maven-jar-plugin.patch > Update Maven jar plugin > --- > > Key: RANGER-1528 > URL: https://issues.apache.org/jira/browse/RANGER-1528 > Project: Ranger > Issue Type: Improvement > Components: build-infra > Reporter: Colm O hEigeartaigh > Assignee: Colm O hEigeartaigh > Fix For: 1.0.0 > > Attachments: 0001-RANGER-1528-Update-Maven-jar-plugin.patch > > > This task is to update the Maven jar plugin from 2.6 to 3.0.2. 2.6 does not > work with Java 9. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (RANGER-1529) Remove tez dependency from Hive/HDFS plugins
Colm O hEigeartaigh created RANGER-1529: --- Summary: Remove tez dependency from Hive/HDFS plugins Key: RANGER-1529 URL: https://issues.apache.org/jira/browse/RANGER-1529 Project: Ranger Issue Type: Improvement Components: plugins Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 1.0.0 There are some tez dependencies listed as "optional" for both the Hive + HDFS plugins. They should be removed as they are not required and are not included in the distribution, and are dragging some old dependencies into the build classpath for those modules. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1529) Remove tez dependency from Hive/HDFS plugins
[ https://issues.apache.org/jira/browse/RANGER-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1529: Attachment: 0001-RANGER-1529-Remove-tez-dependency-from-Hive-HDFS-plu.patch > Remove tez dependency from Hive/HDFS plugins > > > Key: RANGER-1529 > URL: https://issues.apache.org/jira/browse/RANGER-1529 > Project: Ranger > Issue Type: Improvement > Components: plugins > Reporter: Colm O hEigeartaigh > Assignee: Colm O hEigeartaigh > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1529-Remove-tez-dependency-from-Hive-HDFS-plu.patch > > > There are some tez dependencies listed as "optional" for both the Hive + HDFS > plugins. They should be removed as they are not required and are not included > in the distribution, and are dragging some old dependencies into the build > classpath for those modules. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1530) NPE in HadoopConfigHolder
[ https://issues.apache.org/jira/browse/RANGER-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1530: Fix Version/s: 0.7.1 > NPE in HadoopConfigHolder > - > > Key: RANGER-1530 > URL: https://issues.apache.org/jira/browse/RANGER-1530 > Project: Ranger > Issue Type: Bug > Components: plugins > Reporter: Colm O hEigeartaigh > Assignee: Colm O hEigeartaigh > Fix For: 1.0.0, 0.7.1 > > Attachments: 0001-RANGER-1530-NPE-in-HadoopConfigHolder.patch > > > RANGER-1483 has introduced a NPE in HadoopConfigHolder if the > ENABLE_HIVE_METASTORE_LOOKUP property is not configured. There is a related > problem in HdfsClient. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1530) NPE in HadoopConfigHolder
[ https://issues.apache.org/jira/browse/RANGER-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1530: Attachment: 0001-RANGER-1530-NPE-in-HadoopConfigHolder.patch > NPE in HadoopConfigHolder > - > > Key: RANGER-1530 > URL: https://issues.apache.org/jira/browse/RANGER-1530 > Project: Ranger > Issue Type: Bug > Components: plugins > Reporter: Colm O hEigeartaigh > Assignee: Colm O hEigeartaigh > Fix For: 1.0.0, 0.7.1 > > Attachments: 0001-RANGER-1530-NPE-in-HadoopConfigHolder.patch > > > RANGER-1483 has introduced a NPE in HadoopConfigHolder if the > ENABLE_HIVE_METASTORE_LOOKUP property is not configured. There is a related > problem in HdfsClient. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (RANGER-1530) NPE in HadoopConfigHolder
Colm O hEigeartaigh created RANGER-1530: --- Summary: NPE in HadoopConfigHolder Key: RANGER-1530 URL: https://issues.apache.org/jira/browse/RANGER-1530 Project: Ranger Issue Type: Bug Components: plugins Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 1.0.0 Attachments: 0001-RANGER-1530-NPE-in-HadoopConfigHolder.patch RANGER-1483 has introduced a NPE in HadoopConfigHolder if the ENABLE_HIVE_METASTORE_LOOKUP property is not configured. There is a related problem in HdfsClient. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1433) Enabled secure processing feature
[ https://issues.apache.org/jira/browse/RANGER-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1433: Fix Version/s: 0.7.1 > Enabled secure processing feature > - > > Key: RANGER-1433 > URL: https://issues.apache.org/jira/browse/RANGER-1433 > Project: Ranger > Issue Type: Improvement > Components: plugins > Reporter: Colm O hEigeartaigh > Assignee: Colm O hEigeartaigh >Priority: Minor > Fix For: 1.0.0, 0.7.1 > > Attachments: 0001-RANGER-1433-Enabled-secure-processing-feature.patch > > > This task is to enable the secure processing feature on all > DocumentBuilderFactory/TransformerFactory instances. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1433) Enabled secure processing feature
[ https://issues.apache.org/jira/browse/RANGER-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1433: Fix Version/s: (was: 0.7.1) > Enabled secure processing feature > - > > Key: RANGER-1433 > URL: https://issues.apache.org/jira/browse/RANGER-1433 > 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-1433-Enabled-secure-processing-feature.patch > > > This task is to enable the secure processing feature on all > DocumentBuilderFactory/TransformerFactory instances. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1536) Error information in the printed logs
[
https://issues.apache.org/jira/browse/RANGER-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh updated RANGER-1536:
Fix Version/s: 1.0.0
> Error information in the printed logs
> -
>
> Key: RANGER-1536
> URL: https://issues.apache.org/jira/browse/RANGER-1536
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Reporter: Qiang Zhang
>Assignee: Qiang Zhang
>Priority: Minor
> Labels: patch
> Fix For: 1.0.0
>
>
> {code}
> if(StringUtils.isEmpty(nameRules)){
> if(LOG.isDebugEnabled()){
> LOG.debug("Name is empty. Setting Name Rule as 'DEFAULT'");
>}
> nameRules = DEFAULT_NAME_RULE;
> }
> {code}
> we should change "Name is empty. Setting Name Rule as 'DEFAULT'" to "Name
> Rule is empty. Setting Name Rule as 'DEFAULT'"
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (RANGER-1539) Improve, modify print log display method name
[
https://issues.apache.org/jira/browse/RANGER-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh updated RANGER-1539:
Fix Version/s: 1.0.0
> Improve, modify print log display method name
> -
>
> Key: RANGER-1539
> URL: https://issues.apache.org/jira/browse/RANGER-1539
> Project: Ranger
> Issue Type: Improvement
> Components: plugins
>Affects Versions: master
>Reporter: Qiang Zhang
>Assignee: Qiang Zhang
>Priority: Minor
> Fix For: 1.0.0
>
> Attachments:
> 0001-RANGER-1539-Improve-modify-print-log-display-method-.patch
>
>
> Improve, modify print log display method name chang from
> LOG.info("===> HdfsClient.testConnection()" ); to
> LOG.info("===> HdfsClient.connectionTest()" );
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (RANGER-1542) Exceptions occured when I test connection during create a new service for atlas-plugin
[
https://issues.apache.org/jira/browse/RANGER-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15982643#comment-15982643
]
Colm O hEigeartaigh commented on RANGER-1542:
-
Will it not fall back to the "finally" block (looking at the code for
1.0.0-SNAPSHOT) + use the plain password if decryption fails?
> Exceptions occured when I test connection during create a new service for
> atlas-plugin
> --
>
> Key: RANGER-1542
> URL: https://issues.apache.org/jira/browse/RANGER-1542
> Project: Ranger
> Issue Type: Bug
> Components: plugins
>Reporter: Qiang Zhang
>Assignee: Qiang Zhang
> Labels: patch
> Attachments: test.JPG
>
>
> {code}
> 2017-04-25 07:02:20,358 [timed-executor-pool-0] ERROR
> org.apache.ranger.plugin.util.PasswordUtils (PasswordUtils.java:127) - Unable
> to decrypt password due to error
> javax.crypto.BadPaddingException: Given final block not properly padded
> at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:811)
> at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:676)
> at com.sun.crypto.provider.PBECipherCore.doFinal(PBECipherCore.java:422)
> at
> com.sun.crypto.provider.PBEWithMD5AndDESCipher.engineDoFinal(PBEWithMD5AndDESCipher.java:316)
> at javax.crypto.Cipher.doFinal(Cipher.java:2131)
> at
> org.apache.ranger.plugin.util.PasswordUtils.decryptPassword(PasswordUtils.java:112)
> at
> org.apache.ranger.services.atlas.client.AtlasClient.getStatusResponse(AtlasClient.java:183)
> at
> org.apache.ranger.services.atlas.client.AtlasClient.connectionTestResource(AtlasClient.java:227)
> at
> org.apache.ranger.services.atlas.client.AtlasClient$1$1.run(AtlasClient.java:123)
> at
> org.apache.ranger.services.atlas.client.AtlasClient$1$1.run(AtlasClient.java:114)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:356)
> at
> org.apache.ranger.services.atlas.client.AtlasClient$1.call(AtlasClient.java:114)
> at
> org.apache.ranger.services.atlas.client.AtlasClient$1.call(AtlasClient.java:107)
> at
> org.apache.ranger.services.atlas.client.AtlasClient.timedTask(AtlasClient.java:692)
> at
> org.apache.ranger.services.atlas.client.AtlasClient.getResourceList(AtlasClient.java:161)
> at
> org.apache.ranger.services.atlas.client.AtlasClient.getAtlasResource(AtlasClient.java:673)
> at
> org.apache.ranger.services.atlas.client.AtlasClient.connectionTest(AtlasClient.java:619)
> at
> org.apache.ranger.services.atlas.client.AtlasResourceMgr.validateConfig(AtlasResourceMgr.java:40)
> at
> org.apache.ranger.services.atlas.RangerServiceAtlas.validateConfig(RangerServiceAtlas.java:58)
> at
> org.apache.ranger.biz.ServiceMgr$ValidateCallable.actualCall(ServiceMgr.java:563)
> at
> org.apache.ranger.biz.ServiceMgr$ValidateCallable.actualCall(ServiceMgr.java:550)
> at
> org.apache.ranger.biz.ServiceMgr$TimedCallable.call(ServiceMgr.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> 2017-04-25 07:02:20,358 [timed-executor-pool-0] INFO
> apache.ranger.services.atlas.client.AtlasClient (AtlasClient.java:185) -
> Password decryption failed; trying Atlas connection with received password
> string
> 2017-04-25 07:02:20,359 [timed-executor-pool-0] ERROR
> org.apache.ranger.plugin.util.PasswordUtils (PasswordUtils.java:127) - Unable
> to decrypt password due to error
> javax.crypto.BadPaddingException: Given final block not properly padded
> at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:811)
> at com.sun.crypto.provider.CipherCore.doFinal(CipherCore.java:676)
> at com.sun.crypto.provider.PBECipherCore.doFinal(PBECipherCore.java:422)
> at
> com.sun.crypto.provider.PBEWithMD5AndDESCipher.engineDoFinal(PBEWithMD5AndDESCipher.java:316)
> at javax.crypto.Cipher.doFinal(Cipher.java:2131)
> at
> org.apache.ranger.plugin.util.PasswordUtils.decryptPassword(PasswordUtils.java:112)
> at
> org.apache.ranger.services.atlas.client.AtlasClient.getStatusResponse(AtlasClient.java:192)
> at
> org.apache.ranger.services.
[jira] [Resolved] (RANGER-1478) Refactor RangerPolicyEngineOptions, RangerConfiguration is looked up too many times
[ https://issues.apache.org/jira/browse/RANGER-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved RANGER-1478. - Resolution: Fixed > Refactor RangerPolicyEngineOptions, RangerConfiguration is looked up too many > times > --- > > Key: RANGER-1478 > URL: https://issues.apache.org/jira/browse/RANGER-1478 > Project: Ranger > Issue Type: Improvement > Components: plugins >Affects Versions: 0.7.0 >Reporter: Zsombor Gegesy >Assignee: Zsombor Gegesy >Priority: Minor > Labels: code-cleanup > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1478-Small-refactor-in-RangerPolicyEngineCach.patch > > > RangerPolicyEngineOptions has a lot of public fields, which is written from > various places from the code base, which should be avoided. That object is > configured from RangerConfiguration, but in the middle of the plugin > initialization code, which makes this a bit more complex, than it should be. > Suggestions: > * RangerConfiguration should be treated as an object, not a static facade for > a couple of config values > * RangerPolicyEngineOptions should get his configuration from directly the > RangerConfiguration, in an explicit, encapsulated way. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1501) Audit Flush to HDFS does not actually cause the audit logs to be flushed to HDFS
[ https://issues.apache.org/jira/browse/RANGER-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1501: Fix Version/s: (was: master) 1.0.0 > Audit Flush to HDFS does not actually cause the audit logs to be flushed to > HDFS > - > > Key: RANGER-1501 > URL: https://issues.apache.org/jira/browse/RANGER-1501 > Project: Ranger > Issue Type: Bug > Components: audit >Affects Versions: 0.7.0 >Reporter: Yan >Assignee: Yan > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1501-Audit-Flush-to-HDFS-does-not-actually-ca.patch > > > The reason is that HDFS file stream's flush() call does not really flush the > data all the way to disk, nor even makes the data visible to HDFS users. See > the HDFS semantics of the flush/sync at > https://issues.apache.org/jira/browse/HADOOP-6313. > Consequently the audit logs on HDFS won't be visible/durable from HDFS client > until the log file is closed. This will, among other issues, boost chances of > losing audit logs in case of system failure. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (RANGER-1501) Audit Flush to HDFS does not actually cause the audit logs to be flushed to HDFS
[ https://issues.apache.org/jira/browse/RANGER-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh reassigned RANGER-1501: --- Assignee: Colm O hEigeartaigh (was: Yan) > Audit Flush to HDFS does not actually cause the audit logs to be flushed to > HDFS > - > > Key: RANGER-1501 > URL: https://issues.apache.org/jira/browse/RANGER-1501 > Project: Ranger > Issue Type: Bug > Components: audit >Affects Versions: 0.7.0 >Reporter: Yan > Assignee: Colm O hEigeartaigh > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1501-Audit-Flush-to-HDFS-does-not-actually-ca.patch > > > The reason is that HDFS file stream's flush() call does not really flush the > data all the way to disk, nor even makes the data visible to HDFS users. See > the HDFS semantics of the flush/sync at > https://issues.apache.org/jira/browse/HADOOP-6313. > Consequently the audit logs on HDFS won't be visible/durable from HDFS client > until the log file is closed. This will, among other issues, boost chances of > losing audit logs in case of system failure. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1501) Audit Flush to HDFS does not actually cause the audit logs to be flushed to HDFS
[ https://issues.apache.org/jira/browse/RANGER-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15983057#comment-15983057 ] Colm O hEigeartaigh commented on RANGER-1501: - Hi [~rmani], [~yzhou2001], Even with this patch applied, I can't see audit events in the HDFS audit file without shutting down HDFS + starting it up again. The "finally" section in "logJSON" just flushes the PrintWriter, shouldn't it be calling flush() as well to flush the ostream? > Audit Flush to HDFS does not actually cause the audit logs to be flushed to > HDFS > - > > Key: RANGER-1501 > URL: https://issues.apache.org/jira/browse/RANGER-1501 > Project: Ranger > Issue Type: Bug > Components: audit >Affects Versions: 0.7.0 > Reporter: Yan >Assignee: Colm O hEigeartaigh > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1501-Audit-Flush-to-HDFS-does-not-actually-ca.patch > > > The reason is that HDFS file stream's flush() call does not really flush the > data all the way to disk, nor even makes the data visible to HDFS users. See > the HDFS semantics of the flush/sync at > https://issues.apache.org/jira/browse/HADOOP-6313. > Consequently the audit logs on HDFS won't be visible/durable from HDFS client > until the log file is closed. This will, among other issues, boost chances of > losing audit logs in case of system failure. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (RANGER-1501) Audit Flush to HDFS does not actually cause the audit logs to be flushed to HDFS
[ https://issues.apache.org/jira/browse/RANGER-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh reassigned RANGER-1501: --- Assignee: Yan (was: Colm O hEigeartaigh) > Audit Flush to HDFS does not actually cause the audit logs to be flushed to > HDFS > - > > Key: RANGER-1501 > URL: https://issues.apache.org/jira/browse/RANGER-1501 > Project: Ranger > Issue Type: Bug > Components: audit >Affects Versions: 0.7.0 >Reporter: Yan >Assignee: Yan > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1501-Audit-Flush-to-HDFS-does-not-actually-ca.patch > > > The reason is that HDFS file stream's flush() call does not really flush the > data all the way to disk, nor even makes the data visible to HDFS users. See > the HDFS semantics of the flush/sync at > https://issues.apache.org/jira/browse/HADOOP-6313. > Consequently the audit logs on HDFS won't be visible/durable from HDFS client > until the log file is closed. This will, among other issues, boost chances of > losing audit logs in case of system failure. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1537) when use mysql5.7 ,ranger-admin setup error
[
https://issues.apache.org/jira/browse/RANGER-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15984888#comment-15984888
]
Colm O hEigeartaigh commented on RANGER-1537:
-
This bug has already been fixed:
https://issues.apache.org/jira/browse/RANGER-1018
> when use mysql5.7 ,ranger-admin setup error
> ---
>
> Key: RANGER-1537
> URL: https://issues.apache.org/jira/browse/RANGER-1537
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Affects Versions: 0.5.3
>Reporter: zhangxiaolu
> Attachments: RANGER-1537.patch
>
>
> If user use mysql which version is 5.7, and execute ranger-admin's setup.sh,
> the error like this:
> /usr/jdk64/jdk1.7.0_67/bin/java -cp
> /usr/share/java/mysql-connector-java.jar:/usr/lib/ranger-admin/jisql/lib/*
> org.apache.util.sql.Jisql -driver mysqlconj -cstring
> jdbc:mysql://docker1.cmss.com/ranger -u 'rangerdba' -p '' -noheader
> -trim -c \; -input
> /usr/lib/ranger/ranger-admin/db/mysql/create_dbversion_catalog.sql
> Error executing: create table if not exists x_db_version_h ( id
> bigint not null auto_increment primary key,
> version varchar(64) not null, inst_at timestamp
> not null default current_timestamp, inst_by varchar(256)
> not null, updated_at timestamp not null, updated_by
> varchar(256) not null, active ENUM('Y', 'N') default 'Y' ) ;
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Invalid default
> value for 'updated_at'
> SQLException : SQL state: 42000
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Invalid default
> value for 'updated_at' ErrorCode: 1067
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (RANGER-1501) Audit Flush to HDFS does not actually cause the audit logs to be flushed to HDFS
[ https://issues.apache.org/jira/browse/RANGER-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15985107#comment-15985107 ] Colm O hEigeartaigh commented on RANGER-1501: - Great thanks for the feedback guys. > Audit Flush to HDFS does not actually cause the audit logs to be flushed to > HDFS > - > > Key: RANGER-1501 > URL: https://issues.apache.org/jira/browse/RANGER-1501 > Project: Ranger > Issue Type: Bug > Components: audit >Affects Versions: 0.7.0 >Reporter: Yan >Assignee: Yan > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1501-Audit-Flush-to-HDFS-does-not-actually-ca.patch > > > The reason is that HDFS file stream's flush() call does not really flush the > data all the way to disk, nor even makes the data visible to HDFS users. See > the HDFS semantics of the flush/sync at > https://issues.apache.org/jira/browse/HADOOP-6313. > Consequently the audit logs on HDFS won't be visible/durable from HDFS client > until the log file is closed. This will, among other issues, boost chances of > losing audit logs in case of system failure. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1535) Add tag attributes to audit log record
[ https://issues.apache.org/jira/browse/RANGER-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15986193#comment-15986193 ] Colm O hEigeartaigh commented on RANGER-1535: - Please close + mark as submitted the review requests when you resolve the JIRA as well. Colm. > Add tag attributes to audit log record > -- > > Key: RANGER-1535 > URL: https://issues.apache.org/jira/browse/RANGER-1535 > Project: Ranger > Issue Type: Bug > Components: Ranger >Affects Versions: 1.0.0 >Reporter: Abhay Kulkarni >Assignee: Abhay Kulkarni > Fix For: 1.0.0 > > > Currently, in the access audit log record, the tags column is populated when > the accessed resource has any tags associated with it. However, if a tag has > any attributes, their values are not shown in the audit log record. As > authorization decision may be based on the attribute-value(s) as well as > tag-type (such as in the case of expiry_date attribute’s value for EXPIRES_ON > tag-type), they too need to be populated and displayed on audit log record. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1436) Turn Ranger deny policy & except condition blocks ON by default
[ https://issues.apache.org/jira/browse/RANGER-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15986194#comment-15986194 ] Colm O hEigeartaigh commented on RANGER-1436: - Please close + mark as submitted the review requests when you resolve the JIRA as well. Colm. > Turn Ranger deny policy & except condition blocks ON by default > --- > > Key: RANGER-1436 > URL: https://issues.apache.org/jira/browse/RANGER-1436 > Project: Ranger > Issue Type: Improvement > Components: Ranger >Affects Versions: 0.7.0 >Reporter: Srikanth Venkat >Assignee: Abhay Kulkarni > Fix For: 1.0.0 > > > Currently Ranger admins have to do a service def update to turn on Deny > Conditions block and Deny/Allow Except conditions in their Ranger install for > resource based policies. But these are enabled by default for tag based > policies. It would be useful to have consistency and turn this feature > consistently ON by default for both resource and tag based policies. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1531) Good coding practice while parsing XML documents in Ranger
[ https://issues.apache.org/jira/browse/RANGER-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15986209#comment-15986209 ] Colm O hEigeartaigh commented on RANGER-1531: - Please mark the review requests as "resolved" as well when you resolve the JIRA. Colm. > Good coding practice while parsing XML documents in Ranger > -- > > Key: RANGER-1531 > URL: https://issues.apache.org/jira/browse/RANGER-1531 > Project: Ranger > Issue Type: Bug > Components: Ranger, usersync >Affects Versions: 0.7.0 >Reporter: Sailaja Polavarapu >Assignee: Sailaja Polavarapu > Fix For: 1.0.0, 0.7.1 > > Attachments: > 0001-RANGER-1531-added-code-to-not-allow-external-entitie (1).patch, > 0001-RANGER-1531-added-code-to-not-allow-external-entitie.patch, > 0001-RANGER-1531-Good-coding-practice-while-parsing-XML-d.patch > > > Implement good coding practices while parsing XML documents in Ranger -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (RANGER-1549) Add COMPONENT_INSTALL_DIR_NAME to the Storm install.properties
Colm O hEigeartaigh created RANGER-1549: --- Summary: Add COMPONENT_INSTALL_DIR_NAME to the Storm install.properties Key: RANGER-1549 URL: https://issues.apache.org/jira/browse/RANGER-1549 Project: Ranger Issue Type: Improvement Components: plugins Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 1.0.0 Add COMPONENT_INSTALL_DIR_NAME to the Storm install.properties as per the other plugins. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1549) Add COMPONENT_INSTALL_DIR_NAME to the Storm install.properties
[ https://issues.apache.org/jira/browse/RANGER-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1549: Attachment: 0001-RANGER-1549-Add-COMPONENT_INSTALL_DIR_NAME-to-the-St.patch > Add COMPONENT_INSTALL_DIR_NAME to the Storm install.properties > -- > > Key: RANGER-1549 > URL: https://issues.apache.org/jira/browse/RANGER-1549 > Project: Ranger > Issue Type: Improvement > Components: plugins > Reporter: Colm O hEigeartaigh > Assignee: Colm O hEigeartaigh > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1549-Add-COMPONENT_INSTALL_DIR_NAME-to-the-St.patch > > > Add COMPONENT_INSTALL_DIR_NAME to the Storm install.properties as per the > other plugins. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1431) Do some code improvement in Java method AuthSessionService.mapEntityToViewBean
[
https://issues.apache.org/jira/browse/RANGER-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh updated RANGER-1431:
Fix Version/s: 0.7.1
> Do some code improvement in Java method AuthSessionService.mapEntityToViewBean
> --
>
> Key: RANGER-1431
> URL: https://issues.apache.org/jira/browse/RANGER-1431
> Project: Ranger
> Issue Type: Bug
> Components: admin
>Affects Versions: master
>Reporter: Qiang Zhang
>Assignee: Qiang Zhang
>Priority: Minor
> Labels: patch
> Fix For: 1.0.0, 0.7.1
>
> Attachments:
> 0001-RANGER-1431-Do-some-code-improvement-in-Java-method-.patch
>
> Original Estimate: 12h
> Remaining Estimate: 12h
>
> In method mapEntityToViewBean of class
> \security-admin\src\main\java\org\apache\ranger\service\AuthSessionService.java,
> there is some code can be improved:
> 1.The following code is repated twice, remove one of them.
> {code}
> viewObj.setLastName(gjUser.getLastName());
> {code}
> 2.Check null before using gjUser.
> {code}
> XXPortalUser gjUser = daoMgr.getXXPortalUser().getById(resource.getUserId());
> {code}
> 3.Family name should be last name instead of email address.
> {code}
> viewObj.setFamilyScreenName(gjUser.getEmailAddress());
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (RANGER-1544) Misaligned input boxes and cleanup on Reports Search
[ https://issues.apache.org/jira/browse/RANGER-1544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1544: Fix Version/s: 1.0.0 > Misaligned input boxes and cleanup on Reports Search > > > Key: RANGER-1544 > URL: https://issues.apache.org/jira/browse/RANGER-1544 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 0.7.1 >Reporter: Anna Shaverdian >Assignee: Anna Shaverdian >Priority: Trivial > Labels: newbie, patch > Fix For: 1.0.0 > > Attachments: 0001-RANGER-1544-Misaligned-input-boxes.patch, Screen > Shot 2017-04-25 at 8.58.31 PM.png > > > On the Ranger Admin > User Access Report page, the input boxes for Policy > Type and Resource will overlap the other text boxes when resizing the window. > Also UserAccessLayout_tmpl.html has some typos (ie searchInfoUserAccss) and > needs to reformat the indentation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1544) Misaligned input boxes and cleanup on Reports Search
[ https://issues.apache.org/jira/browse/RANGER-1544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1544: Fix Version/s: (was: 0.7.1) > Misaligned input boxes and cleanup on Reports Search > > > Key: RANGER-1544 > URL: https://issues.apache.org/jira/browse/RANGER-1544 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 0.7.1 >Reporter: Anna Shaverdian >Assignee: Anna Shaverdian >Priority: Trivial > Labels: newbie, patch > Fix For: 1.0.0 > > Attachments: 0001-RANGER-1544-Misaligned-input-boxes.patch, Screen > Shot 2017-04-25 at 8.58.31 PM.png > > > On the Ranger Admin > User Access Report page, the input boxes for Policy > Type and Resource will overlap the other text boxes when resizing the window. > Also UserAccessLayout_tmpl.html has some typos (ie searchInfoUserAccss) and > needs to reformat the indentation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1544) Misaligned input boxes and cleanup on Reports Search
[ https://issues.apache.org/jira/browse/RANGER-1544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15998436#comment-15998436 ] Colm O hEigeartaigh commented on RANGER-1544: - Maybe I'm missing something, but even with the patch applied, I still see the same behaviour when I increase the font size on that window? > Misaligned input boxes and cleanup on Reports Search > > > Key: RANGER-1544 > URL: https://issues.apache.org/jira/browse/RANGER-1544 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 0.7.1 >Reporter: Anna Shaverdian >Assignee: Anna Shaverdian >Priority: Trivial > Labels: newbie, patch > Fix For: 1.0.0 > > Attachments: 0001-RANGER-1544-Misaligned-input-boxes.patch, Screen > Shot 2017-04-25 at 8.58.31 PM.png > > > On the Ranger Admin > User Access Report page, the input boxes for Policy > Type and Resource will overlap the other text boxes when resizing the window. > Also UserAccessLayout_tmpl.html has some typos (ie searchInfoUserAccss) and > needs to reformat the indentation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1563) Ranger build needs gcc... docs/validation
[ https://issues.apache.org/jira/browse/RANGER-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000575#comment-16000575 ] Colm O hEigeartaigh commented on RANGER-1563: - Could you submit a patch for this Nigel (to update the docs?) The docs in question are in: docs/src/site/xdoc/quick_start_guide.xml in the source. > Ranger build needs gcc... docs/validation > - > > Key: RANGER-1563 > URL: https://issues.apache.org/jira/browse/RANGER-1563 > Project: Ranger > Issue Type: Bug > Components: documentation >Reporter: Nigel Jones > > When building ranger on a new Linux system I had a build failure, caused by > [INFO] Executed tasks > [INFO] > [INFO] --- native-maven-plugin:1.0-alpha-8:compile (default-compile) @ > credValidator --- > [INFO] /bin/sh -c cd /home/cloudusr/src/ranger/unixauthnative && gcc > -I/home/cloudusr/src/ranger/unixauthnative/src/main/c -o > /home/cloudusr/src/ranger/unixauthnative/target/objs/credValidator.o -c > /home/cloudusr/src/ranger/unixauthnative/src/main/c/credValidator.c > /bin/sh: 1: gcc: not found > Clearly gcc is needed. Along with java, maven. Listing these prereqs would be > useful > Suggest we update the docs at http://ranger.apache.org/quick_start_guide.html > to make this prereq clear. > Ideally update maven to do a check early on -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1544) Misaligned input boxes and cleanup on Reports Search
[ https://issues.apache.org/jira/browse/RANGER-1544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000583#comment-16000583 ] Colm O hEigeartaigh commented on RANGER-1544: - Yes, the cache was the problem, I can confirm it works fine now. > Misaligned input boxes and cleanup on Reports Search > > > Key: RANGER-1544 > URL: https://issues.apache.org/jira/browse/RANGER-1544 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: 0.7.1 >Reporter: Anna Shaverdian >Assignee: Anna Shaverdian >Priority: Trivial > Labels: newbie, patch > Fix For: 1.0.0 > > Attachments: 0001-RANGER-1544-Misaligned-input-boxes.patch, Screen > Shot 2017-04-25 at 8.58.31 PM.png, Screen Shot 2017-05-05 at 10.13.05 AM.png > > > On the Ranger Admin > User Access Report page, the input boxes for Policy > Type and Resource will overlap the other text boxes when resizing the window. > Also UserAccessLayout_tmpl.html has some typos (ie searchInfoUserAccss) and > needs to reformat the indentation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1563) Ranger build needs gcc... docs/validation
[ https://issues.apache.org/jira/browse/RANGER-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000588#comment-16000588 ] Colm O hEigeartaigh commented on RANGER-1563: - No it appears not, please try asking again. > Ranger build needs gcc... docs/validation > - > > Key: RANGER-1563 > URL: https://issues.apache.org/jira/browse/RANGER-1563 > Project: Ranger > Issue Type: Bug > Components: documentation >Reporter: Nigel Jones > > When building ranger on a new Linux system I had a build failure, caused by > [INFO] Executed tasks > [INFO] > [INFO] --- native-maven-plugin:1.0-alpha-8:compile (default-compile) @ > credValidator --- > [INFO] /bin/sh -c cd /home/cloudusr/src/ranger/unixauthnative && gcc > -I/home/cloudusr/src/ranger/unixauthnative/src/main/c -o > /home/cloudusr/src/ranger/unixauthnative/target/objs/credValidator.o -c > /home/cloudusr/src/ranger/unixauthnative/src/main/c/credValidator.c > /bin/sh: 1: gcc: not found > Clearly gcc is needed. Along with java, maven. Listing these prereqs would be > useful > Suggest we update the docs at http://ranger.apache.org/quick_start_guide.html > to make this prereq clear. > Ideally update maven to do a check early on -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1558) UI Hints Popover Hides after mouse moves away from small Info I icon
[ https://issues.apache.org/jira/browse/RANGER-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1558: Fix Version/s: (was: 0.7.1) > UI Hints Popover Hides after mouse moves away from small Info I icon > > > Key: RANGER-1558 > URL: https://issues.apache.org/jira/browse/RANGER-1558 > Project: Ranger > Issue Type: Bug > Components: admin >Affects Versions: master, 0.7.1 >Reporter: Anna Shaverdian >Assignee: Anna Shaverdian >Priority: Trivial > Fix For: master > > Attachments: > 0001-RANGER-1558-Let-UI-Hints-Popover-stay-open-while-mou.patch, Screen Shot > 2017-05-04 at 2.17.38 PM 1.png > > > On the Ranger Admin UI, there are new helpful UI hints in the form of an "I" > information icon. These are information about different filter attributes. > The information that opens when the user hovers over the "I" is long list of > 10+ items. > Right now the Information Popover items goes away as soon as you move from > the Information I box. But since it's a long list, it would be nice if the > user can hover the mouse along the popover, copy items, and look at the > helpful hints longer. > This JIRA is intended to make the popover hoverable. When the mouse moves > away from the hover box, then the popover should hide. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1529) Remove tez dependency from Hive/HDFS plugins
[ https://issues.apache.org/jira/browse/RANGER-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1529: Attachment: 0001-RANGER-1529-Remove-tez-dependency-from-Hive-HDFS-plu.patch > Remove tez dependency from Hive/HDFS plugins > > > Key: RANGER-1529 > URL: https://issues.apache.org/jira/browse/RANGER-1529 > Project: Ranger > Issue Type: Improvement > Components: plugins > Reporter: Colm O hEigeartaigh > Assignee: Colm O hEigeartaigh > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1529-Remove-tez-dependency-from-Hive-HDFS-plu.patch > > > There are some tez dependencies listed as "optional" for both the Hive + HDFS > plugins. They should be removed as they are not required and are not included > in the distribution, and are dragging some old dependencies into the build > classpath for those modules. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1529) Remove tez dependency from Hive/HDFS plugins
[ https://issues.apache.org/jira/browse/RANGER-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1529: Attachment: (was: 0001-RANGER-1529-Remove-tez-dependency-from-Hive-HDFS-plu.patch) > Remove tez dependency from Hive/HDFS plugins > > > Key: RANGER-1529 > URL: https://issues.apache.org/jira/browse/RANGER-1529 > Project: Ranger > Issue Type: Improvement > Components: plugins > Reporter: Colm O hEigeartaigh > Assignee: Colm O hEigeartaigh > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1529-Remove-tez-dependency-from-Hive-HDFS-plu.patch > > > There are some tez dependencies listed as "optional" for both the Hive + HDFS > plugins. They should be removed as they are not required and are not included > in the distribution, and are dragging some old dependencies into the build > classpath for those modules. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1498) Remove unnecessary mockito stubs
[ https://issues.apache.org/jira/browse/RANGER-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1498: Attachment: (was: 0001-RANGER-1498-Remove-unnecessary-mockito-stubs.patch) > Remove unnecessary mockito stubs > > > Key: RANGER-1498 > URL: https://issues.apache.org/jira/browse/RANGER-1498 > Project: Ranger > Issue Type: Test > Components: admin > Reporter: Colm O hEigeartaigh > Assignee: Colm O hEigeartaigh > Fix For: 1.0.0 > > > This task is to remove the unnecessary mockito stubs in the test code. This > will smooth the path to updating to use Mockito 2, which errors by default on > unused stubs. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1498) Remove unnecessary mockito stubs
[ https://issues.apache.org/jira/browse/RANGER-1498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1498: Attachment: 0001-RANGER-1498-Remove-unnecessary-mockito-stubs.patch > Remove unnecessary mockito stubs > > > Key: RANGER-1498 > URL: https://issues.apache.org/jira/browse/RANGER-1498 > Project: Ranger > Issue Type: Test > Components: admin > Reporter: Colm O hEigeartaigh > Assignee: Colm O hEigeartaigh > Fix For: 1.0.0 > > Attachments: 0001-RANGER-1498-Remove-unnecessary-mockito-stubs.patch > > > This task is to remove the unnecessary mockito stubs in the test code. This > will smooth the path to updating to use Mockito 2, which errors by default on > unused stubs. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1565) Make SOLR setup config docs consistent with code
[ https://issues.apache.org/jira/browse/RANGER-1565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16003586#comment-16003586 ] Colm O hEigeartaigh commented on RANGER-1565: - Yes it sounds reasonable to me. > Make SOLR setup config docs consistent with code > > > Key: RANGER-1565 > URL: https://issues.apache.org/jira/browse/RANGER-1565 > Project: Ranger > Issue Type: Bug > Components: audit >Reporter: Nigel Jones > > In the Apache ranger setup docs we have a section on Solr configuration at > https://cwiki.apache.org/confluence/display/RANGER/Install+and+Configure+Solr+for+Ranger+Audits+-+Apache+Ranger+0.5 > In this doc it refers to setting JAVA_HOME in the install.properties file > (the one in the contrib/ solr setup directory). However when I set this the > ./setup.sh still failed with: > # ./setup.sh > Error: JAVA_HOME environment property not defined, aborting installation. > Looking at the code it appears it does NOT pull out JAVA_HOME from the > properties file at all, but relies on it being specified in the environment > Ideally we would update the script to also source JAVA_HOME from > install.properties, in which case the doc can stay as is. If we don't do this > we need to update the docs accordingly. I would go with the properties file > overriding the local environment, if the variable is set there. > My proposal is to change the script. Happy to work this if it sounds ok... -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (RANGER-1570) Finish cleaning up Mockito stubs
Colm O hEigeartaigh created RANGER-1570: --- Summary: Finish cleaning up Mockito stubs Key: RANGER-1570 URL: https://issues.apache.org/jira/browse/RANGER-1570 Project: Ranger Issue Type: Improvement Components: admin Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 1.0.0 As a continuation of RANGER-1498, continue to cleanup the Mockito stub code to facilitate migrating to Mockito 2. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1570) Finish cleaning up Mockito stubs
[ https://issues.apache.org/jira/browse/RANGER-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1570: Attachment: 0001-RANGER-1570-Finish-cleaning-up-Mockito-stubs.patch > Finish cleaning up Mockito stubs > > > Key: RANGER-1570 > URL: https://issues.apache.org/jira/browse/RANGER-1570 > Project: Ranger > Issue Type: Improvement > Components: admin > Reporter: Colm O hEigeartaigh > Assignee: Colm O hEigeartaigh > Fix For: 1.0.0 > > Attachments: 0001-RANGER-1570-Finish-cleaning-up-Mockito-stubs.patch > > > As a continuation of RANGER-1498, continue to cleanup the Mockito stub code > to facilitate migrating to Mockito 2. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1580) Update Kafka tests to work with 0.10.1.1
[ https://issues.apache.org/jira/browse/RANGER-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1580: Attachment: 0001-RANGER-1580-Update-Kafka-tests-to-work-with-0.10.1.1.patch > Update Kafka tests to work with 0.10.1.1 > > > Key: RANGER-1580 > URL: https://issues.apache.org/jira/browse/RANGER-1580 > Project: Ranger > Issue Type: Test > Components: plugins > Reporter: Colm O hEigeartaigh > Assignee: Colm O hEigeartaigh > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1580-Update-Kafka-tests-to-work-with-0.10.1.1.patch > > > Right now, the Ranger Kafka tests hang with 0.10.1.1, as the authorizer needs > the "describe" policy for the given principal + topic, even when the > principal is not authorized to read the topic. Merging this update will > smooth future migration. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (RANGER-1580) Update Kafka tests to work with 0.10.1.1
Colm O hEigeartaigh created RANGER-1580: --- Summary: Update Kafka tests to work with 0.10.1.1 Key: RANGER-1580 URL: https://issues.apache.org/jira/browse/RANGER-1580 Project: Ranger Issue Type: Test Components: plugins Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 1.0.0 Attachments: 0001-RANGER-1580-Update-Kafka-tests-to-work-with-0.10.1.1.patch Right now, the Ranger Kafka tests hang with 0.10.1.1, as the authorizer needs the "describe" policy for the given principal + topic, even when the principal is not authorized to read the topic. Merging this update will smooth future migration. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1580) Update Kafka tests to work with 0.10.1.1
[ https://issues.apache.org/jira/browse/RANGER-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1580: Attachment: (was: 0001-RANGER-1580-Update-Kafka-tests-to-work-with-0.10.1.1.patch) > Update Kafka tests to work with 0.10.1.1 > > > Key: RANGER-1580 > URL: https://issues.apache.org/jira/browse/RANGER-1580 > Project: Ranger > Issue Type: Test > Components: plugins > Reporter: Colm O hEigeartaigh > Assignee: Colm O hEigeartaigh > Fix For: 1.0.0 > > > Right now, the Ranger Kafka tests hang with 0.10.1.1, as the authorizer needs > the "describe" policy for the given principal + topic, even when the > principal is not authorized to read the topic. Merging this update will > smooth future migration. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1580) Update Kafka tests to work with 0.10.1.1
[ https://issues.apache.org/jira/browse/RANGER-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1580: Attachment: 0001-RANGER-1580-Update-Kafka-tests-to-work-with-0.10.1.1.patch This patch is a better fix. > Update Kafka tests to work with 0.10.1.1 > > > Key: RANGER-1580 > URL: https://issues.apache.org/jira/browse/RANGER-1580 > Project: Ranger > Issue Type: Test > Components: plugins > Reporter: Colm O hEigeartaigh > Assignee: Colm O hEigeartaigh > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1580-Update-Kafka-tests-to-work-with-0.10.1.1.patch > > > Right now, the Ranger Kafka tests hang with 0.10.1.1, as the authorizer needs > the "describe" policy for the given principal + topic, even when the > principal is not authorized to read the topic. Merging this update will > smooth future migration. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1411) Permissions tab pages display are not reasonable
[ https://issues.apache.org/jira/browse/RANGER-1411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1411: Fix Version/s: (was: 0.7.1) > Permissions tab pages display are not reasonable > > > Key: RANGER-1411 > URL: https://issues.apache.org/jira/browse/RANGER-1411 > Project: Ranger > Issue Type: Bug > Components: admin, Ranger >Affects Versions: 0.6.3 >Reporter: Haihui Xu >Assignee: Haihui Xu > Fix For: 1.0.0 > > Attachments: RANGER-1411-1.jpg, RANGER-1411.patch > > > 1.Navigate to Ranger Web UI's Settings Permissions tab, the permissions > table header is Permissions,Groups,Users,Action. But the first column in the > table is modules(Resource Based Policies,Users/Groups,Audits,Reports...). So > the table header should be Modules,Groups,Users,Action. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1584) Allow tagsync to support log directory from Ambari configuration
[ https://issues.apache.org/jira/browse/RANGER-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16013851#comment-16013851 ] Colm O hEigeartaigh commented on RANGER-1584: - Please create a review request as well for this patch. > Allow tagsync to support log directory from Ambari configuration > > > Key: RANGER-1584 > URL: https://issues.apache.org/jira/browse/RANGER-1584 > Project: Ranger > Issue Type: Bug > Components: tagsync >Affects Versions: master, 0.7.1 >Reporter: Yujie Li >Priority: Minor > Attachments: > 0001-RANGER-1584-Allow-tagsync-to-support-log-directory-f.patch > > > Currently Tagsync hardcodes the log directory as /var/log/ranger/tagsync. It > doesn't support customization setting for log location from Ambari side. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (RANGER-1586) There is "cannot resolve symbol 'serviceName'" error in ServiceSolrClient class.
[ https://issues.apache.org/jira/browse/RANGER-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved RANGER-1586. - Resolution: Fixed > There is "cannot resolve symbol 'serviceName'" error in ServiceSolrClient > class. > > > Key: RANGER-1586 > URL: https://issues.apache.org/jira/browse/RANGER-1586 > Project: Ranger > Issue Type: Bug > Components: plugins >Affects Versions: 1.0.0 >Reporter: peng.jianhua >Assignee: peng.jianhua >Priority: Trivial > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1586-There-is-cannot-resolve-symbol-serviceNa.patch > > > There is "cannot resolve symbol 'serviceName'" error in ServiceSolrClient > class. > I deleted it to resolve the issue and keep the code consistent. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (RANGER-1587) Cleanup Ranger KMS service dependencies
Colm O hEigeartaigh created RANGER-1587: --- Summary: Cleanup Ranger KMS service dependencies Key: RANGER-1587 URL: https://issues.apache.org/jira/browse/RANGER-1587 Project: Ranger Issue Type: Improvement Components: kms Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 1.0.0 The Ranger KMS service pom is a bit of a mess, with a large number of dependencies listed - most of which can be imported via Hadoop. I've made the following changes (and verified that the jars in the KMS distribution are the exact same as before): Removed: commons-digester 1.8 (comes from commons-configuration 1.6) commons-configuration 1.6 (comes from Hadoop 2.7.1) javax.activation 1.1 (comes from jaxb-api 2.2.2) jaxb-api 2.2.2 (comes from jaxb-impl 2.2.3-1) eclipselink + javax.persistence (comes from ranger-plugins-audit) commons-beanutils 1.7.0 (comes from commons-digester 1.8) commons-beanutils-core 1.8.0 (comes from commons-configuration 1.6) commons-compress 1.4.1 (comes from hadoop 2.7.1) commons-math3 3.1.1 (comes from hadoop 2.7.1) commons-net 3.1 (comes from hadoop 2.7.1) apacheds-i18n 2.0.0-M15 (comes from apacheds-kerberos-codec 2.0.0-M15) api-asn1-api 1.0.0-M20 (comes from apacheds-kerberos-codec 2.0.0-M15) api-util 1.0.0-M20 (comes from apacheds-kerberos-codec 2.0.0-M15) apacheds-i18n 2.0.0-M15 (comes from apacheds-kerberos-codec 2.0.0-M15) apacheds-kerberos-codec 2.0.0-M15 (comes from hadoop-auth 2.7.1) avro 1.7.4 (comes from hadoop-common 2.7.1) commons-cli 1.2 (comes from hadoop-common 2.7.1) commons-io 2.4 (comes from hadoop-common 2.7.1) commons-codec 1.4 (comes from hadoop-common 2.7.1) gson 2.2.4 (comes from hadoop-common 2.7.1) hadoop-annotations 2.7.1 (comes from hadoop-common 2.7.1) htrace 3.1.0-incubating (comes from hadoop-common 2.7.1) jaxb-impl:jar:2.2.3-1 (comes from jersey-json 1.19.3) jettison 1.1 (comes from jersey-json 1.19.3) jsch 0.1.42 (comes from hadoop-common 2.7.1) paranamer 2.3 (comes from avro 1.7.4) protobuf-java 2.5.0 (comes from hadoop-common 2.7.1) snappy-java 1.0.4.1 (comes from avro 1.7.4) xmlenc 0.52 (comes from hadoop-common 2.7.1) xz 1.0 (comes from commons-compress 1.4.1) noggit 0.6 (comes from solrj 5.5.1) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1587) Cleanup Ranger KMS service dependencies
[ https://issues.apache.org/jira/browse/RANGER-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1587: Attachment: 0001-RANGER-1587-Cleanup-Ranger-KMS-service-dependencies.patch > Cleanup Ranger KMS service dependencies > --- > > Key: RANGER-1587 > URL: https://issues.apache.org/jira/browse/RANGER-1587 > Project: Ranger > Issue Type: Improvement > Components: kms > Reporter: Colm O hEigeartaigh > Assignee: Colm O hEigeartaigh > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1587-Cleanup-Ranger-KMS-service-dependencies.patch > > > The Ranger KMS service pom is a bit of a mess, with a large number of > dependencies listed - most of which can be imported via Hadoop. I've made the > following changes (and verified that the jars in the KMS distribution are the > exact same as before): > Removed: > commons-digester 1.8 (comes from commons-configuration 1.6) > commons-configuration 1.6 (comes from Hadoop 2.7.1) > javax.activation 1.1 (comes from jaxb-api 2.2.2) > jaxb-api 2.2.2 (comes from jaxb-impl 2.2.3-1) > eclipselink + javax.persistence (comes from ranger-plugins-audit) > commons-beanutils 1.7.0 (comes from commons-digester 1.8) > commons-beanutils-core 1.8.0 (comes from commons-configuration 1.6) > commons-compress 1.4.1 (comes from hadoop 2.7.1) > commons-math3 3.1.1 (comes from hadoop 2.7.1) > commons-net 3.1 (comes from hadoop 2.7.1) > apacheds-i18n 2.0.0-M15 (comes from apacheds-kerberos-codec 2.0.0-M15) > api-asn1-api 1.0.0-M20 (comes from apacheds-kerberos-codec 2.0.0-M15) > api-util 1.0.0-M20 (comes from apacheds-kerberos-codec 2.0.0-M15) > apacheds-i18n 2.0.0-M15 (comes from apacheds-kerberos-codec 2.0.0-M15) > apacheds-kerberos-codec 2.0.0-M15 (comes from hadoop-auth 2.7.1) > avro 1.7.4 (comes from hadoop-common 2.7.1) > commons-cli 1.2 (comes from hadoop-common 2.7.1) > commons-io 2.4 (comes from hadoop-common 2.7.1) > commons-codec 1.4 (comes from hadoop-common 2.7.1) > gson 2.2.4 (comes from hadoop-common 2.7.1) > hadoop-annotations 2.7.1 (comes from hadoop-common 2.7.1) > htrace 3.1.0-incubating (comes from hadoop-common 2.7.1) > jaxb-impl:jar:2.2.3-1 (comes from jersey-json 1.19.3) > jettison 1.1 (comes from jersey-json 1.19.3) > jsch 0.1.42 (comes from hadoop-common 2.7.1) > paranamer 2.3 (comes from avro 1.7.4) > protobuf-java 2.5.0 (comes from hadoop-common 2.7.1) > snappy-java 1.0.4.1 (comes from avro 1.7.4) > xmlenc 0.52 (comes from hadoop-common 2.7.1) > xz 1.0 (comes from commons-compress 1.4.1) > noggit 0.6 (comes from solrj 5.5.1) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1584) Allow tagsync to support log directory from Ambari configuration
[ https://issues.apache.org/jira/browse/RANGER-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16015438#comment-16015438 ] Colm O hEigeartaigh commented on RANGER-1584: - I don't have the permissions to assign you...try asking again on the mailing list. > Allow tagsync to support log directory from Ambari configuration > > > Key: RANGER-1584 > URL: https://issues.apache.org/jira/browse/RANGER-1584 > Project: Ranger > Issue Type: Bug > Components: tagsync >Affects Versions: master, 0.7.1 >Reporter: Yujie Li >Priority: Minor > Attachments: > 0001-RANGER-1584-Allow-tagsync-to-support-log-directory-f.patch > > > Currently Tagsync hardcodes the log directory as /var/log/ranger/tagsync. It > doesn't support customization setting for log location from Ambari side. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (RANGER-1588) Simplify Storm Test config
Colm O hEigeartaigh created RANGER-1588: --- Summary: Simplify Storm Test config Key: RANGER-1588 URL: https://issues.apache.org/jira/browse/RANGER-1588 Project: Ranger Issue Type: Test Components: plugins Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 1.0.0 The Storm test config has way too many unneeded properties defined. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1588) Simplify Storm Test config
[ https://issues.apache.org/jira/browse/RANGER-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1588: Attachment: 0001-RANGER-1588-Simplify-Storm-Test-config.patch > Simplify Storm Test config > -- > > Key: RANGER-1588 > URL: https://issues.apache.org/jira/browse/RANGER-1588 > Project: Ranger > Issue Type: Test > Components: plugins > Reporter: Colm O hEigeartaigh > Assignee: Colm O hEigeartaigh > Fix For: 1.0.0 > > Attachments: 0001-RANGER-1588-Simplify-Storm-Test-config.patch > > > The Storm test config has way too many unneeded properties defined. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1589) Ranger
[
https://issues.apache.org/jira/browse/RANGER-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16015843#comment-16015843
]
Colm O hEigeartaigh commented on RANGER-1589:
-
Could you submit a patch for this?
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=55151244
> Ranger
> ---
>
> Key: RANGER-1589
> URL: https://issues.apache.org/jira/browse/RANGER-1589
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 0.7.0
> Environment: Mac OS Sierra, python3 by default.
>Reporter: Denes Bodo
>Priority: Minor
> Labels: build, easyfix, newbie
>
> When python3 is the default python version on the computer Ranger build fails.
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-antrun-plugin:1.7:run
> (generate-version-annotation) on project ranger-util: An Ant BuildException
> has occured: exec returned: 1
> [ERROR] around Ant part .. @
> 4:48 in
> /Users/dbodo/work/repos/ranger/ranger-util/target/antrun/build-main.xml
> {noformat}
> I recommend to use "python2" instead of "python".
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (RANGER-1589) Ranger build fails when python3 is the default
[
https://issues.apache.org/jira/browse/RANGER-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh updated RANGER-1589:
Fix Version/s: 0.7.1
1.0.0
> Ranger build fails when python3 is the default
> --
>
> Key: RANGER-1589
> URL: https://issues.apache.org/jira/browse/RANGER-1589
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 0.7.0, master
> Environment: Mac OS Sierra, python3 by default.
>Reporter: Denes Bodo
>Priority: Minor
> Labels: build, easyfix, newbie
> Fix For: 1.0.0
>
> Attachments:
> 0001-RANGER-1589-fix-build-ranger-utils-python-version-wa.patch
>
>
> When python3 is the default python version on the computer Ranger build fails.
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-antrun-plugin:1.7:run
> (generate-version-annotation) on project ranger-util: An Ant BuildException
> has occured: exec returned: 1
> [ERROR] around Ant part .. @
> 4:48 in
> /Users/dbodo/work/repos/ranger/ranger-util/target/antrun/build-main.xml
> {noformat}
> I recommend to use "python2" instead of "python".
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (RANGER-1589) Ranger build fails when python3 is the default
[
https://issues.apache.org/jira/browse/RANGER-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh updated RANGER-1589:
Fix Version/s: (was: 0.7.1)
> Ranger build fails when python3 is the default
> --
>
> Key: RANGER-1589
> URL: https://issues.apache.org/jira/browse/RANGER-1589
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 0.7.0, master
> Environment: Mac OS Sierra, python3 by default.
>Reporter: Denes Bodo
>Priority: Minor
> Labels: build, easyfix, newbie
> Fix For: 1.0.0
>
> Attachments:
> 0001-RANGER-1589-fix-build-ranger-utils-python-version-wa.patch
>
>
> When python3 is the default python version on the computer Ranger build fails.
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-antrun-plugin:1.7:run
> (generate-version-annotation) on project ranger-util: An Ant BuildException
> has occured: exec returned: 1
> [ERROR] around Ant part .. @
> 4:48 in
> /Users/dbodo/work/repos/ranger/ranger-util/target/antrun/build-main.xml
> {noformat}
> I recommend to use "python2" instead of "python".
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (RANGER-1523) Add AtlasResourceMapper implementation for Apache Storm
[ https://issues.apache.org/jira/browse/RANGER-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16016009#comment-16016009 ] Colm O hEigeartaigh commented on RANGER-1523: - *bump* > Add AtlasResourceMapper implementation for Apache Storm > --- > > Key: RANGER-1523 > URL: https://issues.apache.org/jira/browse/RANGER-1523 > Project: Ranger > Issue Type: New Feature > Components: tagsync > Reporter: Colm O hEigeartaigh > Assignee: Colm O hEigeartaigh > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1523-Add-AtlasResourceMapper-implementation-f.patch > > > This task is to add a AtlasResourceMapper implementation for Apache Storm. > This will allow us to sync tags associated with Storm topologies into Ranger > via the REST aproach + to create tag based authorization policies as a result. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1590) Modify code for the error logs in ranger\knox-agent\src\main\java\org\apache\ranger\services\knox\client\KnoxClient.java
[
https://issues.apache.org/jira/browse/RANGER-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh updated RANGER-1590:
Fix Version/s: 1.0.0
> Modify code for the error logs in
> ranger\knox-agent\src\main\java\org\apache\ranger\services\knox\client\KnoxClient.java
>
>
> Key: RANGER-1590
> URL: https://issues.apache.org/jira/browse/RANGER-1590
> Project: Ranger
> Issue Type: Improvement
> Components: plugins
>Affects Versions: master
>Reporter: peng.jianhua
>Assignee: peng.jianhua
> Fix For: 1.0.0
>
>
> modify code for the error logs in
> ranger\knox-agent\src\main\java\org\apache\ranger\services\knox\client\KnoxClient.java
> chang from LOG.debug("Knox service look up response JSON string: " +
> jsonString);to LOG.debug("Knox service lookup response JSON string:
> " + jsonString);
> Reason :keep the log consistent:
> response = webResource.accept(EXPECTED_MIME_TYPE)
>
> .get(ClientResponse.class);
> LOG.debug("Knox service lookup
> response: " + response);
> if (response != null) {
> if (response.getStatus() ==
> 200) {
> String jsonString =
> response.getEntity(String.class);
> LOG.debug("Knox service
> lookup response JSON string: " + jsonString);
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (RANGER-1590) Modify code for the error logs in ranger\knox-agent\src\main\java\org\apache\ranger\services\knox\client\KnoxClient.java
[
https://issues.apache.org/jira/browse/RANGER-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh resolved RANGER-1590.
-
Resolution: Fixed
> Modify code for the error logs in
> ranger\knox-agent\src\main\java\org\apache\ranger\services\knox\client\KnoxClient.java
>
>
> Key: RANGER-1590
> URL: https://issues.apache.org/jira/browse/RANGER-1590
> Project: Ranger
> Issue Type: Improvement
> Components: plugins
>Affects Versions: master
>Reporter: peng.jianhua
>Assignee: peng.jianhua
> Fix For: 1.0.0
>
>
> modify code for the error logs in
> ranger\knox-agent\src\main\java\org\apache\ranger\services\knox\client\KnoxClient.java
> chang from LOG.debug("Knox service look up response JSON string: " +
> jsonString);to LOG.debug("Knox service lookup response JSON string:
> " + jsonString);
> Reason :keep the log consistent:
> response = webResource.accept(EXPECTED_MIME_TYPE)
>
> .get(ClientResponse.class);
> LOG.debug("Knox service lookup
> response: " + response);
> if (response != null) {
> if (response.getStatus() ==
> 200) {
> String jsonString =
> response.getEntity(String.class);
> LOG.debug("Knox service
> lookup response JSON string: " + jsonString);
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Resolved] (RANGER-1589) Ranger build fails when python3 is the default
[
https://issues.apache.org/jira/browse/RANGER-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh resolved RANGER-1589.
-
Resolution: Fixed
> Ranger build fails when python3 is the default
> --
>
> Key: RANGER-1589
> URL: https://issues.apache.org/jira/browse/RANGER-1589
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
>Affects Versions: 0.7.0, master
> Environment: Mac OS Sierra, python3 by default.
>Reporter: Denes Bodo
>Priority: Minor
> Labels: build, easyfix, newbie
> Fix For: 1.0.0
>
> Attachments:
> 0001-RANGER-1589-fix-build-ranger-utils-python-version-wa.patch
>
>
> When python3 is the default python version on the computer Ranger build fails.
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-antrun-plugin:1.7:run
> (generate-version-annotation) on project ranger-util: An Ant BuildException
> has occured: exec returned: 1
> [ERROR] around Ant part .. @
> 4:48 in
> /Users/dbodo/work/repos/ranger/ranger-util/target/antrun/build-main.xml
> {noformat}
> I recommend to use "python2" instead of "python".
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (RANGER-1593) Avoid Classloading default AtlasResourceMappers
Colm O hEigeartaigh created RANGER-1593: --- Summary: Avoid Classloading default AtlasResourceMappers Key: RANGER-1593 URL: https://issues.apache.org/jira/browse/RANGER-1593 Project: Ranger Issue Type: Improvement Components: tagsync Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Priority: Minor Fix For: 1.0.0 In AtlasResourceMapperUtil we classload both the default AtlasResourceMappers and then the custom ones. This is unnecessary - we should just instantiate the default ones and classload the custom ones. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1593) Avoid Classloading default AtlasResourceMappers
[ https://issues.apache.org/jira/browse/RANGER-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1593: Attachment: 0001-RANGER-1593-Avoid-Classloading-default-AtlasResource.patch > Avoid Classloading default AtlasResourceMappers > --- > > Key: RANGER-1593 > URL: https://issues.apache.org/jira/browse/RANGER-1593 > Project: Ranger > Issue Type: Improvement > Components: tagsync > Reporter: Colm O hEigeartaigh > Assignee: Colm O hEigeartaigh >Priority: Minor > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1593-Avoid-Classloading-default-AtlasResource.patch > > > In AtlasResourceMapperUtil we classload both the default AtlasResourceMappers > and then the custom ones. This is unnecessary - we should just instantiate > the default ones and classload the custom ones. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (RANGER-1594) Fix HBase tests to work with HBase 1.2.x
Colm O hEigeartaigh created RANGER-1594: --- Summary: Fix HBase tests to work with HBase 1.2.x Key: RANGER-1594 URL: https://issues.apache.org/jira/browse/RANGER-1594 Project: Ranger Issue Type: Test Components: plugins Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 1.0.0 Currently, the HBase tests in Ranger fail on an upgrade to 1.2.x. This task is to fix the tests so that when we upgrade everything works. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1594) Fix HBase tests to work with HBase 1.2.x
[ https://issues.apache.org/jira/browse/RANGER-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1594: Attachment: 0001-RANGER-1594-Fix-HBase-tests-to-work-with-HBase-1.2.x.patch > Fix HBase tests to work with HBase 1.2.x > > > Key: RANGER-1594 > URL: https://issues.apache.org/jira/browse/RANGER-1594 > Project: Ranger > Issue Type: Test > Components: plugins > Reporter: Colm O hEigeartaigh > Assignee: Colm O hEigeartaigh > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1594-Fix-HBase-tests-to-work-with-HBase-1.2.x.patch > > > Currently, the HBase tests in Ranger fail on an upgrade to 1.2.x. This task > is to fix the tests so that when we upgrade everything works. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1593) Avoid Classloading default AtlasResourceMappers
[ https://issues.apache.org/jira/browse/RANGER-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1593: Attachment: 0001-RANGER-1593-Avoid-Classloading-default-AtlasResource.patch Fixing whitespace issues. > Avoid Classloading default AtlasResourceMappers > --- > > Key: RANGER-1593 > URL: https://issues.apache.org/jira/browse/RANGER-1593 > Project: Ranger > Issue Type: Improvement > Components: tagsync > Reporter: Colm O hEigeartaigh > Assignee: Colm O hEigeartaigh >Priority: Minor > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1593-Avoid-Classloading-default-AtlasResource.patch > > > In AtlasResourceMapperUtil we classload both the default AtlasResourceMappers > and then the custom ones. This is unnecessary - we should just instantiate > the default ones and classload the custom ones. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1593) Avoid Classloading default AtlasResourceMappers
[ https://issues.apache.org/jira/browse/RANGER-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1593: Attachment: (was: 0001-RANGER-1593-Avoid-Classloading-default-AtlasResource.patch) > Avoid Classloading default AtlasResourceMappers > --- > > Key: RANGER-1593 > URL: https://issues.apache.org/jira/browse/RANGER-1593 > Project: Ranger > Issue Type: Improvement > Components: tagsync > Reporter: Colm O hEigeartaigh > Assignee: Colm O hEigeartaigh >Priority: Minor > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1593-Avoid-Classloading-default-AtlasResource.patch > > > In AtlasResourceMapperUtil we classload both the default AtlasResourceMappers > and then the custom ones. This is unnecessary - we should just instantiate > the default ones and classload the custom ones. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (RANGER-1446) Ranger Solr Plugin does not work when the collection list in the request is empty
[ https://issues.apache.org/jira/browse/RANGER-1446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16019788#comment-16019788 ] Colm O hEigeartaigh commented on RANGER-1446: - Hi [~yzhou2001], I'm wondering if the RangerSolrAuthorizer..createRequest logic should be modified after this change (to default to "true"). If no collection name is specified then it will not attempt any authorization. I'm not sure if this could arise in practise or not. It would seem safer to default to "*" if no collection name is specified and to perform the authorization. Would this change break your tests? Colm. > Ranger Solr Plugin does not work when the collection list in the request is > empty > - > > Key: RANGER-1446 > URL: https://issues.apache.org/jira/browse/RANGER-1446 > Project: Ranger > Issue Type: Bug > Components: plugins >Affects Versions: 0.7.0, 0.6.1, 0.6.2, 0.6.3 >Reporter: Yan >Assignee: Yan >Priority: Critical > Fix For: 1.0.0, 0.7.1 > > Attachments: > 0001-Ranger-1446-Ranger-Solr-Plugin-does-not-work-when-th.patch > > > The fix of Ranger-1095 set the initial value of "denied" to "true" from the > previous "false". One impact of this change is that, when > context.getCollectionRequests() is empty which could be the case in many > invocations Solr makes to Ranger on authorization per client request, the > permission is plainly denied without going to Ranger policy engine. So the > fix changed the default behavior related "denied". > A proper fix of Ranger-1095 IMO should be just to set the "denied" to "true" > in the catch block without changing the initial value of the variable. > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (RANGER-1608) SOLR resource lookup fails with basic auth
Colm O hEigeartaigh created RANGER-1608: --- Summary: SOLR resource lookup fails with basic auth Key: RANGER-1608 URL: https://issues.apache.org/jira/browse/RANGER-1608 Project: Ranger Issue Type: Bug Components: admin Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 1.0.0 Currently, the SOLR connection test + subsequent resource lookup when creating policies fails when basic authentication is enabled in SOLR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1608) SOLR resource lookup fails with basic auth
[ https://issues.apache.org/jira/browse/RANGER-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1608: Attachment: 0001-RANGER-1608-SOLR-resource-lookup-fails-with-basic-au.patch > SOLR resource lookup fails with basic auth > -- > > Key: RANGER-1608 > URL: https://issues.apache.org/jira/browse/RANGER-1608 > Project: Ranger > Issue Type: Bug > Components: admin > Reporter: Colm O hEigeartaigh > Assignee: Colm O hEigeartaigh > Fix For: 1.0.0 > > Attachments: > 0001-RANGER-1608-SOLR-resource-lookup-fails-with-basic-au.patch > > > Currently, the SOLR connection test + subsequent resource lookup when > creating policies fails when basic authentication is enabled in SOLR. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (RANGER-1050) Change my name on all systems
[ https://issues.apache.org/jira/browse/RANGER-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved RANGER-1050. - Resolution: Not A Problem > Change my name on all systems > - > > Key: RANGER-1050 > URL: https://issues.apache.org/jira/browse/RANGER-1050 > Project: Ranger > Issue Type: Bug > Components: admin >Reporter: Josephine Agyekum-Bonsu > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (RANGER-1050) Change my name on all systems
[ https://issues.apache.org/jira/browse/RANGER-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed RANGER-1050. --- > Change my name on all systems > - > > Key: RANGER-1050 > URL: https://issues.apache.org/jira/browse/RANGER-1050 > Project: Ranger > Issue Type: Bug > Components: admin >Reporter: Josephine Agyekum-Bonsu > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (RANGER-1049) Testing connection at a Kerberos server
[
https://issues.apache.org/jira/browse/RANGER-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh resolved RANGER-1049.
-
Resolution: Cannot Reproduce
Please refer questions to the Ranger users mailing list instead.
> Testing connection at a Kerberos server
> ---
>
> Key: RANGER-1049
> URL: https://issues.apache.org/jira/browse/RANGER-1049
> Project: Ranger
> Issue Type: Bug
> Components: admin, plugins
>Affects Versions: 0.5.3
> Environment: CenOS6.7/zookeeper3.4.6/hadoop2.7.1/Ranger0.5.3
>Reporter: Myungsun
>Priority: Minor
>
> Hi~
> The Ranger's HDFS connection test failed in a Kerberos Server.
> Of course, I refer to this [RANGER-399]
> Please Give your help
> ## Ranger ERROR xa_portal.log ##
> 2016-06-22 17:17:20,327 [timed-executor-pool-0] INFO
> org.apache.ranger.plugin.client.BaseClient (BaseClient.java:100) - Init
> Login: using username/password
> 2016-06-22 17:17:20,339 [timed-executor-pool-0] ERROR
> apache.ranger.services.hdfs.client.HdfsResourceMgr (HdfsResourceMgr.java:48)
> - <== HdfsResourceMgr.testConnection Error:
> org.apache.ranger.plugin.client.HadoopException: Unable to login to Hadoop
> environment [hadoop]
> 2016-06-22 17:17:20,339 [timed-executor-pool-0] ERROR
> org.apache.ranger.services.hdfs.RangerServiceHdfs (RangerServiceHdfs.java:59)
> - <== RangerServiceHdfs.validateConfig
> Error:org.apache.ranger.plugin.client.HadoopException: Unable to login to
> Hadoop environment [hadoop]
> 2016-06-22 17:17:20,339 [timed-executor-pool-0] ERROR
> org.apache.ranger.biz.ServiceMgr$TimedCallable (ServiceMgr.java:434) -
> TimedCallable.call: Error:org.apache.ranger.plugin.client.HadoopException:
> Unable to login to Hadoop environment [hadoop]
> 2016-06-22 17:17:20,339 [timed-executor-pool-0] DEBUG
> org.apache.ranger.biz.ServiceMgr$TimedCallable (ServiceMgr.java:442) - <==
> TimedCallable: validate config for service[hadoop]: wait time[0 ms],
> execution time [12 ms]
> 2016-06-22 17:17:20,339 [http-bio-6080-exec-5] DEBUG
> org.apache.ranger.common.TimedExecutor (TimedExecutor.java:92) -
> TimedExecutor: Caught exception[java.util.concurrent.ExecutionException] for
> callable[validate config for service[hadoop]]:
> detail[org.apache.ranger.plugin.client.HadoopException: Unable to login to
> Hadoop environment [hadoop]]. Re-throwing...
> 2016-06-22 17:17:20,340 [http-bio-6080-exec-5] ERROR
> org.apache.ranger.biz.ServiceMgr (ServiceMgr.java:120) - ==>
> ServiceMgr.validateConfig Error:java.util.concurrent.ExecutionException:
> org.apache.ranger.plugin.client.HadoopException: Unable to login to Hadoop
> environment [hadoop]
> 2016-06-22 17:17:20,340 [http-bio-6080-exec-5] DEBUG
> org.apache.ranger.biz.ServiceMgr (ServiceMgr.java:125) - ==>
> ServiceMgr.validateConfig for Response:
> (VXResponse={org.apache.ranger.view.VXResponse@1cf17880statusCode={1}
> msgDesc={Unable to connect repository with given config for hadoop}
> messageList={[VXMessage={org.apache.ranger.view.VXMessage@311e2a58name={null}
> rbKey={null} message={Unable to connect repository with given config for
> hadoop} objectId={null} fieldName={null} }]} })
> Ranger HDFS
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Closed] (RANGER-1049) Testing connection at a Kerberos server
[
https://issues.apache.org/jira/browse/RANGER-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh closed RANGER-1049.
---
> Testing connection at a Kerberos server
> ---
>
> Key: RANGER-1049
> URL: https://issues.apache.org/jira/browse/RANGER-1049
> Project: Ranger
> Issue Type: Bug
> Components: admin, plugins
>Affects Versions: 0.5.3
> Environment: CenOS6.7/zookeeper3.4.6/hadoop2.7.1/Ranger0.5.3
>Reporter: Myungsun
>Priority: Minor
>
> Hi~
> The Ranger's HDFS connection test failed in a Kerberos Server.
> Of course, I refer to this [RANGER-399]
> Please Give your help
> ## Ranger ERROR xa_portal.log ##
> 2016-06-22 17:17:20,327 [timed-executor-pool-0] INFO
> org.apache.ranger.plugin.client.BaseClient (BaseClient.java:100) - Init
> Login: using username/password
> 2016-06-22 17:17:20,339 [timed-executor-pool-0] ERROR
> apache.ranger.services.hdfs.client.HdfsResourceMgr (HdfsResourceMgr.java:48)
> - <== HdfsResourceMgr.testConnection Error:
> org.apache.ranger.plugin.client.HadoopException: Unable to login to Hadoop
> environment [hadoop]
> 2016-06-22 17:17:20,339 [timed-executor-pool-0] ERROR
> org.apache.ranger.services.hdfs.RangerServiceHdfs (RangerServiceHdfs.java:59)
> - <== RangerServiceHdfs.validateConfig
> Error:org.apache.ranger.plugin.client.HadoopException: Unable to login to
> Hadoop environment [hadoop]
> 2016-06-22 17:17:20,339 [timed-executor-pool-0] ERROR
> org.apache.ranger.biz.ServiceMgr$TimedCallable (ServiceMgr.java:434) -
> TimedCallable.call: Error:org.apache.ranger.plugin.client.HadoopException:
> Unable to login to Hadoop environment [hadoop]
> 2016-06-22 17:17:20,339 [timed-executor-pool-0] DEBUG
> org.apache.ranger.biz.ServiceMgr$TimedCallable (ServiceMgr.java:442) - <==
> TimedCallable: validate config for service[hadoop]: wait time[0 ms],
> execution time [12 ms]
> 2016-06-22 17:17:20,339 [http-bio-6080-exec-5] DEBUG
> org.apache.ranger.common.TimedExecutor (TimedExecutor.java:92) -
> TimedExecutor: Caught exception[java.util.concurrent.ExecutionException] for
> callable[validate config for service[hadoop]]:
> detail[org.apache.ranger.plugin.client.HadoopException: Unable to login to
> Hadoop environment [hadoop]]. Re-throwing...
> 2016-06-22 17:17:20,340 [http-bio-6080-exec-5] ERROR
> org.apache.ranger.biz.ServiceMgr (ServiceMgr.java:120) - ==>
> ServiceMgr.validateConfig Error:java.util.concurrent.ExecutionException:
> org.apache.ranger.plugin.client.HadoopException: Unable to login to Hadoop
> environment [hadoop]
> 2016-06-22 17:17:20,340 [http-bio-6080-exec-5] DEBUG
> org.apache.ranger.biz.ServiceMgr (ServiceMgr.java:125) - ==>
> ServiceMgr.validateConfig for Response:
> (VXResponse={org.apache.ranger.view.VXResponse@1cf17880statusCode={1}
> msgDesc={Unable to connect repository with given config for hadoop}
> messageList={[VXMessage={org.apache.ranger.view.VXMessage@311e2a58name={null}
> rbKey={null} message={Unable to connect repository with given config for
> hadoop} objectId={null} fieldName={null} }]} })
> Ranger HDFS
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (RANGER-1584) Allow tagsync to support log directory from Ambari configuration
[ https://issues.apache.org/jira/browse/RANGER-1584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1584: Fix Version/s: 1.0.0 > Allow tagsync to support log directory from Ambari configuration > > > Key: RANGER-1584 > URL: https://issues.apache.org/jira/browse/RANGER-1584 > Project: Ranger > Issue Type: Bug > Components: tagsync >Affects Versions: master, 0.7.1 >Reporter: Yujie Li >Assignee: Yujie Li >Priority: Minor > Fix For: 1.0.0, 0.7.1 > > Attachments: > 0001-RANGER-1584-Allow-tagsync-to-support-log-directory-f.patch > > > Currently Tagsync hardcodes the log directory as /var/log/ranger/tagsync. It > doesn't support customization setting for log location from Ambari side. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (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:all-tabpanel ] Colm O hEigeartaigh updated RANGER-689: --- Summary: For Solr plugin, use resources folders for adding Ranger properties (was: For Solr plugin, use lib/ext and resources folders for adding Ranger jars and properties) > 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 > > 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.3.15#6346)
[jira] [Assigned] (RANGER-689) For Solr plugin, use lib/ext and resources folders for adding Ranger jars and properties
[ https://issues.apache.org/jira/browse/RANGER-689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh reassigned RANGER-689: -- Assignee: Colm O hEigeartaigh > For Solr plugin, use lib/ext and resources folders for adding Ranger jars and > 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 > > 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.3.15#6346)
[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&focusedCommentId=16022697#comment-16022697 ] Colm O hEigeartaigh commented on RANGER-689: Putting the jars into service/lib/ext does not seem to work. I will submit a patch to put the resources into server/resources 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 > > 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.3.15#6346)
[jira] [Updated] (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:all-tabpanel ] Colm O hEigeartaigh updated RANGER-689: --- Fix Version/s: 1.0.0 > 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 > > > 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.3.15#6346)
[jira] [Updated] (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:all-tabpanel ] Colm O hEigeartaigh updated RANGER-689: --- Attachment: 0001-RANGER-689-For-Solr-plugin-use-resources-folders-for.patch > 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.3.15#6346)
[jira] [Created] (RANGER-1616) Upgrade to Mockito 2
Colm O hEigeartaigh created RANGER-1616: --- Summary: Upgrade to Mockito 2 Key: RANGER-1616 URL: https://issues.apache.org/jira/browse/RANGER-1616 Project: Ranger Issue Type: Improvement Components: admin Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 1.0.0 This task is to upgrade the mockito testing framework to mockito 2. Mockito 2 works with Java 9 and it also enforces that the test-code is kept tidy by making sure that unused mocks aren't allowed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1616) Upgrade to Mockito 2
[ https://issues.apache.org/jira/browse/RANGER-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1616: Attachment: 0001-RANGER-1616-Upgrade-to-Mockito-2.patch > Upgrade to Mockito 2 > > > Key: RANGER-1616 > URL: https://issues.apache.org/jira/browse/RANGER-1616 > Project: Ranger > Issue Type: Improvement > Components: admin > Reporter: Colm O hEigeartaigh > Assignee: Colm O hEigeartaigh > Fix For: 1.0.0 > > Attachments: 0001-RANGER-1616-Upgrade-to-Mockito-2.patch > > > This task is to upgrade the mockito testing framework to mockito 2. Mockito 2 > works with Java 9 and it also enforces that the test-code is kept tidy by > making sure that unused mocks aren't allowed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1616) Upgrade to Mockito 2
[ https://issues.apache.org/jira/browse/RANGER-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1616: Attachment: (was: 0001-RANGER-1616-Upgrade-to-Mockito-2.patch) > Upgrade to Mockito 2 > > > Key: RANGER-1616 > URL: https://issues.apache.org/jira/browse/RANGER-1616 > Project: Ranger > Issue Type: Improvement > Components: admin > Reporter: Colm O hEigeartaigh > Assignee: Colm O hEigeartaigh > Fix For: 1.0.0 > > > This task is to upgrade the mockito testing framework to mockito 2. Mockito 2 > works with Java 9 and it also enforces that the test-code is kept tidy by > making sure that unused mocks aren't allowed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (RANGER-1616) Upgrade to Mockito 2
[ https://issues.apache.org/jira/browse/RANGER-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated RANGER-1616: Attachment: 0001-RANGER-1616-Upgrade-to-Mockito-2.patch > Upgrade to Mockito 2 > > > Key: RANGER-1616 > URL: https://issues.apache.org/jira/browse/RANGER-1616 > Project: Ranger > Issue Type: Improvement > Components: admin > Reporter: Colm O hEigeartaigh > Assignee: Colm O hEigeartaigh > Fix For: 1.0.0 > > Attachments: 0001-RANGER-1616-Upgrade-to-Mockito-2.patch > > > This task is to upgrade the mockito testing framework to mockito 2. Mockito 2 > works with Java 9 and it also enforces that the test-code is kept tidy by > making sure that unused mocks aren't allowed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (RANGER-1076) XML export of *all* issues of type bug
[ https://issues.apache.org/jira/browse/RANGER-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved RANGER-1076. - Resolution: Not A Problem > XML export of *all* issues of type bug > -- > > Key: RANGER-1076 > URL: https://issues.apache.org/jira/browse/RANGER-1076 > Project: Ranger > Issue Type: Bug > Components: admin >Reporter: Clayton Lemons > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (RANGER-1076) XML export of *all* issues of type bug
[ https://issues.apache.org/jira/browse/RANGER-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed RANGER-1076. --- > XML export of *all* issues of type bug > -- > > Key: RANGER-1076 > URL: https://issues.apache.org/jira/browse/RANGER-1076 > Project: Ranger > Issue Type: Bug > Components: admin >Reporter: Clayton Lemons > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (RANGER-1337) test jira permission for newly created jira - please ignore
[ https://issues.apache.org/jira/browse/RANGER-1337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved RANGER-1337. - Resolution: Not A Problem > test jira permission for newly created jira - please ignore > --- > > Key: RANGER-1337 > URL: https://issues.apache.org/jira/browse/RANGER-1337 > Project: Ranger > Issue Type: Bug > Components: build-infra >Reporter: Selvamohan Neethiraj > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (RANGER-947) Access to report bugs for Apache Commons VFS
[ https://issues.apache.org/jira/browse/RANGER-947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved RANGER-947. Resolution: Not A Problem > Access to report bugs for Apache Commons VFS > > > Key: RANGER-947 > URL: https://issues.apache.org/jira/browse/RANGER-947 > Project: Ranger > Issue Type: Bug > Components: admin >Reporter: Raghavendra > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (RANGER-1337) test jira permission for newly created jira - please ignore
[ https://issues.apache.org/jira/browse/RANGER-1337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh closed RANGER-1337. --- > test jira permission for newly created jira - please ignore > --- > > Key: RANGER-1337 > URL: https://issues.apache.org/jira/browse/RANGER-1337 > Project: Ranger > Issue Type: Bug > Components: build-infra >Reporter: Selvamohan Neethiraj > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
