[
https://issues.apache.org/jira/browse/AVRO-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13556519#comment-13556519
]
Harsh J commented on AVRO-1234:
-------------------------------
The check helps [helped?] avoid pulling in files of other types in the input
directory. Note that the new API was added _after_ the old API, and hence this
may have as well been a regression in the former?
If the intention of the input format is to only pick up files it can process,
than failing the job with some failed tasks afterwards, then an extension or
magic-bytes check is good to have.
> Avro MapReduce jobs silently ignore input data without '.avro' extension
> ------------------------------------------------------------------------
>
> Key: AVRO-1234
> URL: https://issues.apache.org/jira/browse/AVRO-1234
> Project: Avro
> Issue Type: Bug
> Affects Versions: 1.7.3
> Reporter: Dave Beech
> Assignee: Dave Beech
> Attachments: AVRO-1234.patch
>
>
> The AvroInputFormat class explicitly checks each input path for a '.avro'
> extension.
> If only some of the input paths have the correct extension, the remainder are
> silently ignored and not included in the job. However, if none of the input
> paths have the extension, the job will continue and succeed even though no
> map tasks are allocated, and no work is done.
> This only happens using the old mapred API. The new mapreduce API version
> will happily read files regardless of extension.
> Is the check necessary?
--
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
