hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xuefu Zhang (JIRA)" <>
Subject [jira] [Commented] (HIVE-7048) CompositeKeyHBaseFactory should not use FamilyFilter
Date Wed, 21 May 2014 14:28:38 GMT


Xuefu Zhang commented on HIVE-7048:

We cannot make CompositeKeyHBaseFactory abstract as it's existing functionality: user provides
a key class for HBase key via HBaseSerDe.HBASE_COMPOSITE_KEY_CLASS. However, without knowing
how the key is serialized, CompositeKeyHBaseFactory is not able to do any pushdown. Thus,
I think we should get rid of all pushdown/filter related code from CompositeKeyHBaseFactory.
User desiring of this capability would have to provided their own key factory class. It's
fine to extract the pushdown/filter related code into utility methods somewhere.

> CompositeKeyHBaseFactory should not use FamilyFilter
> ----------------------------------------------------
>                 Key: HIVE-7048
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>          Components: HBase Handler
>            Reporter: Swarnim Kulkarni
>            Assignee: Swarnim Kulkarni
>            Priority: Blocker
>         Attachments: HIVE-7048.1.patch.txt
> HIVE-6411 introduced a more generic way to provide composite key implementations via
custom factory implementations. However it seems like the CompositeHBaseKeyFactory implementation
uses a FamilyFilter for row key scans which doesn't seem appropriate. This should be investigated
further and if possible replaced with a RowRangeScanFilter.

This message was sent by Atlassian JIRA

View raw message