You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Brock Noland (JIRA)" <ji...@apache.org> on 2012/05/17 01:03:06 UTC

[jira] [Created] (SQOOP-487) InformationSchemaManager.getPrimaryKeyQuery can take a very long time for large mysql table with partitions

Brock Noland created SQOOP-487:
----------------------------------

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


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

[jira] [Commented] (SQOOP-487) InformationSchemaManager.getPrimaryKeyQuery can take a very long time for large mysql table with partitions

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SQOOP-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13287608#comment-13287608 ] 

Hudson commented on SQOOP-487:
------------------------------

Integrated in Sqoop-ant-jdk-1.6 #119 (See [https://builds.apache.org/job/Sqoop-ant-jdk-1.6/119/])
    SQOOP-487  Log InformationSchemaManager.getPrimaryKeyQuery invocation (Revision 1345313)

     Result = SUCCESS
blee : 
Files : 
* /sqoop/trunk/src/java/org/apache/sqoop/manager/CatalogQueryManager.java

                
> 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

[jira] [Updated] (SQOOP-487) InformationSchemaManager.getPrimaryKeyQuery can take a very long time for large mysql table with partitions

Posted by "Jarek Jarcec Cecho (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SQOOP-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jarek Jarcec Cecho updated SQOOP-487:
-------------------------------------

    Attachment: SQOOP-487.patch
    
> 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
>             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

[jira] [Commented] (SQOOP-487) InformationSchemaManager.getPrimaryKeyQuery can take a very long time for large mysql table with partitions

Posted by "Jarek Jarcec Cecho (JIRA)" <ji...@apache.org>.
    [ 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