[
https://issues.apache.org/jira/browse/HIVE-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13892894#comment-13892894
]
Navis commented on HIVE-2599:
-----------------------------
I cannot understand the intention of this issue. Without this patch,
{noformat}
hive> CREATE TABLE hbase_struct(key struct<col1:int,col2:int>, value string)
> STORED BY 'org.apache.hadoop.hive.hbase.HBaseStorageHandler'
> WITH SERDEPROPERTIES ("hbase.columns.mapping" = ":key,cf:string");
...
hive> insert into table hbase_struct select struct(1000,2000),'value' from src
tablesample (1 rows);
...
hive> select * from hbase_struct;
{"col1":1000,"col2":2000} value
hive> select key.col1,key.col2 from hbase_struct;
1000 2000
{noformat}
I can do anything with default LazyStruct and now it's making new Struct and
using it. Is it for controlling wire-format on hbase rathe than default json
serialization?
> Support Composit/Compound Keys with HBaseStorageHandler
> -------------------------------------------------------
>
> Key: HIVE-2599
> URL: https://issues.apache.org/jira/browse/HIVE-2599
> Project: Hive
> Issue Type: Improvement
> Components: HBase Handler
> Affects Versions: 0.8.0
> Reporter: Hans Uhlig
> Assignee: Swarnim Kulkarni
> Fix For: 0.13.0
>
> Attachments: HIVE-2599.1.patch.txt, HIVE-2599.2.patch.txt,
> HIVE-2599.2.patch.txt, HIVE-2599.3.patch.txt, HIVE-2599.4.patch.txt
>
>
> It would be really nice for hive to be able to understand composite keys from
> an underlying HBase schema. Currently we have to store key fields twice to be
> able to both key and make data available. I noticed John Sichi mentioned in
> HIVE-1228 that this would be a separate issue but I cant find any follow up.
> How feasible is this in the HBaseStorageHandler?
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
