[jira] [Updated] (MAPREDUCE-6286) A typo in HistoryViewer makes some code useless, which causes counter limits are not reset correctly.

2017-07-31 Thread Junping Du (JIRA) 

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

Junping Du updated MAPREDUCE-6286:
--
Fix Version/s: (was: 3.0.0-alpha1)
   (was: 2.9.0)

> A typo in HistoryViewer makes some code useless, which causes counter limits 
> are not reset correctly.
> -
>
> Key: MAPREDUCE-6286
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6286
> Project: Hadoop Map/Reduce
>  Issue Type: Bug
>  Components: client
>Affects Versions: 2.6.0
>Reporter: zhihai xu
>Assignee: zhihai xu
> Attachments: MAPREDUCE-6286.000.patch
>
>
> A typo in HistoryViewer makes some code useless and it causes counter limits 
> are not reset correctly.
> The typo is
> Limits.reset(conf);
> We should use jobConf instead of conf.
> With the typo, the following code becomes useless:
> {code}
>   final Path jobConfPath = new Path(jobFile.getParent(),  jobDetails[0]
>   + "_" + jobDetails[1] + "_" + jobDetails[2] + "_conf.xml");
>   final Configuration jobConf = new Configuration(conf);
> jobConf.addResource(fs.open(jobConfPath), jobConfPath.toString());
> {code}
> The code wants to load the configuration from the Job configuration file and 
> reset the Limits based on the new configuration loaded from the Job 
> configuration file. But with the typo, the Limits are reset with the old 
> configuration.
> So this typo is apparent.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

-
To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org

[jira] [Updated] (MAPREDUCE-6286) A typo in HistoryViewer makes some code useless, which causes counter limits are not reset correctly.

2016-12-28 Thread Junping Du (JIRA) 

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

Junping Du updated MAPREDUCE-6286:
--
Fix Version/s: (was: 2.8.0)
   2.9.0

> A typo in HistoryViewer makes some code useless, which causes counter limits 
> are not reset correctly.
> -
>
> Key: MAPREDUCE-6286
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6286
> Project: Hadoop Map/Reduce
>  Issue Type: Bug
>  Components: client
>Affects Versions: 2.6.0
>Reporter: zhihai xu
>Assignee: zhihai xu
> Fix For: 2.9.0, 3.0.0-alpha1
>
> Attachments: MAPREDUCE-6286.000.patch
>
>
> A typo in HistoryViewer makes some code useless and it causes counter limits 
> are not reset correctly.
> The typo is
> Limits.reset(conf);
> We should use jobConf instead of conf.
> With the typo, the following code becomes useless:
> {code}
>   final Path jobConfPath = new Path(jobFile.getParent(),  jobDetails[0]
>   + "_" + jobDetails[1] + "_" + jobDetails[2] + "_conf.xml");
>   final Configuration jobConf = new Configuration(conf);
> jobConf.addResource(fs.open(jobConfPath), jobConfPath.toString());
> {code}
> The code wants to load the configuration from the Job configuration file and 
> reset the Limits based on the new configuration loaded from the Job 
> configuration file. But with the typo, the Limits are reset with the old 
> configuration.
> So this typo is apparent.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org

[jira] [Updated] (MAPREDUCE-6286) A typo in HistoryViewer makes some code useless, which causes counter limits are not reset correctly.

2015-03-31 Thread Vinod Kumar Vavilapalli (JIRA) 

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

Vinod Kumar Vavilapalli updated MAPREDUCE-6286:
---
Fix Version/s: (was: 2.7.0)
   2.8.0

