[ https://issues.apache.org/jira/browse/HIVE-6411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13960208#comment-13960208 ]
Swarnim Kulkarni commented on HIVE-6411: ---------------------------------------- [~xuefuz][~navis] I was wondering if there is something that is still holding us back on this JIRA or can we get this in? > Support more generic way of using composite key for HBaseHandler > ---------------------------------------------------------------- > > Key: HIVE-6411 > URL: https://issues.apache.org/jira/browse/HIVE-6411 > Project: Hive > Issue Type: Improvement > Components: HBase Handler > Reporter: Navis > Assignee: Navis > Priority: Minor > Attachments: HIVE-6411.1.patch.txt, HIVE-6411.2.patch.txt, > HIVE-6411.3.patch.txt, HIVE-6411.4.patch.txt, HIVE-6411.5.patch.txt, > HIVE-6411.6.patch.txt, HIVE-6411.7.patch.txt, HIVE-6411.8.patch.txt, > HIVE-6411.9.patch.txt > > > HIVE-2599 introduced using custom object for the row key. But it forces key > objects to extend HBaseCompositeKey, which is again extension of LazyStruct. > If user provides proper Object and OI, we can replace internal key and keyOI > with those. > Initial implementation is based on factory interface. > {code} > public interface HBaseKeyFactory { > void init(SerDeParameters parameters, Properties properties) throws > SerDeException; > ObjectInspector createObjectInspector(TypeInfo type) throws SerDeException; > LazyObjectBase createObject(ObjectInspector inspector) throws > SerDeException; > } > {code} -- This message was sent by Atlassian JIRA (v6.2#6252)