You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Arvind Prabhakar (JIRA)" <ji...@apache.org> on 2011/07/27 22:53:09 UTC
[jira] [Created] (SQOOP-302) Use Information Schema for
MySQLManager
Use Information Schema for MySQLManager
---------------------------------------
Key: SQOOP-302
URL: https://issues.apache.org/jira/browse/SQOOP-302
Project: Sqoop
Issue Type: Task
Components: connectors/mysql
Reporter: Arvind Prabhakar
The connector for MySQL implemented by MySQLManager uses JDBC Metadata Interface to query database metadata. This should be changed so that the connector instead uses Information Schema to query any metadata where necessary.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (SQOOP-302) Use Information Schema for
MySQLManager
Posted by "Arvind Prabhakar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SQOOP-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arvind Prabhakar reassigned SQOOP-302:
--------------------------------------
Assignee: Bilung Lee
> Use Information Schema for MySQLManager
> ---------------------------------------
>
> Key: SQOOP-302
> URL: https://issues.apache.org/jira/browse/SQOOP-302
> Project: Sqoop
> Issue Type: Task
> Components: connectors/mysql
> Reporter: Arvind Prabhakar
> Assignee: Bilung Lee
>
> The connector for MySQL implemented by MySQLManager uses JDBC Metadata Interface to query database metadata. This should be changed so that the connector instead uses Information Schema to query any metadata where necessary.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SQOOP-302) Use Information Schema for
MySQLManager
Posted by "Bilung Lee (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SQOOP-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bilung Lee updated SQOOP-302:
-----------------------------
Attachment: SQOOP-302.diff
> Use Information Schema for MySQLManager
> ---------------------------------------
>
> Key: SQOOP-302
> URL: https://issues.apache.org/jira/browse/SQOOP-302
> Project: Sqoop
> Issue Type: Task
> Components: connectors/mysql
> Reporter: Arvind Prabhakar
> Assignee: Bilung Lee
> Attachments: SQOOP-302.diff
>
>
> The connector for MySQL implemented by MySQLManager uses JDBC Metadata Interface to query database metadata. This should be changed so that the connector instead uses Information Schema to query any metadata where necessary.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SQOOP-302) Use Information Schema for
MySQLManager
Posted by "Arvind Prabhakar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SQOOP-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arvind Prabhakar updated SQOOP-302:
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.4.0
Status: Resolved (was: Patch Available)
Committed. Thanks Bilung.
> Use Information Schema for MySQLManager
> ---------------------------------------
>
> Key: SQOOP-302
> URL: https://issues.apache.org/jira/browse/SQOOP-302
> Project: Sqoop
> Issue Type: Task
> Components: connectors/mysql
> Reporter: Arvind Prabhakar
> Assignee: Bilung Lee
> Fix For: 1.4.0
>
> Attachments: SQOOP-302.diff
>
>
> The connector for MySQL implemented by MySQLManager uses JDBC Metadata Interface to query database metadata. This should be changed so that the connector instead uses Information Schema to query any metadata where necessary.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SQOOP-302) Use Information Schema for
MySQLManager
Posted by "Bilung Lee (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SQOOP-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bilung Lee updated SQOOP-302:
-----------------------------
Status: Patch Available (was: In Progress)
> Use Information Schema for MySQLManager
> ---------------------------------------
>
> Key: SQOOP-302
> URL: https://issues.apache.org/jira/browse/SQOOP-302
> Project: Sqoop
> Issue Type: Task
> Components: connectors/mysql
> Reporter: Arvind Prabhakar
> Assignee: Bilung Lee
> Attachments: SQOOP-302.diff
>
>
> The connector for MySQL implemented by MySQLManager uses JDBC Metadata Interface to query database metadata. This should be changed so that the connector instead uses Information Schema to query any metadata where necessary.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Work started] (SQOOP-302) Use Information Schema for
MySQLManager
Posted by "Bilung Lee (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SQOOP-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on SQOOP-302 started by Bilung Lee.
> Use Information Schema for MySQLManager
> ---------------------------------------
>
> Key: SQOOP-302
> URL: https://issues.apache.org/jira/browse/SQOOP-302
> Project: Sqoop
> Issue Type: Task
> Components: connectors/mysql
> Reporter: Arvind Prabhakar
> Assignee: Bilung Lee
> Attachments: SQOOP-302.diff
>
>
> The connector for MySQL implemented by MySQLManager uses JDBC Metadata Interface to query database metadata. This should be changed so that the connector instead uses Information Schema to query any metadata where necessary.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira