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

Hudson commented on SQOOP-1282:
-------------------------------

SUCCESS: Integrated in Sqoop-ant-jdk-1.6-hadoop23 #1079 (See 
[https://builds.apache.org/job/Sqoop-ant-jdk-1.6-hadoop23/1079/])
SQOOP-1282: Consider avro files even if they carry no extension (jarcec: 
https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=d37bd1168c81e72f71bbdb7eedcf643f366e5b26)
* src/test/com/cloudera/sqoop/TestAvroExport.java
* src/java/org/apache/sqoop/mapreduce/AvroInputFormat.java


> Consider avro files even if they carry no extension
> ---------------------------------------------------
>
>                 Key: SQOOP-1282
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1282
>             Project: Sqoop
>          Issue Type: Improvement
>    Affects Versions: 1.4.4
>            Reporter: Harsh J
>            Assignee: Harsh J
>            Priority: Minor
>             Fix For: 1.4.5
>
>         Attachments: SQOOP-1282.patch
>
>
> The Export jobs in Sqoop have a mechanism that checks file contents to 
> determine if its of Avro type or etc. regardless of extension, so it makes 
> less sense to then also go forward and silently ignore all files in the 
> export-dir that carry no .avro extension.
> Kinda similar to AVRO-1234, except we do not check for file validity in the 
> Avro project's input format or driver levels as we already do in Sqoop.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to