[
https://issues.apache.org/jira/browse/PHOENIX-946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13978247#comment-13978247
]
Gabriel Reid commented on PHOENIX-946:
--------------------------------------
My take on this is that goal (if desirable) would be to implement "Build
something similar to HiveHBaseHandler where we try to leverage a lot of
Inputformat code written for Pig and be able to run Hive Queries as MR jobs",
as [[email protected]] outlined above.
This would indeed mean that the queries would be executed within the context of
MR jobs (or a Tez DAG?), so it will mean that many of the advantages of Phoenix
would probably be lost, or at least not used (such as doing pre-aggregations in
coprocessors, for example).
However, the potential win that I see is that it would allow doing things like
joining data stored on HDFS with data stored in Phoenix/HBase. In other words,
I see this as giving Hive access to Phoenix data, and not the other way around.
I don't see all that much use in being able to parse HiveQL or tying in to the
HiveMetastore/HCat from Phoenix, as that would just result in a Hive-similar
query tool that can only query Phoenix-stored HBase data (as opposed to what
Hive can do, which is query pretty much anything)
> Use Phoenix to service Hive queries over HBase data
> ---------------------------------------------------
>
> Key: PHOENIX-946
> URL: https://issues.apache.org/jira/browse/PHOENIX-946
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
