You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Ruslan Dautkhanov (JIRA)" <ji...@apache.org> on 2016/04/12 07:24:25 UTC
[jira] [Commented] (SQOOP-2907) Export parquet files to RDBMS:
don't require .metadata for parquet files
[ https://issues.apache.org/jira/browse/SQOOP-2907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15236616#comment-15236616 ]
Ruslan Dautkhanov commented on SQOOP-2907:
------------------------------------------
https://issues.cloudera.org/browse/KITE-1121 "Don't require .metadata for Parquet files"
> 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
>
> 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)