[
https://issues.apache.org/jira/browse/BIGTOP-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13787677#comment-13787677
]
Andrew Purtell commented on BIGTOP-993:
---------------------------------------
bq. My personal take now is that it would be useful to expose the sqlline.sh
Ok. If you would like something a bit more, like a wrapper of some kind in
/usr/bin ("hbase-phoenix-sqlline"?) let me know.
bq. with the possibility of taking jars from HDFS could even be trivial
Well... to do this for coprocessors put the path to the jar in HDFS into the
table attribute, and to do this for filters set 'hbase.dynamic.jars.dir' in the
HBase site config and make sure the jar is located in that directory. Ok, so
now Phoenix is "installed" on HDFS but that dynamic jars dir is a DLL hell.
What I want to do in BIGTOP-1007 is set up a standard for HBase configuration
fragments for coprocessor applications packaged by Bigtop, with helpful
modifications on the HBase side as needed to avoid repeating history.
I also don't think hosting package bits on a distributed filesystem fits well
with OS level package management. A DEB or RPM cannot presume the service or
its dependencies are running at install or removal time. (Not suggesting you
suggested that - just making a point.) Highly likely this is going to be an
issue with YARN apps down the road.
> 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)
