[
https://issues.apache.org/jira/browse/PHOENIX-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15246124#comment-15246124
]
Josh Elser commented on PHOENIX-2743:
-------------------------------------
{quote}
bq . I would assume that it's not necessary for any of them, but let me know
if I'm wrong
Actually I added that only for the packages that are not in the dependencies in
the root pom.xml. Not sure whether it's good to include them there since they
are used in this package only and the module has it's own artifact. If we want
to make it as a part of phoenix-client.jar, those dependencies can be moved to
the root pom.xml and specify the version there.
{quote}
Ah! I'm with you now. Convention states that we should have all dependencies
declared in dependencyManagement and just refer to dependencies by
groupId:artifactId in sub-modules. I will clean that up too (super easy to
change). Thanks.
> 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)
