[
https://issues.apache.org/jira/browse/HADOOP-5968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Kimball updated HADOOP-5968:
----------------------------------
Attachment: mysql-warning.patch
Attaching patch for this message. No test because it just moves log4j messages
around -- does not affect functionality.
> Sqoop should only print a warning about mysql import speed once
> ---------------------------------------------------------------
>
> Key: HADOOP-5968
> URL: https://issues.apache.org/jira/browse/HADOOP-5968
> Project: Hadoop Core
> Issue Type: Improvement
> Reporter: Aaron Kimball
> Assignee: Aaron Kimball
> Priority: Minor
> Attachments: mysql-warning.patch
>
>
> After HADOOP-5844, Sqoop can use mysqldump as an alternative to JDBC for
> importing from MySQL. If you use the JDBC mechanism, it prints a warning if
> you could have enabled the mysqldump path instead. But the warning is printed
> multiple times (every time the LocalMySQLManager is instantiated), and also
> when the MySQL manager is used for informational queries (e.g., listing
> tables) rather than true imports.
> It should only emit the warning once per session, and only then if it's
> actually doing an import.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
