sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Mazak" <pmazak2...@yahoo.com>
Subject Re: Review Request 34104: Fix for SQOOP-1369 Avro export ignores --columns option
Date Tue, 07 Jul 2015 20:03:55 GMT

This is an automatically generated e-mail. To reply, visit:

(Updated July 7, 2015, 8:03 p.m.)

Review request for Sqoop and Yibing Shi.


Addressed code review comments to remove empty import line and check specifiedColumns == null
|| specifiedColumns.contains()
Added JdbcExportJobTest

Repository: sqoop-trunk


Supplied a patch that worked for us. 
There are 2 global places to consider - parent class SqlManager and child class CatalogQueryManager
- when returning getColumnNames to actually rely on those column names you specified with
--columns option. 
There was 1 place to consider for Avro/Parquet in JdbcExportJob.configureGenericRecordExportInputFormat()
to only add the columnType if it's one that was specified with --columns option.

Diffs (updated)

  src/java/org/apache/sqoop/manager/CatalogQueryManager.java 4e063ed 
  src/java/org/apache/sqoop/manager/OracleManager.java 69b613f 
  src/java/org/apache/sqoop/manager/SqlManager.java ead581d 
  src/java/org/apache/sqoop/mapreduce/JdbcExportJob.java 93d438a 
  src/test/org/apache/sqoop/manager/SqlManagerTest.java PRE-CREATION 
  src/test/org/apache/sqoop/mapreduce/JdbcExportJobTest.java PRE-CREATION 

Diff: https://reviews.apache.org/r/34104/diff/


Integration testing passed exporting AVRO to MS SQL Server


Paul Mazak

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message