Sandish Kumar HN commented on SQOOP-2907:

Hi [~yuan_zac]
To get your change committed please do the following:
Create a review request at Apache's review board for project Sqoop and link it 
to this JIRA ticket: https://reviews.apache.org/
Please consider the guidelines below:
Review board
Summary: generate your summary using the issue's jira key + jira title
Groups: add the relevant group so everyone on the project will know about your 
patch (Sqoop)
Bugs: add the issue's jira key so it's easy to navigate to the jira side
Repository: sqoop-trunk for Sqoop1 or sqoop-sqoop2 for Sqoop2
And as soon as the patch gets committed, it's very useful for the community if 
you close the review and mark it as "Submitted" at the Review board. The button 
to do this is top right at your own tickets, right next to the Download Diff 
Link: please add the link of the review as an external/web link so it's easy to 
navigate to the reviews side
Status: mark it as "patch available"
Sqoop community will receive emails about your new ticket and review request 
and will review your change.

> 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

Reply via email to