sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zac Zhou (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SQOOP-2907) Export parquet files to RDBMS: don't require .metadata for parquet files
Date Wed, 09 Aug 2017 09:56:01 GMT

     [ https://issues.apache.org/jira/browse/SQOOP-2907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Zac Zhou updated SQOOP-2907:
----------------------------
    Attachment: SQOOP-2907.patch2

SQOOP-2907.patch2 is attached, which is compatible with sqoop-trunk

> 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, SQOOP-2907.patch2
>
>
> 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)

Mime
View raw message