[jira] [Reopened] (HADOOP-7418) support for multiple slashes in the path separator
[ https://issues.apache.org/jira/browse/HADOOP-7418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Kumar M R reopened HADOOP-7418: - Assignee: (was: Andrew Look) support for multiple slashes in the path separator -- Key: HADOOP-7418 URL: https://issues.apache.org/jira/browse/HADOOP-7418 Project: Hadoop Common Issue Type: Bug Affects Versions: 0.23.0 Environment: Linux running JDK 1.6 Reporter: Sudharsan Sampath Priority: Minor Labels: BB2015-05-RFC, newbie Attachments: HADOOP-7418--20110719.txt, HADOOP-7418.txt, HADOOP-7418.txt, HDFS-1460.txt, HDFS-1460.txt the parsing of the input path string to identify the uri authority conflicts with the file system paths. For instance the following is a valid path in both the linux file system and the hdfs. //user/directory1//directory2. While this works perfectly fine in the command line for manipulating hdfs, the same fails when specified as the input path for a mapper class with the following expcetion. Exception in thread main java.net.UnknownHostException: unknown host: user at org.apache.hadoop.ipc.Client$Connection.init(Client.java:195) as the org.apache.hadoop.fs.Path class assumes the string that follows the '//' to be an uri authority -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HADOOP-11939) deprecate DistCpV1 and Logalyzer
Brahma Reddy Battula created HADOOP-11939: - Summary: deprecate DistCpV1 and Logalyzer Key: HADOOP-11939 URL: https://issues.apache.org/jira/browse/HADOOP-11939 Project: Hadoop Common Issue Type: Bug Reporter: Brahma Reddy Battula Assignee: Brahma Reddy Battula -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (HADOOP-8087) Paths that start with a double slash cause No filesystem for scheme: null errors
[
https://issues.apache.org/jira/browse/HADOOP-8087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kiran Kumar M R reopened HADOOP-8087:
-
Assignee: (was: Rajesh Kartha)
Paths that start with a double slash cause No filesystem for scheme: null
errors
--
Key: HADOOP-8087
URL: https://issues.apache.org/jira/browse/HADOOP-8087
Project: Hadoop Common
Issue Type: Bug
Affects Versions: 0.23.0, 0.24.0
Reporter: Daryn Sharp
Attachments: HADOOP-8087.001.patch, HADOOP-8087.002.patch,
HADOOP-8087.003.patch, HADOOP-8087.004.patch, HADOOP-8087.005.patch
{{Path}} is incorrectly parsing {{//dir/path}} in a very unexpected way.
While it should translate to the directory {{$fs.default.name}/dir/path}}, it
instead discards the {{//dir}} and returns
{{$fs.default.name/path}}. The problem is {{Path}} is trying to parsing an
authority even when a scheme is not present.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (HADOOP-7418) support for multiple slashes in the path separator
[ https://issues.apache.org/jira/browse/HADOOP-7418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Kumar M R resolved HADOOP-7418. - Resolution: Duplicate HADOOP-8087 had patch attached recently. Fix for this issue can discussed and closed in that. support for multiple slashes in the path separator -- Key: HADOOP-7418 URL: https://issues.apache.org/jira/browse/HADOOP-7418 Project: Hadoop Common Issue Type: Bug Affects Versions: 0.23.0 Environment: Linux running JDK 1.6 Reporter: Sudharsan Sampath Priority: Minor Labels: BB2015-05-RFC, newbie Attachments: HADOOP-7418--20110719.txt, HADOOP-7418.txt, HADOOP-7418.txt, HDFS-1460.txt, HDFS-1460.txt the parsing of the input path string to identify the uri authority conflicts with the file system paths. For instance the following is a valid path in both the linux file system and the hdfs. //user/directory1//directory2. While this works perfectly fine in the command line for manipulating hdfs, the same fails when specified as the input path for a mapper class with the following expcetion. Exception in thread main java.net.UnknownHostException: unknown host: user at org.apache.hadoop.ipc.Client$Connection.init(Client.java:195) as the org.apache.hadoop.fs.Path class assumes the string that follows the '//' to be an uri authority -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[DISCUSS] branch-1
May we declare this branch dead and just close bugs (but not necessarily concepts, ideas, etc) with won’t fix? I don’t think anyone has any intention of working on the 1.3 release, especially given that 1.2.1 was Aug 2013 …. I guess we need a PMC member to declare a vote or whatever….
Re: [DISCUSS] branch-1
I would be -1 to declaring the branch dead just yet. There have been 7 commits to that branch this year. I know this isn't comparable to trunk or branch-2, but it is not negligible either. I propose we come up with a policy for deprecating past major release branches. May be, something along the lines of - deprecate branch-x when release x+3.0.0 goes GA? On Fri, May 8, 2015 at 10:41 AM, Allen Wittenauer a...@altiscale.com wrote: May we declare this branch dead and just close bugs (but not necessarily concepts, ideas, etc) with won’t fix? I don’t think anyone has any intention of working on the 1.3 release, especially given that 1.2.1 was Aug 2013 …. I guess we need a PMC member to declare a vote or whatever…. -- Karthik Kambatla Software Engineer, Cloudera Inc. http://five.sentenc.es
Re: [DISCUSS] branch-1
+1 to auto-closing branch-1 issues. -Sandy On Fri, May 8, 2015 at 11:14 AM, Karthik Kambatla ka...@cloudera.com wrote: Closing out the JIRAs as Auto Closed or Closed due to Inactivity seems reasonable to me. For branch-1, we can be more aggressive. We should probably do the same less aggressively for other branches too. On Fri, May 8, 2015 at 11:01 AM, Arun C Murthy acmur...@apache.org wrote: +1 Arun On May 8, 2015, at 10:41 AM, Allen Wittenauer a...@altiscale.com wrote: May we declare this branch dead and just close bugs (but not necessarily concepts, ideas, etc) with won’t fix? I don’t think anyone has any intention of working on the 1.3 release, especially given that 1.2.1 was Aug 2013 …. I guess we need a PMC member to declare a vote or whatever…. -- Karthik Kambatla Software Engineer, Cloudera Inc. http://five.sentenc.es
Re: [DISCUSS] branch-1
Closing out the JIRAs as Auto Closed or Closed due to Inactivity seems reasonable to me. For branch-1, we can be more aggressive. We should probably do the same less aggressively for other branches too. On Fri, May 8, 2015 at 11:01 AM, Arun C Murthy acmur...@apache.org wrote: +1 Arun On May 8, 2015, at 10:41 AM, Allen Wittenauer a...@altiscale.com wrote: May we declare this branch dead and just close bugs (but not necessarily concepts, ideas, etc) with won’t fix? I don’t think anyone has any intention of working on the 1.3 release, especially given that 1.2.1 was Aug 2013 …. I guess we need a PMC member to declare a vote or whatever…. -- Karthik Kambatla Software Engineer, Cloudera Inc. http://five.sentenc.es
Re: [DISCUSS] branch-1
+1 Arun On May 8, 2015, at 10:41 AM, Allen Wittenauer a...@altiscale.com wrote: May we declare this branch dead and just close bugs (but not necessarily concepts, ideas, etc) with won’t fix? I don’t think anyone has any intention of working on the 1.3 release, especially given that 1.2.1 was Aug 2013 …. I guess we need a PMC member to declare a vote or whatever….
[jira] [Created] (HADOOP-11940) TestTraceAdmin fails
Kihwal Lee created HADOOP-11940:
---
Summary: TestTraceAdmin fails
Key: HADOOP-11940
URL: https://issues.apache.org/jira/browse/HADOOP-11940
Project: Hadoop Common
Issue Type: Bug
Reporter: Kihwal Lee
After HADOOP-11912, {{TestTraceAdmin#testCreateAndDestroySpanReceiver}} in hdfs
started failing.
It was probably unnoticed because the jira changed and triggered unit testing
in common only.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Re: Jenkins precommit-*-build
Thank you Allen! --Konst On Tue, May 5, 2015 at 5:14 PM, Allen Wittenauer a...@altiscale.com wrote: HDFS, MAPREDUCE, and YARN have been migrated. Let me know of any issues and I’ll try to get to them as I can. This should be the end of the Jenkins race conditions for our pre commits! *crosses fingers*
[jira] [Resolved] (HADOOP-10492) Help Commands needs change after deprecation
[ https://issues.apache.org/jira/browse/HADOOP-10492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brahma Reddy Battula resolved HADOOP-10492. --- Resolution: Not A Problem Help Commands needs change after deprecation Key: HADOOP-10492 URL: https://issues.apache.org/jira/browse/HADOOP-10492 Project: Hadoop Common Issue Type: Bug Reporter: Raja Nagendra Kumar Attachments: HADOOP-10492.patch As hadoop dfs is deprecated, the help should show usage with HDFS e.g in the following command it still refers to Usage: hadoop fs [generic options] D:\Apps\java\BI\hadoop\hw\hdp\hadoop-2.2.0.2.0.6.0-0009hdfs dfs Usage: hadoop fs [generic options] [-appendToFile localsrc ... dst] [-cat [-ignoreCrc] src ...] [-checksum src ...] [-chgrp [-R] GROUP PATH...] [-chmod [-R] MODE[,MODE]... | OCTALMODE PATH...] [-chown [-R] [OWNER][:[GROUP]] PATH...] [-copyFromLocal [-f] [-p] localsrc ... dst] [-copyToLocal [-p] [-ignoreCrc] [-crc] src ... localdst] [-count [-q] path ...] [-cp [-f] [-p] src ... dst] [-createSnapshot snapshotDir [snapshotName]] [-deleteSnapshot snapshotDir snapshotName] [-df [-h] [path ...]] [-du [-s] [-h] path ...] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HADOOP-11944) add option to test-patch to avoid relocating patch process directory
Sean Busbey created HADOOP-11944: Summary: add option to test-patch to avoid relocating patch process directory Key: HADOOP-11944 URL: https://issues.apache.org/jira/browse/HADOOP-11944 Project: Hadoop Common Issue Type: Improvement Reporter: Sean Busbey Assignee: Sean Busbey Priority: Minor When we have a jenkins setup that places the patch process in a defined location under WORKPLACE, there's no need to have patch process relocate it. Add a flag to leave it as is. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: REMINDER! REGISTRATIONS CLOSING 5/6!
Thanks Allen a lot for organizing the Haoop Bug Bash, very happy to see many folks by face! Wish you all a nice weekend! --Yongjun On Tue, May 5, 2015 at 9:31 PM, Allen Wittenauer a...@altiscale.com wrote: On May 5, 2015, at 8:10 PM, Allen Wittenauer a...@altiscale.com wrote: * We’ll be closing registrations to the Bug Bash on May 6th at 3PM Pacific time. So make sure you do it son: https://www.eventbrite.com/e/apache-hadoop-global-bug-bash-tickets-16507188445 That should be *noon* Pacific time. So just do it already, ok? [I can’t tell time. Someone should buy me an Apple Watch Edition or something.]
[jira] [Resolved] (HADOOP-10363) Closing of SequenceFile.Reader / SequenceFile.Writer in DistCh should check against null
[
https://issues.apache.org/jira/browse/HADOOP-10363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Varun Saxena resolved HADOOP-10363.
---
Resolution: Not A Problem
Closing this. This issue no longer exists as DistCh now uses try with resources
construct. Feel free to reopen if you think otherwise
Closing of SequenceFile.Reader / SequenceFile.Writer in DistCh should check
against null
Key: HADOOP-10363
URL: https://issues.apache.org/jira/browse/HADOOP-10363
Project: Hadoop Common
Issue Type: Bug
Reporter: Ted Yu
Priority: Minor
Attachments: HADOOP-10363.patch
Here is related code:
{code}
try {
for(in = new SequenceFile.Reader(fs, srcs, job); in.next(key, value);
) {
...
finally {
in.close();
}
{code}
{code}
SequenceFile.Writer opWriter = null;
try {
opWriter = SequenceFile.createWriter(fs, jobconf, opList, Text.class,
FileOperation.class, SequenceFile.CompressionType.NONE);
...
} finally {
opWriter.close();
}
{code}
If ctor of Reader / Writer throws exception, the close() would be called on
null object.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HADOOP-11945) Add Apache Ignite (incubating) to the Hadoop-related projects
Konstantin Boudnik created HADOOP-11945: --- Summary: Add Apache Ignite (incubating) to the Hadoop-related projects Key: HADOOP-11945 URL: https://issues.apache.org/jira/browse/HADOOP-11945 Project: Hadoop Common Issue Type: Improvement Components: site Affects Versions: 2.5.2 Reporter: Konstantin Boudnik Assignee: Konstantin Boudnik Fix For: site Apache Ignite (incubating) has the implementation of HDFS compatible in-memory file system (IGFS) and in-memory MapReduce accelerator. These two components allow Ignite users to run OLTP/SQL/computational workloads on top of HDFS storage. Let's add this project to the list of Hadoop related ones. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
