Re: Review Request 58466: SQOOP-3158 - Columns added to Mysql after initial sqoop import, export back to table with same schema fails

> On May 9, 2017, 3:09 p.m., Szabolcs Vasas wrote: > > src/java/org/apache/sqoop/orm/ClassWriter.java > > Lines 1416 (patched) > > > > > > I think the hard coded "null" value will not work if > > the user

Re: Review Request 58466: SQOOP-3158 - Columns added to Mysql after initial sqoop import, export back to table with same schema fails

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/58466/ --- (Updated May 21, 2017, 11:12 a.m.) Review request for Sqoop, Attila Szabo and

[jira] [Comment Edited] (SQOOP-3158) Columns added to Mysql after initial sqoop import, export back to table with same schema fails

[ https://issues.apache.org/jira/browse/SQOOP-3158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16018783#comment-16018783 ] Eric Lin edited comment on SQOOP-3158 at 5/21/17 11:10 AM: --- Latest patch based

[jira] [Updated] (SQOOP-3158) Columns added to Mysql after initial sqoop import, export back to table with same schema fails

[ https://issues.apache.org/jira/browse/SQOOP-3158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Lin updated SQOOP-3158: Attachment: SQOOP-3158.3.patch Latest patch based on review. > Columns added to Mysql after initial sqoop