[
https://issues.apache.org/jira/browse/HIVE-6147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887238#comment-13887238
]
Xuefu Zhang commented on HIVE-6147:
-----------------------------------
This looks good, but from the patch, it seems that the solution is only for
HBase. I wonder if we have given thoughts on the idea of generalizing the
problem and providing a general solution. I can see the benefits of separating
the storage (such as hbase) and data format (avro, thrift, protocol buf,
parquet, etc). Then we solve M + N problems rather than M * N problems. What
if the avro data is coming from other storage, such as accumulo, or parquet
data from HBase.
> Support avro data stored in HBase columns
> -----------------------------------------
>
> Key: HIVE-6147
> URL: https://issues.apache.org/jira/browse/HIVE-6147
> Project: Hive
> Issue Type: Bug
> Components: HBase Handler
> Affects Versions: 0.12.0
> Reporter: Swarnim Kulkarni
> Assignee: Swarnim Kulkarni
> Attachments: HIVE-6147.1.patch.txt
>
>
> Presently, the HBase Hive integration supports querying only primitive data
> types in columns. It would be nice to be able to store and query Avro objects
> in HBase columns by making them visible as structs to Hive. This will allow
> Hive to perform ad hoc analysis of HBase data which can be deeply structured.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
