[
https://issues.apache.org/jira/browse/HIVE-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12836828#action_12836828
]
John Sichi commented on HIVE-705:
---------------------------------
Jonathan, thanks for the input. I think we should be able to come up with a
mapping feature which encompasses what you've proposed plus what's in HIVE-806
so that it will be up to the user to decide how to map a particular set of
HBase tables into Hive.
We can do this by allowing the HBase table name to be specified as part of
mapping it into Hive. That way, you can have
Hive t1(c1, c2) -> HBase t.cf1(c1, c2)
Hive t2(c3, c4) -> HBase t.cf2(c3, c4)
or
Hive t(c1,c2,c3,c4) -> HBase t(cf1(c1, c2), cf2(c3, c4))
or
Hive t(cf1map, cf2map) -> HBase t(cf1, cf2)
or variations. I'm going to write up a proposal in the Hive wiki and solicit
feedback.
> Let Hive can analyse hbase's tables
> -----------------------------------
>
> Key: HIVE-705
> URL: https://issues.apache.org/jira/browse/HIVE-705
> Project: Hadoop Hive
> Issue Type: New Feature
> Reporter: Samuel Guo
> Assignee: John Sichi
> Attachments: hbase-0.19.3-test.jar, hbase-0.19.3.jar,
> HIVE-705.1.patch, HIVE-705_draft.patch, HIVE-705_revision806905.patch,
> HIVE-705_revision883033.patch
>
>
> Add a serde over the hbase's tables, so that hive can analyse the data stored
> in hbase easily.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
