sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthic Hariharan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-2056) Support for Mysql Sqoop Metastore
Date Wed, 13 May 2015 18:42:01 GMT

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

Karthic Hariharan commented on SQOOP-2056:
------------------------------------------

Patch attached to ticket. Can you review [~jarcec], it is based off of the branch-1.4.5. 
Github link for the same:
https://github.com/karthich/sqoop/tree/SQOOP-2056

> Support for Mysql Sqoop Metastore
> ---------------------------------
>
>                 Key: SQOOP-2056
>                 URL: https://issues.apache.org/jira/browse/SQOOP-2056
>             Project: Sqoop
>          Issue Type: New Feature
>    Affects Versions: 1.4.5
>            Reporter: Karthic Hariharan
>            Assignee: Karthic Hariharan
>         Attachments: sqoop-patch.txt
>
>
> We would love to see sqoop metastore supported for Mysql.
> At the moment sqoop metastore can be set up only with HSQLdb. Even though you can fake
a mysql database to look like a HSQLdb (refer http://bit.ly/1tz2J5u), it does not translate
to compatibility to all of sqoop's features. 
> Some of the incompatibilities are:
> * Metastore client assumes all connections to the metastore is in serializable transaction
isolation so when sqoop job is executed it never really finishes because it's trying to run
a transaction within a transaction.
> * Incremental loads using last modified timestamp doesnt work because the sqoop job tries
to get the current time on the database which is a different sql command for Hsqldb and mysql.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message