Removed this from 2.7.0. See the discussion on 
[MAPREDUCE-6288|https://issues.apache.org/jira/browse/MAPREDUCE-6288?focusedCommentId=14387563page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14387563].

 A typo in HistoryViewer makes some code useless, which causes counter limits 
 are not reset correctly.
 -

 Key: MAPREDUCE-6286
 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6286
 Project: Hadoop Map/Reduce
  Issue Type: Bug
  Components: client
Affects Versions: 2.6.0
Reporter: zhihai xu
Assignee: zhihai xu
 Fix For: 2.8.0

 Attachments: MAPREDUCE-6286.000.patch


 A typo in HistoryViewer makes some code useless and it causes counter limits 
 are not reset correctly.
 The typo is
 Limits.reset(conf);
 We should use jobConf instead of conf.
 With the typo, the following code becomes useless:
 {code}
   final Path jobConfPath = new Path(jobFile.getParent(),  jobDetails[0]
   + _ + jobDetails[1] + _ + jobDetails[2] + _conf.xml);
   final Configuration jobConf = new Configuration(conf);
 jobConf.addResource(fs.open(jobConfPath), jobConfPath.toString());
 {code}
 The code wants to load the configuration from the Job configuration file and 
 reset the Limits based on the new configuration loaded from the Job 
 configuration file. But with the typo, the Limits are reset with the old 
 configuration.
 So this typo is apparent.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MAPREDUCE-6286) A typo in HistoryViewer makes some code useless, which causes counter limits are not reset correctly.

2015-03-21 Thread zhihai xu (JIRA) 

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

zhihai xu updated MAPREDUCE-6286:
-
Description: 
A typo in HistoryViewer makes some code useless and it causes counter limits 
are not reset correctly.
The typo is
Limits.reset(conf);
We should use jobConf instead of conf.
With the typo, the following code becomes useless:
{code}
  final Path jobConfPath = new Path(jobFile.getParent(),  jobDetails[0]
  + _ + jobDetails[1] + _ + jobDetails[2] + _conf.xml);
  final Configuration jobConf = new Configuration(conf);
jobConf.addResource(fs.open(jobConfPath), jobConfPath.toString());
{code}
The code wants to load the configuration from the Job configuration file and 
reset the Limits based on the new configuration loaded from the Job 
configuration file. But with the typo, the Limits are reset with the old 
configuration.
So this typo is apparent.

  was:
A typo in HistoryViewer makes some code useless.
The typo is
Limits.reset(conf);
We should use jobConf instead of conf.
With the typo, the following code becomes useless:
{code}
  final Path jobConfPath = new Path(jobFile.getParent(),  jobDetails[0]
  + _ + jobDetails[1] + _ + jobDetails[2] + _conf.xml);
  final Configuration jobConf = new Configuration(conf);
jobConf.addResource(fs.open(jobConfPath), jobConfPath.toString());
{code}
The code wants to load the configuration from the Job configuration file and 
reset the Limits based on the new configuration loaded from the Job 
configuration file. But with the typo, the Limits are reset with the old 
configuration.
So this typo is apparent.

Summary: A typo in HistoryViewer makes some code useless, which causes 
counter limits are not reset correctly.  (was: A typo in HistoryViewer makes 
some code useless.)

 A typo in HistoryViewer makes some code useless, which causes counter limits 
 are not reset correctly.
 -

 Key: MAPREDUCE-6286
 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6286
 Project: Hadoop Map/Reduce
  Issue Type: Bug
  Components: client
Reporter: zhihai xu
Assignee: zhihai xu
 Attachments: MAPREDUCE-6286.000.patch


 A typo in HistoryViewer makes some code useless and it causes counter limits 
 are not reset correctly.
 The typo is
 Limits.reset(conf);
 We should use jobConf instead of conf.
 With the typo, the following code becomes useless:
 {code}
   final Path jobConfPath = new Path(jobFile.getParent(),  jobDetails[0]
   + _ + jobDetails[1] + _ + jobDetails[2] + _conf.xml);
   final Configuration jobConf = new Configuration(conf);
 jobConf.addResource(fs.open(jobConfPath), jobConfPath.toString());
 {code}
 The code wants to load the configuration from the Job configuration file and 
 reset the Limits based on the new configuration loaded from the Job 
 configuration file. But with the typo, the Limits are reset with the old 
 configuration.
 So this typo is apparent.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MAPREDUCE-6286) A typo in HistoryViewer makes some code useless, which causes counter limits are not reset correctly.

2015-03-21 Thread Harsh J (JIRA) 

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

Harsh J updated MAPREDUCE-6286:
---
   Resolution: Fixed
