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

ASF GitHub Bot commented on PHOENIX-2743:
-----------------------------------------

Github user ss77892 commented on the pull request:

    https://github.com/apache/phoenix/pull/155#issuecomment-208572335
  
    Actually I want to get some integration tests in the similar way as it was 
done in PHOENIX-331, but there is a clash between versions. This implementation 
uses Hive 1.2.1, so to run Hive minicluster it's require hadoop version >=  
2.6, but hbase artifacts are still using 2.5, so it's hard to get all those 
miniclusters run together. I still hope to get it resolved. That's why the pom 
contains dependencies on calcite, hbase-test and others. 
    I will add javadocs and clean commented code where it's possible.


> HivePhoenixHandler for big-big join with predicate push down
> ------------------------------------------------------------
>
>                 Key: PHOENIX-2743
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2743
>             Project: Phoenix
>          Issue Type: New Feature
>    Affects Versions: 4.5.0, 4.6.0
>         Environment: hive-1.2.1
>            Reporter: JeongMin Ju
>              Labels: features, performance
>         Attachments: PHOENIX-2743-1.patch
>
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> Phoenix support hash join & sort-merge join. But in case of big*big join does 
> not process well.
> Therefore Need other method like Hive.
> I implemented hive-phoenix-handler that can access Apache Phoenix table on 
> HBase using HiveQL.
> hive-phoenix-handler is very faster than hive-hbase-handler because of 
> applying predicate push down.
> I am publishing source code to github for contribution and maybe will be 
> completed by next week.
> https://github.com/mini666/hive-phoenix-handler
> please, review my proposal.



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

Reply via email to