[jira] [Created] (HADOOP-16198) Upgrade Jackson-databind version to 2.9.8
Bharat Viswanadham created HADOOP-16198: --- Summary: Upgrade Jackson-databind version to 2.9.8 Key: HADOOP-16198 URL: https://issues.apache.org/jira/browse/HADOOP-16198 Project: Hadoop Common Issue Type: Bug Reporter: Bharat Viswanadham Assignee: Bharat Viswanadham Jackson-databind is affected by below CVEs and are getting reported by Customers. CVE-2018-14719 CVE-2018-14720 CVE-2018-14721 CVE-2018-1000873 CVE-2018-7489 CVE-2018-19362 CVE-2017-15095 CVE-2018-19361 CVE-2017-7525 CVE-2018-19360 CVE-2017-17485 CVE-2018-5968 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Resolved] (HADOOP-16198) Upgrade Jackson-databind version to 2.9.8
[ https://issues.apache.org/jira/browse/HADOOP-16198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham resolved HADOOP-16198. - Resolution: Duplicate > Upgrade Jackson-databind version to 2.9.8 > - > > Key: HADOOP-16198 > URL: https://issues.apache.org/jira/browse/HADOOP-16198 > Project: Hadoop Common > Issue Type: Bug >Reporter: Bharat Viswanadham >Assignee: Bharat Viswanadham >Priority: Major > > Jackson-databind 2.9.8 has a few fixes which are important to include. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Resolved] (HADOOP-16302) Fix typo on Hadoop Site Help dropdown menu
[ https://issues.apache.org/jira/browse/HADOOP-16302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham resolved HADOOP-16302. - Resolution: Fixed > Fix typo on Hadoop Site Help dropdown menu > -- > > Key: HADOOP-16302 > URL: https://issues.apache.org/jira/browse/HADOOP-16302 > Project: Hadoop Common > Issue Type: Bug > Components: site >Affects Versions: asf-site >Reporter: Dinesh Chitlangia >Assignee: Dinesh Chitlangia >Priority: Minor > Attachments: Screen Shot 2019-05-07 at 11.57.01 PM.png > > > On hadoop.apache.org the Help tab on top menu bar has Sponsorship spelt as > Sponsorshop. > This jira aims to fix this typo. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-16372) Fix typo in DFSUtil getHttpPolicy method
Bharat Viswanadham created HADOOP-16372: --- Summary: Fix typo in DFSUtil getHttpPolicy method Key: HADOOP-16372 URL: https://issues.apache.org/jira/browse/HADOOP-16372 Project: Hadoop Common Issue Type: Bug Reporter: Bharat Viswanadham [https://github.com/apache/hadoop/blob/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DFSUtil.java#L1479] -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Resolved] (HADOOP-16373) Fix typo in FileSystemShell#test documentation
[
https://issues.apache.org/jira/browse/HADOOP-16373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Viswanadham resolved HADOOP-16373.
-
Resolution: Fixed
Fix Version/s: 0.5.0
> Fix typo in FileSystemShell#test documentation
> --
>
> Key: HADOOP-16373
> URL: https://issues.apache.org/jira/browse/HADOOP-16373
> Project: Hadoop Common
> Issue Type: Bug
> Components: documentation
>Affects Versions: 2.7.1, 3.0.0, 3.2.0, 2.9.2, 3.1.2
>Reporter: Dinesh Chitlangia
>Assignee: Dinesh Chitlangia
>Priority: Trivial
> Fix For: 0.5.0
>
>
> Typo is describing option -d
> https://hadoop.apache.org/docs/r3.1.2/hadoop-project-dist/hadoop-common/FileSystemShell.html#test
> {code:java}
> test
> Usage: hadoop fs -test -[defsz] URI
> Options:
> -d: f the path is a directory, return 0.
> -e: if the path exists, return 0.
> -f: if the path is a file, return 0.
> -s: if the path is not empty, return 0.
> -z: if the file is zero length, return 0.
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-17245) Add RootedOzFS AbstractFileSystem to core-default.xml
Bharat Viswanadham created HADOOP-17245: --- Summary: Add RootedOzFS AbstractFileSystem to core-default.xml Key: HADOOP-17245 URL: https://issues.apache.org/jira/browse/HADOOP-17245 Project: Hadoop Common Issue Type: Bug Reporter: Bharat Viswanadham Assignee: Bharat Viswanadham When "ofs" is default, when running mapreduce job, YarnClient fails with below exception. Caused by: org.apache.hadoop.fs.UnsupportedFileSystemException: fs.AbstractFileSystem.ofs.impl=null: No AbstractFileSystem configured for scheme: ofs at org.apache.hadoop.fs.AbstractFileSystem.createFileSystem(AbstractFileSystem.java:176) at org.apache.hadoop.fs.AbstractFileSystem.get(AbstractFileSystem.java:265) at org.apache.hadoop.fs.FileContext$2.run(FileContext.java:341) at org.apache.hadoop.fs.FileContext$2.run(FileContext.java:338) at java.security.AccessController.doPrivileged(Native Method) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-14847) Remove Guava Supplier and change to java Supplier in AMRMClient and AMRMClientAysnc
Bharat Viswanadham created HADOOP-14847: --- Summary: Remove Guava Supplier and change to java Supplier in AMRMClient and AMRMClientAysnc Key: HADOOP-14847 URL: https://issues.apache.org/jira/browse/HADOOP-14847 Project: Hadoop Common Issue Type: Sub-task Reporter: Bharat Viswanadham Remove the Guava library Supplier usage in user facing API's in AMRMClient.java and AMRMClientAsync.java -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Resolved] (HADOOP-14697) Analyze the properties files which need to be included/excluded from hadoop-client-runtime and hadoop-client-minicluster
[ https://issues.apache.org/jira/browse/HADOOP-14697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham resolved HADOOP-14697. - Resolution: Duplicate This is being taken care in Thanks [~busbey] for handling this.[https://issues.apache.org/jira/browse/HADOOP-14089] > Analyze the properties files which need to be included/excluded from > hadoop-client-runtime and hadoop-client-minicluster > > > Key: HADOOP-14697 > URL: https://issues.apache.org/jira/browse/HADOOP-14697 > Project: Hadoop Common > Issue Type: Sub-task >Reporter: Bharat Viswanadham > > about.html > capacity-scheduler.xml > catalog.cat > container-log4j.properties > hdfs-default.xml > java.policy > javaee_5.xsd > javaee_6.xsd > javaee_web_services_client_1_2.xsd > javaee_web_services_client_1_3.xsd > jdtCompilerAdapter.jar > jsp_2_1.xsd > jsp_2_2.xsd > krb5.conf > log4j.properties > plugin.properties > plugin.xml > web-app_2_5.xsd > web-app_3_0.xsd > web-common_3_0.xsd > xml.xsd > This issue is raised from [https://issues.apache.org/jira/browse/HADOOP-14685] -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-14867) Update HDFS Federation Document, for incorrect property name for secondary name node
Bharat Viswanadham created HADOOP-14867: --- Summary: Update HDFS Federation Document, for incorrect property name for secondary name node Key: HADOOP-14867 URL: https://issues.apache.org/jira/browse/HADOOP-14867 Project: Hadoop Common Issue Type: Bug Reporter: Bharat Viswanadham HDFS Federation setup documentation is having incorrect property name for secondary namenode http port It is mentioned as dfs.namenode.secondaryhttp-address.ns1 snn-host1:http-port dfs.namenode.rpc-address.ns2 nn-host2:rpc-port Actual property should be dfs.namenode.secondary.http-address.ns. Because of this documentation error, when the document is followed and user tries to setup HDFS federated cluster, secondary namenode will not be started and also hdfs getconf -secondarynamenodes will throw an exception -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-14894) ReflectionUtils should use Time.monotonicNow to mesaure duration
Bharat Viswanadham created HADOOP-14894: --- Summary: ReflectionUtils should use Time.monotonicNow to mesaure duration Key: HADOOP-14894 URL: https://issues.apache.org/jira/browse/HADOOP-14894 Project: Hadoop Common Issue Type: Sub-task Reporter: Bharat Viswanadham ReflectionUtils should use Time.monotonicNow to mesaure duration -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-14915) method name is incorrect in ConfServlet
Bharat Viswanadham created HADOOP-14915: --- Summary: method name is incorrect in ConfServlet Key: HADOOP-14915 URL: https://issues.apache.org/jira/browse/HADOOP-14915 Project: Hadoop Common Issue Type: Bug Reporter: Bharat Viswanadham Assignee: Bharat Viswanadham Priority: Minor method name is parseAccecptHeader. Modify it as parseAcceptHeader -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-14916) Replace HdfsFileStatus constructors with a builder pattern.
Bharat Viswanadham created HADOOP-14916: --- Summary: Replace HdfsFileStatus constructors with a builder pattern. Key: HADOOP-14916 URL: https://issues.apache.org/jira/browse/HADOOP-14916 Project: Hadoop Common Issue Type: Bug Reporter: Bharat Viswanadham -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-14929) Cleanup usage of decodecomponent and use QueryStringDecoder from netty
Bharat Viswanadham created HADOOP-14929: --- Summary: Cleanup usage of decodecomponent and use QueryStringDecoder from netty Key: HADOOP-14929 URL: https://issues.apache.org/jira/browse/HADOOP-14929 Project: Hadoop Common Issue Type: Bug Reporter: Bharat Viswanadham Assignee: Bharat Viswanadham This is from the review of HADOOP-14910 There is also other place usage of decodeComponent(param(CreateFlagParam.NAME), StandardCharsets.UTF_8); In ParameterParser.java Line 147-148: String cf = decodeComponent(param(CreateFlagParam.NAME), StandardCharsets.UTF_8); Use QueryStringDecoder from netty here too and cleanup the decodeComponent. Actually this is added for netty issue only. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-14934) Remove Warnings when building ozone
Bharat Viswanadham created HADOOP-14934: --- Summary: Remove Warnings when building ozone Key: HADOOP-14934 URL: https://issues.apache.org/jira/browse/HADOOP-14934 Project: Hadoop Common Issue Type: Bug Reporter: Bharat Viswanadham [WARNING] [WARNING] Some problems were encountered while building the effective model for org.apache.hadoop:hadoop-ozone:jar:3.1.0-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-project-info-reports-plugin is missing. @ org.apache.hadoop:hadoop-ozone:[unknown-version], /Users/aengineer/codereview/hadoop-tools/hadoop-ozone/pom.xml, line 36, column 15 [WARNING] [WARNING] Some problems were encountered while building the effective model for org.apache.hadoop:hadoop-dist:jar:3.1.0-SNAPSHOT [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-gpg-plugin is missing. @ line 133, column 15 [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. [WARNING] -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-15168) Add kdiag and HadoopKerberosName tools to hadoop command
Bharat Viswanadham created HADOOP-15168: --- Summary: Add kdiag and HadoopKerberosName tools to hadoop command Key: HADOOP-15168 URL: https://issues.apache.org/jira/browse/HADOOP-15168 Project: Hadoop Common Issue Type: Bug Reporter: Bharat Viswanadham Assignee: Bharat Viswanadham -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Resolved] (HADOOP-15139) [Umbrella] Improvements and fixes for Hadoop shaded client work
[ https://issues.apache.org/jira/browse/HADOOP-15139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham resolved HADOOP-15139. - Resolution: Fixed Target Version/s: 3.1.1, 3.2.0 (was: 3.2.0) > [Umbrella] Improvements and fixes for Hadoop shaded client work > > > Key: HADOOP-15139 > URL: https://issues.apache.org/jira/browse/HADOOP-15139 > Project: Hadoop Common > Issue Type: Bug >Reporter: Junping Du >Assignee: Bharat Viswanadham >Priority: Critical > > In HADOOP-11656, we have made great progress in splitting out third-party > dependencies from shaded hadoop client jar (hadoop-client-api), put runtime > dependencies in hadoop-client-runtime, and have shaded version of > hadoop-client-minicluster for test. However, there are still some left work > for this feature to be fully completed: > - We don't have a comprehensive documentation to guide downstream > projects/users to use shaded JARs instead of previous JARs > - We should consider to wrap up hadoop tools (distcp, aws, azure) to have > shaded version > - More issues could be identified when shaded jars are adopted in more test > and production environment, like HADOOP-15137. > Let's have this umbrella JIRA to track all efforts that left to improve > hadoop shaded client effort. > CC [~busbey], [~bharatviswa] and [~vinodkv]. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-15879) Upgrade eclipse jetty version to 9.3.25.v20180904
Bharat Viswanadham created HADOOP-15879: --- Summary: Upgrade eclipse jetty version to 9.3.25.v20180904 Key: HADOOP-15879 URL: https://issues.apache.org/jira/browse/HADOOP-15879 Project: Hadoop Common Issue Type: Task Reporter: Bharat Viswanadham -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-15924) Hadoop aws cannot be used with shaded jars
Bharat Viswanadham created HADOOP-15924: --- Summary: Hadoop aws cannot be used with shaded jars Key: HADOOP-15924 URL: https://issues.apache.org/jira/browse/HADOOP-15924 Project: Hadoop Common Issue Type: Bug Reporter: Bharat Viswanadham Issue is hadoop-aws cannot be used with shaded jars. The recommended client side jars for hadoop 3 are client-api/runtime shaded jars. They shade guava etc. So something like SemaphoredDelegatingExecutor refers to shaded guava classes. hadoop-aws has S3AFileSystem implementation which refers to SemaphoredDelegatingExecutor with unshaded guava ListeningService in the constructor. When S3AFileSystem is created then it uses the hadoop-api jar and finds SemaphoredDelegatingExecutor but not the right constructor because in client-api jar SemaphoredDelegatingExecutor constructor has the shaded guava ListenerService. So essentially none of the aws/azure/adl hadoop FS implementations will work with the shaded Hadoop client runtime jars. This Jira is created to track the work required to make hadoop-aws work with hadoop shaded client jars. The solution for this can be, hadoop-aws depends on hadoop shaded jars. In this way, we shall not see the issue. Currently, hadoop-aws depends on aws-sdk-bundle and all other remaining jars are provided dependencies. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Resolved] (HADOOP-17905) Modify Text.ensureCapacity() to efficiently max out the backing array size
[ https://issues.apache.org/jira/browse/HADOOP-17905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham resolved HADOOP-17905. - Fix Version/s: 3.3.2 Resolution: Fixed > Modify Text.ensureCapacity() to efficiently max out the backing array size > -- > > Key: HADOOP-17905 > URL: https://issues.apache.org/jira/browse/HADOOP-17905 > Project: Hadoop Common > Issue Type: Improvement >Reporter: Peter Bacsko >Assignee: Peter Bacsko >Priority: Major > Labels: pull-request-available > Fix For: 3.3.2 > > Time Spent: 3h 50m > Remaining Estimate: 0h > > This is a continuation of HADOOP-17901. > Right now we use a factor of 1.5x to increase the byte array if it's full. > However, if the size reaches a certain point, the increment is only (current > size + length). This can cause performance issues if the textual data which > we intend to store is beyond this point. > Instead, let's max out the array to the maximum. Based on different sources, > a safe choice seems to be Integer.MAX_VALUE - 8 (see ArrayList, > AbstractCollection, HashTable, etc). -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-14685) Test jars to exclude from hadoop-client-minicluster jar
Bharat Viswanadham created HADOOP-14685: --- Summary: Test jars to exclude from hadoop-client-minicluster jar Key: HADOOP-14685 URL: https://issues.apache.org/jira/browse/HADOOP-14685 Project: Hadoop Common Issue Type: Bug Components: common Affects Versions: 3.0.0-beta1 Reporter: Bharat Viswanadham Assignee: Bharat Viswanadham This jira is to discuss, what test jars to be included/excluded from hadoop-client-minicluster -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
[jira] [Created] (HADOOP-14697) Analyze the properties files which need to be included/excluded from hadoop-client-runtime and hadoop-client-minicluster
Bharat Viswanadham created HADOOP-14697: --- Summary: Analyze the properties files which need to be included/excluded from hadoop-client-runtime and hadoop-client-minicluster Key: HADOOP-14697 URL: https://issues.apache.org/jira/browse/HADOOP-14697 Project: Hadoop Common Issue Type: Sub-task Reporter: Bharat Viswanadham about.html capacity-scheduler.xml catalog.cat container-log4j.properties hdfs-default.xml java.policy javaee_5.xsd javaee_6.xsd javaee_web_services_client_1_2.xsd javaee_web_services_client_1_3.xsd jdtCompilerAdapter.jar jsp_2_1.xsd jsp_2_2.xsd krb5.conf log4j.properties plugin.properties plugin.xml web-app_2_5.xsd web-app_3_0.xsd web-common_3_0.xsd xml.xsd This issue is raised from [https://issues.apache.org/jira/browse/HADOOP-14685] -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org
