[ https://issues.apache.org/jira/browse/HADOOP-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518871 ]
Owen O'Malley commented on HADOOP-1668: --------------------------------------- HADOOP-1197 API - deprecated method for Configuration.getObject, because Configrations should only contain strings HADOOP-1343 API - deprecate Configuration.set(String,Object) so that only strings are put in Configrations HADOOP-1344 API - Add RunningJob.getJobName() to get the name of the job. HADOOP-1336 Config - Enable speculative execution by default. HADOOP-1207 CLI - Fix FsShell to not stop 'rm' command when a file does not exist HADOOP-1484 webui - Allow killing jobs from webui. Disabled by default. HADOOP-1473 CLI/API - Job/TIP/Task ids now unique across job tracker restarts. > add INCOMPATIBLE CHANGES section to CHANGES.txt for Hadoop 0.14 > --------------------------------------------------------------- > > Key: HADOOP-1668 > URL: https://issues.apache.org/jira/browse/HADOOP-1668 > Project: Hadoop > Issue Type: Bug > Components: documentation > Affects Versions: 0.14.0 > Reporter: Nigel Daley > Assignee: Nigel Daley > Priority: Blocker > Fix For: 0.14.0 > > > HADOOP-1134 and some other Jira's have introduced incompatible changes into > Hadoop 0.14. As per HADOOP-1667 the CHANGES.txt file will include sections > for these kind of changes for Hadoop 0.15 and beyond. As a stop gap for > 0.14, the CHANGES.txt file needs an INCOMPATIBLE CHANGES section. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.