[
https://issues.apache.org/jira/browse/SQOOP-2907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16118505#comment-16118505
]
Anna Szonyi edited comment on SQOOP-2907 at 8/8/17 3:52 PM:
------------------------------------------------------------
Hi [[email protected]],
Thanks for picking this up again! Please make sure that it applies to the
current trunk (or if needed please rebase on it), also we should ping
[~yuan_zac] and [~chenkai.dr] in case the original author wants to reclaim
their patch. If not (or we receive no reply), then please submit it for review!
Thanks,
Anna
was (Author: anna.szonyi):
Hi [[email protected]],
Thanks for picking this up again! Please make sure that it applies to the
current trunk (or if needed please rebase on it), also we should ping
[~yuan_zac] in case the original author wants to reclaim their patch. If not
(or we receive no reply), then please submit it 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)
