hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amareshwari Sriramadasu (JIRA)" <j...@apache.org>
Subject [jira] Created: (HADOOP-4732) connectionTimeout and readTimeout are passed in wrong order in ReduceTask.java
Date Wed, 26 Nov 2008 11:12:44 GMT
 connectionTimeout and readTimeout are passed in wrong order in ReduceTask.java
-------------------------------------------------------------------------------

                 Key: HADOOP-4732
                 URL: https://issues.apache.org/jira/browse/HADOOP-4732
             Project: Hadoop Core
          Issue Type: Bug
          Components: mapred
            Reporter: Amareshwari Sriramadasu
            Assignee: Amareshwari Sriramadasu
            Priority: Minor
             Fix For: 0.20.0


In ReduceTask.java, The parameters for method calls for getInputStream(URLConnection connection,
 int connectionTimeout,  int readTimeout) should be in that order. Now it is
{code}
        InputStream input = getInputStream(connection, DEFAULT_READ_TIMEOUT, 
                                           STALLED_COPY_TIMEOUT);
{code}
It works now because both DEFAULT_READ_TIMEOUT and STALLED_COPY_TIMEOUT have the same value.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message