[
https://issues.apache.org/jira/browse/SQOOP-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14297452#comment-14297452
]
Jarek Jarcec Cecho commented on SQOOP-2056:
-------------------------------------------
You can [already download|http://www.apache.org/dyn/closer.cgi/sqoop/1.99.4]
early bits [~khariharan]. Please do note that Sqoop 2 is currently not on
feature parity with Sqoop 1. We have [preliminary
roadmap|https://cwiki.apache.org/confluence/display/SQOOP/Sqoop+2+Roadmap] on
the wiki. If you have any questions, feel free to drop them to our [dev
list|http://sqoop.apache.org/mail-lists.html].
> Support for Mysql Sqoop Metastore
> ---------------------------------
>
> Key: SQOOP-2056
> URL: https://issues.apache.org/jira/browse/SQOOP-2056
> Project: Sqoop
> Issue Type: New Feature
> Reporter: Karthic Hariharan
>
> 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)