Fix Version/s: 2.8.0
 Hadoop Flags: Reviewed
   Status: Resolved  (was: Patch Available)

 A typo in HistoryViewer makes some code useless, which causes counter limits 
 are not reset correctly.
 -

 Key: MAPREDUCE-6286
 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6286
 Project: Hadoop Map/Reduce
  Issue Type: Bug
  Components: client
Affects Versions: 2.6.0
Reporter: zhihai xu
Assignee: zhihai xu
 Fix For: 2.8.0

 Attachments: MAPREDUCE-6286.000.patch


 A typo in HistoryViewer makes some code useless and it causes counter limits 
 are not reset correctly.
 The typo is
 Limits.reset(conf);
 We should use jobConf instead of conf.
 With the typo, the following code becomes useless:
 {code}
   final Path jobConfPath = new Path(jobFile.getParent(),  jobDetails[0]
   + _ + jobDetails[1] + _ + jobDetails[2] + _conf.xml);
   final Configuration jobConf = new Configuration(conf);
 jobConf.addResource(fs.open(jobConfPath), jobConfPath.toString());
 {code}
 The code wants to load the configuration from the Job configuration file and 
 reset the Limits based on the new configuration loaded from the Job 
 configuration file. But with the typo, the Limits are reset with the old 
 configuration.
 So this typo is apparent.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MAPREDUCE-6286) A typo in HistoryViewer makes some code useless, which causes counter limits are not reset correctly.

2015-03-21 Thread Harsh J (JIRA) 

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

Harsh J updated MAPREDUCE-6286:
---
Affects Version/s: 2.6.0

 A typo in HistoryViewer makes some code useless, which causes counter limits 
 are not reset correctly.
 -

 Key: MAPREDUCE-6286
 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6286
 Project: Hadoop Map/Reduce
  Issue Type: Bug
  Components: client
Affects Versions: 2.6.0
Reporter: zhihai xu
Assignee: zhihai xu
 Fix For: 2.8.0

 Attachments: MAPREDUCE-6286.000.patch


 A typo in HistoryViewer makes some code useless and it causes counter limits 
 are not reset correctly.
 The typo is
 Limits.reset(conf);
 We should use jobConf instead of conf.
 With the typo, the following code becomes useless:
 {code}
   final Path jobConfPath = new Path(jobFile.getParent(),  jobDetails[0]
   + _ + jobDetails[1] + _ + jobDetails[2] + _conf.xml);
   final Configuration jobConf = new Configuration(conf);
 jobConf.addResource(fs.open(jobConfPath), jobConfPath.toString());
 {code}
 The code wants to load the configuration from the Job configuration file and 
 reset the Limits based on the new configuration loaded from the Job 
 configuration file. But with the typo, the Limits are reset with the old 
 configuration.
 So this typo is apparent.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (MAPREDUCE-6286) A typo in HistoryViewer makes some code useless, which causes counter limits are not reset correctly.

2015-03-21 Thread Harsh J (JIRA) 

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

Harsh J updated MAPREDUCE-6286:
---
Fix Version/s: (was: 2.8.0)
   2.7.0

 A typo in HistoryViewer makes some code useless, which causes counter limits 
 are not reset correctly.
 -

 Key: MAPREDUCE-6286
 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6286
 Project: Hadoop Map/Reduce
  Issue Type: Bug
  Components: client
Affects Versions: 2.6.0
Reporter: zhihai xu
Assignee: zhihai xu
 Fix For: 2.7.0

 Attachments: MAPREDUCE-6286.000.patch


 A typo in HistoryViewer makes some code useless and it causes counter limits 
 are not reset correctly.
 The typo is
 Limits.reset(conf);
 We should use jobConf instead of conf.
 With the typo, the following code becomes useless:
 {code}
   final Path jobConfPath = new Path(jobFile.getParent(),  jobDetails[0]
   + _ + jobDetails[1] + _ + jobDetails[2] + _conf.xml);
   final Configuration jobConf = new Configuration(conf);
 jobConf.addResource(fs.open(jobConfPath), jobConfPath.toString());
 {code}
 The code wants to load the configuration from the Job configuration file and 
 reset the Limits based on the new configuration loaded from the Job 
 configuration file. But with the typo, the Limits are reset with the old 
 configuration.
 So this typo is apparent.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)