sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Jarcec Cecho (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-487) InformationSchemaManager.getPrimaryKeyQuery can take a very long time for large mysql table with partitions
Date Sun, 20 May 2012 08:46:41 GMT

    [ https://issues.apache.org/jira/browse/SQOOP-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13279700#comment-13279700
] 

Jarek Jarcec Cecho commented on SQOOP-487:
------------------------------------------

Attached patch do have granted Apache license even though that Apache icon is not visible
(at least for me).
                
> InformationSchemaManager.getPrimaryKeyQuery can take a very long time for large mysql
table with partitions
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: SQOOP-487
>                 URL: https://issues.apache.org/jira/browse/SQOOP-487
>             Project: Sqoop
>          Issue Type: Improvement
>    Affects Versions: 1.3.0
>            Reporter: Brock Noland
>            Assignee: Jarek Jarcec Cecho
>             Fix For: 1.4.2-incubating
>
>         Attachments: SQOOP-487.patch
>
>
> Since we are already verbose when starting a job it would be nice to log a message saying
we are obtaining the primary key.

--
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

        

Mime
View raw message