hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom White (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-5968) Sqoop should only print a warning about mysql import speed once
Date Tue, 23 Jun 2009 19:58:07 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-5968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tom White updated HADOOP-5968:
------------------------------

       Resolution: Fixed
    Fix Version/s: 0.21.0
     Hadoop Flags: [Reviewed]
           Status: Resolved  (was: Patch Available)

+1

I've just committed this. Thanks Aaron!

> 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 Common
>          Issue Type: Improvement
>            Reporter: Aaron Kimball
>            Assignee: Aaron Kimball
>            Priority: Minor
>             Fix For: 0.21.0
>
>         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.


Mime
View raw message