[jira] [Commented] (SQOOP-2907) Export parquet files to RDBMS: don't require .metadata for parquet files

[Sandish Kumar HN (JIRA)]

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

Sandish Kumar HN commented on SQOOP-2907:
-

[~514793...@qq.com] gave me permission to submit. 

> 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)

Re: New Sqoop Committer - Boglarka Egyed

[Anna Szonyi]

Congrats Bogi!! :)

On Tue, Aug 8, 2017 at 8:37 PM, Mark Kemper  wrote:

> Congrats Bogi
>
>
> Markus Kemper
> Customer Operations Engineer
> [image: www.cloudera.com] 
>
>
> On Tue, Aug 8, 2017 at 2:30 PM, Abraham Fine  wrote:
>
> > On behalf of the Apache Sqoop PMC, I am pleased to welcome Boglarka Eyed
> > as a new committer to Apache Sqoop. Please join me in congratulating her
> > for this accomplishment!
> >
> > Bogi has made a number of contributions to Sqoop particularly as it
> > relates to testing (especially Sqoop's 3rd party tests). In addition
> > Boglarka has performed many code reviews for the community. Boglarka's
> > reviews have been critical in our effort to maintain high quality code
> > and grow the community.
> >
> > Here is the JIRA listing of her contributions: https://s.apache.org/ruWN
> >
> > We are excited too see what Bogi contributes next!
> >
> > Thanks,
> > Abraham Fine
> >
>

Re: New Sqoop Committer - Boglarka Egyed

[Mark Kemper]

Congrats Bogi


Markus Kemper
Customer Operations Engineer
[image: www.cloudera.com] 


On Tue, Aug 8, 2017 at 2:30 PM, Abraham Fine  wrote:

> On behalf of the Apache Sqoop PMC, I am pleased to welcome Boglarka Eyed
> as a new committer to Apache Sqoop. Please join me in congratulating her
> for this accomplishment!
>
> Bogi has made a number of contributions to Sqoop particularly as it
> relates to testing (especially Sqoop's 3rd party tests). In addition
> Boglarka has performed many code reviews for the community. Boglarka's
> reviews have been critical in our effort to maintain high quality code
> and grow the community.
>
> Here is the JIRA listing of her contributions: https://s.apache.org/ruWN
>
> We are excited too see what Bogi contributes next!
>
> Thanks,
> Abraham Fine
>

New Sqoop Committer - Boglarka Egyed

[Abraham Fine]

On behalf of the Apache Sqoop PMC, I am pleased to welcome Boglarka Eyed
as a new committer to Apache Sqoop. Please join me in congratulating her
for this accomplishment!

Bogi has made a number of contributions to Sqoop particularly as it
relates to testing (especially Sqoop's 3rd party tests). In addition
Boglarka has performed many code reviews for the community. Boglarka's
reviews have been critical in our effort to maintain high quality code
and grow the community. 

Here is the JIRA listing of her contributions: https://s.apache.org/ruWN

We are excited too see what Bogi contributes next! 

Thanks,
Abraham Fine

[jira] [Comment Edited] (SQOOP-2907) Export parquet files to RDBMS: don't require .metadata for parquet files

[Anna Szonyi (JIRA)]

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

Anna Szonyi edited comment on SQOOP-2907 at 8/8/17 3:53 PM:


Hi [~sanysand...@gmail.com],

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 [~514793...@qq.com]] 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 [~sanysand...@gmail.com],

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

> 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)

[jira] [Comment Edited] (SQOOP-2907) Export parquet files to RDBMS: don't require .metadata for parquet files

[Anna Szonyi (JIRA)]

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

Anna Szonyi edited comment on SQOOP-2907 at 8/8/17 3:52 PM:


Hi [~sanysand...@gmail.com],

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 [~sanysand...@gmail.com],

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)

[jira] [Commented] (SQOOP-2907) Export parquet files to RDBMS: don't require .metadata for parquet files

[Anna Szonyi (JIRA)]

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

Anna Szonyi commented on SQOOP-2907:


Hi [~sanysand...@gmail.com],

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)

[jira] [Comment Edited] (SQOOP-2907) Export parquet files to RDBMS: don't require .metadata for parquet files

[Sandish Kumar HN (JIRA)]

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

Sandish Kumar HN edited comment on SQOOP-2907 at 8/8/17 11:52 AM:
--

Hi [~anna.szonyi] 

It seems issue there from a long time.
The attached SQOOP-2907.patch1 works fine with small inline change at AvroUtil. 
 can I submit the patch at review board?? 


was (Author: sanysand...@gmail.com):
[~anna.szonyi] 

It seems issue there from a long time.
The attached SQOOP-2907.patch1 works fine with small inline change at AvroUtil. 
 can I submit the patch at review board?? 

> 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)

[jira] [Commented] (SQOOP-2907) Export parquet files to RDBMS: don't require .metadata for parquet files

[Sandish Kumar HN (JIRA)]

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

Sandish Kumar HN commented on SQOOP-2907:
-

[~anna.szonyi] 

It seems issue there from a long time.
The attached SQOOP-2907.patch1 works fine with small inline change at AvroUtil. 
 can I submit the patch at review board?? 

> 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)