incubator-crunch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Wills (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CRUNCH-146) Jobs given Avro input data without '.avro' extension succeed, but do nothing
Date Thu, 17 Jan 2013 11:22:12 GMT

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

Josh Wills commented on CRUNCH-146:
-----------------------------------

I'm fine with ditching the extension check altogether-- running this one through integration
tests now.
                
> Jobs given Avro input data without '.avro' extension succeed, but do nothing
> ----------------------------------------------------------------------------
>
>                 Key: CRUNCH-146
>                 URL: https://issues.apache.org/jira/browse/CRUNCH-146
>             Project: Crunch
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.4.0
>            Reporter: Dave Beech
>            Assignee: Josh Wills
>         Attachments: CRUNCH-146-errorcheck.patch, CRUNCH-146.patch
>
>
> The Crunch AvroInputFormat class explicitly checks each input path for a '.avro' extension.

> If none of the input paths have such an extension, the job continues and succeeds even
though no map tasks get allocated, and none of the pipeline stages are executed. 
> ( I notice this behaviour is taken from Avro's own input format. It does happen in standard
Avro mapreduce too therefore, but only in the old mapred API - the new mapreduce API version
will happily read files regardless of extension. I'm going to report this as a bug on Avro
as well...)

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

Mime
View raw message