[jira] [Commented] (HIVE-10091) Generate Hbase execution plan for partition filter conditions in HbaseStore api calls

["Alan Gates (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HIVE-10091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14381307#comment-14381307 ] 

Alan Gates commented on HIVE-10091:
-----------------------------------

I've left some comments on review board.

Also a question.  If I read HBaseFilterPlanUtil correctly this can handle non-boolean expressions on initial keys right now, but not booleans or expressions on keys beyond the first one.  I think it's fine to get this checked in as is and and functionality as we go.  I just wanted to make sure I understood correctly.


> Generate Hbase execution plan for partition filter conditions in HbaseStore api calls
> -------------------------------------------------------------------------------------
>
>                 Key: HIVE-10091
>                 URL: https://issues.apache.org/jira/browse/HIVE-10091
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Metastore
>            Reporter: Thejas M Nair
>            Assignee: Thejas M Nair
>             Fix For: hbase-metastore-branch
>
>         Attachments: HIVE-10091.1.patch
>
>
> RawStore functions that support partition filtering are the following - 
> getPartitionsByExpr
> getPartitionsByFilter (takes filter string as argument, used from hcatalog)
> We need to generate a query execution plan in terms of Hbase scan api calls for a given filter condition.
> NO PRECOMMIT TESTS



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)