I'm not aware of any facility for importing to multiple tables in Hbase unfortunately. I think that's a manual process. Hopefully someone else on this mailing list will know the answer to that question better.
On Mon, Dec 23, 2013 at 10:29 AM, Saiph Kappa <[email protected]> wrote: > Yes, I have checked. But I thought there was some automatic way of sqoop > doing that (without users have to explicitly perform the import for each > particular table/column). > > I thought Sqoop could transform relational schemas into hbase "schemas", > i.e., to get a mapping from one structure to another. But this is not the > case right? > > Thanks. > > > On Wed, Dec 18, 2013 at 9:01 PM, Abraham Elmahrek <[email protected]>wrote: > >> Hey there, >> >> Have you checked out >> http://sqoop.apache.org/docs/1.4.4/SqoopUserGuide.html#_importing_data_into_hbase? >> The row key will be what ever column you are splitting by, unless >> --hbase-row-key option is specified. With a join, this should be no >> different. The resulting columns of the join will end up in HBase under the >> same column family using column names for columns in Hbase. >> >> -Abe >> >> >> On Wed, Dec 18, 2013 at 10:08 AM, Saiph Kappa <[email protected]>wrote: >> >>> Hi, >>> >>> Can anyone tell me how sqoop maps relational keys to hbase keys? >>> >>> For instance, in mysql, if I have table Location with columns id, >>> address, city, country, where the last two are foreign keys to tables City >>> and Country, how is this mapped to HBase? Will we still have a table City >>> and Country? >>> >>> Or, if we have tables Consumer, Provider, and Transaction (which is just >>> to join the other two tables when a transaction happens), how is this >>> situation mapped to hbase (in terms of tables and generated keys). >>> >>> Thanks. >>> >> >> >
