[jira] [Resolved] (HADOOP-1922) The task output promotion exception handler should include the IOException in the diagnostic message

2011-07-17 Thread Harsh J (JIRA)

 [ 
https://issues.apache.org/jira/browse/HADOOP-1922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Harsh J resolved HADOOP-1922.
-

Resolution: Fixed

This is now taken care of by OutputCommitter framework.

Although, at the time this was opened around, it was addressed by refactors at 
HADOOP-1874

 The task output promotion exception handler should include the IOException in 
 the diagnostic message
 

 Key: HADOOP-1922
 URL: https://issues.apache.org/jira/browse/HADOOP-1922
 Project: Hadoop Common
  Issue Type: Bug
Reporter: Owen O'Malley
Assignee: Devaraj Das

 When the JobTracker fails to promote output, it should have a more detailed 
 error message that includes the exception that was thrown by the FileSystem 
 operation.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Resolved] (HADOOP-1769) Possible StackOverflowError in FileSystem.get(Uri uri, Configuration conf) method

2011-07-17 Thread Harsh J (JIRA)

 [ 
https://issues.apache.org/jira/browse/HADOOP-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Harsh J resolved HADOOP-1769.
-

Resolution: Cannot Reproduce

Doesn't look like its a problem anymore.

Here's a simple test to guarantee (there may already exist something like this, 
but I did not look)

{code}

  public void testStack() throws IOException, URISyntaxException {
Configuration conf = new Configuration();
String url = /;
URI uri = new URI(url);
assertEquals(null, uri.getScheme());
FileSystem fs = FileSystem.get(uri, conf);
  }

{code}

Marking as 'Cannot Reproduce' (now).

 Possible StackOverflowError in FileSystem.get(Uri uri, Configuration conf) 
 method
 -

 Key: HADOOP-1769
 URL: https://issues.apache.org/jira/browse/HADOOP-1769
 Project: Hadoop Common
  Issue Type: Bug
  Components: fs
Affects Versions: 0.14.0
Reporter: Thomas Friol

 When calling the method Filesytem.get(Uri uri, Configuration conf) with an 
 URI without scheme - StackOverflowError
 {noformat}
 Exception in thread Main Thread java.lang.StackOverflowError:
 at java.util.regex.Matcher.init(Matcher.java:201)
 at java.util.regex.Pattern.matcher(Pattern.java:879)
 at 
 org.apache.hadoop.conf.Configuration.substituteVars(Configuration.java:182)
 at org.apache.hadoop.conf.Configuration.get(Configuration.java:247)
 at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:90)
 at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:143)
 at org.apache.hadoop.fs.FileSystem.getNamed(FileSystem.java:118)
 at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:90)
 at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:143)
 at org.apache.hadoop.fs.FileSystem.getNamed(FileSystem.java:118)
 at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:90)
 at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:143)
 at org.apache.hadoop.fs.FileSystem.getNamed(FileSystem.java:118)
 at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:90)
 at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:143)
 at org.apache.hadoop.fs.FileSystem.getNamed(FileSystem.java:118)
 at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:90)
 at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:143)
 at org.apache.hadoop.fs.FileSystem.getNamed(FileSystem.java:118)
 at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:90)
 at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:143)
 at org.apache.hadoop.fs.FileSystem.getNamed(FileSystem.java:118)
 at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:90)
 at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:143)
 at org.apache.hadoop.fs.FileSystem.getNamed(FileSystem.java:118)
 at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:90)
 at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:143)
 {noformat}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Resolved] (HADOOP-2221) Configuration.toString is broken

2011-07-17 Thread Harsh J (JIRA)

 [ 
https://issues.apache.org/jira/browse/HADOOP-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Harsh J resolved HADOOP-2221.
-

Resolution: Not A Problem

Nicholas - Yep, looks invalid given current state (0.23/trunk) of 
Configuration. Resources and Default Resources are now loaded during toString 
ops.

{code}
  @Override
  public String toString() {
StringBuilder sb = new StringBuilder();
sb.append(Configuration: );
if(loadDefaults) {
  toString(defaultResources, sb);
  if(resources.size()0) {
sb.append(, );
  }
}
toString(resources, sb);
return sb.toString();
  }
{code}

Closing as Not-a-problem (anymore).

 Configuration.toString is broken
 

 Key: HADOOP-2221
 URL: https://issues.apache.org/jira/browse/HADOOP-2221
 Project: Hadoop Common
  Issue Type: Bug
  Components: conf
Affects Versions: 0.15.0
Reporter: Arun C Murthy
Assignee: Arun C Murthy
 Attachments: HADOOP-2221_1_2007117.patch


 {{Configuration.toString}} doesn't string-ify the {{Configuration.resources}} 
 field which was added in HADOOP-785.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira