[
https://issues.apache.org/jira/browse/BIGTOP-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787427#comment-13787427
]
Roman Shaposhnik commented on BIGTOP-993:
-----------------------------------------
[~apurtell] I see where you're coming from. Let me ask you a few questions
about the implementation and perhaps we can settle on a solution that makes
sense. My understanding of the co-processors is that it is possible to load
them up from the HBase shell and I would imagine that it is how the Phoenix
implementation does it -- from the client side. Hence wouldn't it be correct to
assume that sqlline.sh will simply try to load them up and if that fails we can
always bail with a helpful message saying that a certain amount of HBase
configuration is required? Perhaps we can even suggest what needs to be done.
Thoughts?
> Add packaging for Phoenix
> -------------------------
>
> Key: BIGTOP-993
> URL: https://issues.apache.org/jira/browse/BIGTOP-993
> Project: Bigtop
> Issue Type: Sub-task
> Affects Versions: 0.7.0
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Priority: Blocker
> Fix For: 0.7.0
>
> Attachments: 993.patch, 993.patch, 993.patch, 993.patch, 993.patch
>
>
> Phoenix (https://github.com/forcedotcom/phoenix) is an open source BSD-style
> licensed SQL skin over Apache HBase, delivered as a client-embedded JDBC
> driver. The Phoenix query engine transforms your SQL query into one or more
> HBase scans, and orchestrates their execution to produce standard JDBC result
> sets. Direct use of the HBase API, along with coprocessors and custom
> filters, results in performance on the order of milliseconds for small
> queries, or seconds for tens of millions of rows. Applications interact with
> Phoenix through a standard JDBC interface; all the usual interfaces are
> supported.
> As an enhancement of significant value to Apache HBase, in a Bigtop
> distribution Phoenix would have a role similar to that of Datafu, a
> collection of enhancements to Apache Pig.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
