Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <1797863079.1244077567396.JavaMail.jira@brutus>
Date: Wed, 3 Jun 2009 18:06:07 -0700 (PDT)
From: "Aaron Kimball (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Created: (HADOOP-5968) Sqoop should only print a warning
 about mysql import speed once
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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.