[
https://issues.apache.org/jira/browse/SQOOP-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13429229#comment-13429229
]
Abhijeet Gaikwad commented on SQOOP-539:
----------------------------------------
In Sqoop InformationSchemaManager class is a super of two managers namely -
SQLServerManager and MySqlManager.
MySql contains column COLUMN_KEY in INFORMATION_SCHEMA.COLUMNS
(http://dev.mysql.com/doc/refman/5.1/en/columns-table.html), but it seems
SqlServer does not support this column
(http://msdn.microsoft.com/en-us/library/ms188348%28v=sql.105%29.aspx). So this
change will fail the SqlServer flow.
What I propose is to make this change specific to Mysql by overriding
getPrimaryKeyQuery() in MySqlManger class. Let me know.
> getPrimaryKeyQuery is very slow in mysql 5.0.77
> -----------------------------------------------
>
> Key: SQOOP-539
> URL: https://issues.apache.org/jira/browse/SQOOP-539
> Project: Sqoop
> Issue Type: Bug
> Components: connectors/mysql
> Affects Versions: 1.4.1-incubating
> Environment: mysql 5.0.77-percona-highperfb0805
> Reporter: Jhovanny
> Priority: Minor
> Labels: performance
> Fix For: 1.4.2
>
> Attachments: patch
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> The current query used to get the primary key for a table takes 20 seconds in
> my production environment and 11 minutes in my QA environment. I simplified
> it and it now runs very fast (0.08 seconds in my production environment). I'm
> submitting the patch I applied locally.
--
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
