[
https://issues.apache.org/jira/browse/SQOOP-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Jarcec Cecho updated SQOOP-409:
-------------------------------------
Fix Version/s: 1.4.1-incubating
Assignee: Jarek Jarcec Cecho
Status: Patch Available (was: Open)
I've tweaked parameter handling to rise an exception in case that both --direct
and --hive-drop-import-delims are present on the command line.
> hive-drop-import-delims doesn't work with MySQL direct import
> -------------------------------------------------------------
>
> Key: SQOOP-409
> URL: https://issues.apache.org/jira/browse/SQOOP-409
> Project: Sqoop
> Issue Type: Bug
> Components: hive-integration
> Affects Versions: 1.4.0-incubating
> Reporter: Lars Francke
> Assignee: Jarek Jarcec Cecho
> Fix For: 1.4.1-incubating
>
>
> When using {{hive-drop-import-delims}} together with {{direct}} on a MySQL
> database the delimiters are not dropped. I have not tested PostgreSQL yet.
> I tried looking at the code but it wasn't easy to follow.
> There seem to be at least two problems:
> * The logic in {{MySQLDumpMapper.map}} only looks for
> {{MySQLUtils.outputDelimsAreMySQL(conf)}} to decide if it needs to be
> reparsed or not, this should also include the hive options
> * This is just a guess at the real problem: The {{ReparsingStreamThread}}
> calls a {{RecordParser}} directly without using the created ORM classes and
> thus circumventing the calls to {{hiveStringDropDelims}}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
