[
https://issues.apache.org/jira/browse/SQOOP-2907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15784701#comment-15784701
]
Zac Zhou edited comment on SQOOP-2907 at 12/29/16 7:06 AM:
-----------------------------------------------------------
SQOOP-2907.patch1 keep using kite to handle parquet file. But it would get the
schema from parquet file directly if there is no .metastore folder. this way
works for parquet files generated by hive and spark. some unit tests are added
as well
was (Author: yuan_zac):
get schema data from parquet file directly
> 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
> 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.3.4#6332)
