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

Anna Szonyi commented on SQOOP-2907:
------------------------------------

Hi [~yuan_zac],

Thanks for the original patch and the green light! :)

[~sanysand...@gmail.com],

Thank you for the great description of the contribution process! The only minor 
side note is the naming convention we have: it's 
SQOOP-(JIRANr)-(patchrevision).patch (meaning that if you have changed the 
patch 3 times due to a review it would be SQOOP-2907-3.patch).

Please go ahead and submit the rebased patch for review!

Thanks,
Anna

> Export parquet files to RDBMS: don't require .metadata for parquet files
> ------------------------------------------------------------------------
>
>                 Key: SQOOP-2907
>                 URL: https://issues.apache.org/jira/browse/SQOOP-2907
>             Project: Sqoop
>          Issue Type: Improvement
>          Components: metastore
>    Affects Versions: 1.4.6
>         Environment: sqoop 1.4.6
> export parquet files to Oracle
>            Reporter: Ruslan Dautkhanov
>            Assignee: Sandish Kumar HN
>         Attachments: SQOOP-2907.patch, SQOOP-2907.patch1
>
>
> Kite currently requires .metadata.
> Parquet files have their own metadata stored along data files.
> It would be great for Export operation on parquet files to RDBMS not to 
> require .metadata.
> We have most of the files created by Spark and Hive, and they don't create 
> .metadata, it only Kite that does.
> It makes sqoop export of parquet files usability very limited.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to