You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Jason Lowe (JIRA)" <ji...@apache.org> on 2013/01/08 20:58:13 UTC

[jira] [Commented] (MAPREDUCE-4926) Change documentation to use mapreduce.jobtracker.split.metainfo.maxsize

    [ https://issues.apache.org/jira/browse/MAPREDUCE-4926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13547190#comment-13547190 ] 

Jason Lowe commented on MAPREDUCE-4926:
---------------------------------------

Note that I am in the process of changing the code to use mapreduce.job.split.metainfo.maxsize and deprecate mapreduce.jobtracker.split.metainfo.maxsize, see MAPREDUCE-4871.
                
> Change documentation to use mapreduce.jobtracker.split.metainfo.maxsize
> -----------------------------------------------------------------------
>
>                 Key: MAPREDUCE-4926
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4926
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: documentation
>    Affects Versions: 2.0.2-alpha
>            Reporter: Lohit Vijayarenu
>            Priority: Minor
>
> Current 2.0 documentation points to mapreduce.job.split.metainfo.maxsize for restricting max size for job splits, while the code refers to mapreduce.jobtracker.split.metainfo.maxsize

--
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