[
https://issues.apache.org/jira/browse/PHOENIX-946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13979902#comment-13979902
]
Andrew Purtell commented on PHOENIX-946:
----------------------------------------
bq. If you want to just query Phoenix data, use Phoenix directly, and get all
the performance gains available by doing that. If you want to combine Phoenix
data with non-HBase data, use Hive
This describes the current situation. So then as Nick says make sure hive can
serde Phoenix types and understands how to read schema out of the system table
and you're done. It's a good interoperability story if both Phoenix and Hive
are being used somewhere, but as today the Hive experience going against HBase
data sources will be relatively poor compared to what is possible.
I don't see how Hive can use Phoenix server side pieces without knowing a lot
of details of Phoenix internals that are likely to change incompatibly from
release to release but maybe you will have a stable API for the coprocessor
endpoints or put one in place for Hive etc.
> 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)
