[ https://issues.apache.org/jira/browse/SQOOP-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16124922#comment-16124922 ]
Boglarka Egyed commented on SQOOP-2056: --------------------------------------- Hi [~tomharrisonjr], Please be aware that there is an improvement JIRA being in progress (SQOOP-3216) to support other databases as Sqoop Metastore. First patch is already available, please kindly take a look and share your thoughts on the Review Board if you think anything is missing. Thank you, Bogi > 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 > 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.4.14#64029)