hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Douglas (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-1466) FileInputFormat should save #input-files in JobConf
Date Fri, 05 Mar 2010 22:47:27 GMT

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

Chris Douglas commented on MAPREDUCE-1466:
------------------------------------------

Talked with Luke. Since {{INPUT_NUM_FILES}} is shared between both implementations of {{FileInputFormat}},
most config keys were moved to JobContext in MAPREDUCE-849 anyway, and config keys are undocumented
in our current regime: the current patch is correct.

+1

> FileInputFormat should save #input-files in JobConf
> ---------------------------------------------------
>
>                 Key: MAPREDUCE-1466
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1466
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: client
>    Affects Versions: 0.22.0
>            Reporter: Arun C Murthy
>            Assignee: Arun C Murthy
>            Priority: Minor
>             Fix For: 0.22.0
>
>         Attachments: MAPREDUCE-1466_yhadoop20-1.patch, MAPREDUCE-1466_yhadoop20-2.patch,
MAPREDUCE-1466_yhadoop20-3.patch, MAPREDUCE-1466_yhadoop20.patch, mr-1466-trunk-v1.patch
>
>
> We already track the amount of data consumed by MR applications (MAP_INPUT_BYTES), alongwith,
it would be useful to #input-files from the client-side for analysis. Along the lines of MAPREDUCE-1403,
it would be easy to stick in the JobConf during job-submission.

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