hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harsh J (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-2584) Check for serializers early, and give out more information regarding missing serializers
Date Sun, 07 Oct 2012 13:18:03 GMT

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

Harsh J updated MAPREDUCE-2584:

    Attachment: MAPREDUCE-2584.r7.diff

Rebased yet again. Part of this patch's changes on the common side were already committed,
so am inclined to commit this in as well.

But I'd like to know if there are any concerns with this new front-end check. Anyone? Is throwing
an exception bad if there's a ClassNotFound? Should we just WARN?
> Check for serializers early, and give out more information regarding missing serializers
> ----------------------------------------------------------------------------------------
>                 Key: MAPREDUCE-2584
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2584
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: task
>    Affects Versions: 0.20.2
>            Reporter: Harsh J
>            Assignee: Harsh J
>              Labels: serializers, tasks
>         Attachments: MAPREDUCE-2584.r2.diff, MAPREDUCE-2584.r3.diff, MAPREDUCE-2584.r4.diff,
MAPREDUCE-2584.r5.diff, MAPREDUCE-2584.r6.diff, MAPREDUCE-2584.r7.diff, MAPREDUCE-2584.r7.diff
> As discussed on HADOOP-7328, MapReduce can handle serializers in a much better way in
case of bad configuration, improper imports (Some odd Text class instead of the Writable Text
set as key), etc..
> This issue covers the MapReduce parts of the improvements (made to IFile, MapOutputBuffer,
etc. and possible early-check of serializer availability pre-submit) that provide more information
than just an NPE as is the current case.

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

View raw message