Hey There, Here are a couple of thoughts off the top of my head:
1. HBase structure doesn't map very well to your typical relational database. In RDBMS systems, there is a fixed schema for tables where its easy to see what the columns are. In HBase, columns can number into the thousands (inifinite??) and can have any name. I really can only imagine custom, particular transformations that would be useful. 2. Column types aren't available in HBase... so every thing would have to map to a BLOB of some kind in a relational database I suppose. -Abe On Thu, Sep 5, 2013 at 4:12 PM, Suhas Satish <[email protected]> wrote: > Its a good question. Even I'd like to know the answer. > > But from the sqoop documentation site, this may help you speed things up a > bit. It still doesnt avoid the intermediate hive-metadata creation stage. > > MySQL provides a direct mode for exports as well, using the mysqlimport tool. > When exporting to MySQL, use the --direct argument to specify this > codepath. This may be higher-performance than the standard JDBC codepath. > > Note: When using export in direct mode with MySQL, the MySQL bulk utility > mysqlimport must be available in the shell path of the task process. > > > > On Wed, Sep 4, 2013 at 3:15 AM, Apple Wang <[email protected]>wrote: > >> exporting Hbase table to mysql table using sqoop, but I find sqoo > > > > > Cheers, > Suhas. >
