[
https://issues.apache.org/jira/browse/SQOOP-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13536041#comment-13536041
]
Jarek Jarcec Cecho commented on SQOOP-793:
------------------------------------------
Hi Guido,
thank you very much for opening this ticket. I would firstly like to understand
use case that you're trying to solve here. By default MySQL is using JDBC to
transfer data from/to MySQL server. With direct option, Sqoop will use native
utilities (mysqldump, mysqlimport) to perform data movement instead of JDBC.
However input/output format is in both situations the same and Sqoop currently
supports Avro, Sequence file and text files.
My current understanding is that you're trying to create new input/output
format to work with very special type of files that are generated by mysqldump
utility. Such functionality should however be independent on the connector -
e.g. it should be working across all connectors. I'm not quite sure at this
point that it would make sense to support additional input/output file when the
file is so "specific" and unusual. If you have mysql dump files on your HDFS,
you can always perform mapreduce job to convert them to CSV file and than
export them with Sqoop.
To quickly answer your questions:
* SQOOP-589: Is about Sqoop2 so it's not relevant to Sqoop1.
* SQOOP-526: Thanks for fixing! I greatly appreciate that and I know that I'm
missing review. I'll try to review it as soon as possible. Unfortunately I'm
currently in "packing" mode as I'll be travelling around Christmas and I do not
have much time to spare. But don't worry, your contribution will not be
forgotten :-)
* SQOOP-794: I'm running all MySQL third party tests on regular basis and I'm
100% sure that they are working. I'm expecting that you're missing the JDBC
driver in lib directory or similar require "extra step".
Jarcec
> mysqldump > file > hdfs > sqoop
> -------------------------------
>
> Key: SQOOP-793
> URL: https://issues.apache.org/jira/browse/SQOOP-793
> Project: Sqoop
> Issue Type: New Feature
> Components: connectors/mysql
> Reporter: Guido Serra aka Zeph
> Assignee: Guido Serra aka Zeph
> Priority: Minor
>
> extend the MySQLDump module to be able to read from a mysqldump generated
> file,
> saved on hdfs, instead of triggering the "--direct" option or connect via jdbc
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
