[
https://issues.apache.org/jira/browse/AVRO-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13581524#comment-13581524
]
Harsh J commented on AVRO-1234:
-------------------------------
This also would come handy in Flume areas, where the files are prepared
suffix-less sometimes. Painful to rename them in bulk before a job is to be run
with factory classes of avro-mapred.
Would a configurable patch for 1.7 be OK to go in as well, such that default
behavior is preserved but carries a toggle as well, for those who search and
discover?
> 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
> Fix For: 1.8.0
>
> 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
