You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-dev@hadoop.apache.org by "Harsh J (JIRA)" <ji...@apache.org> on 2012/09/28 15:51:07 UTC

[jira] [Created] (MAPREDUCE-4692) Investigate and remove MR1 JTConfig and its constants use in the MR project on trunk

Harsh J created MAPREDUCE-4692:
----------------------------------

             Summary: Investigate and remove MR1 JTConfig and its constants use in the MR project on trunk
                 Key: MAPREDUCE-4692
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4692
             Project: Hadoop Map/Reduce
          Issue Type: Bug
          Components: client
            Reporter: Harsh J
            Priority: Minor


Filed on behalf of Robert from MAPREDUCE-3223

{code}
Are there any JIRAs to deprecate the configs from where they reside in the code? ./hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/server/jobtracker/JTConfig.java for example. I know we cannot delete them out just yet, because MRV1 code still exists and may be using it, but it would be good to mark all of those configs as deprecated. So that we can delete them in trunk once the MRV1 code is completely removed.
{code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira