[ 
https://issues.apache.org/jira/browse/BIGTOP-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13779022#comment-13779022
 ] 

Sean Mackrory commented on BIGTOP-993:
--------------------------------------

I've built RPMs on openSUSE 12.3 and installed / removed DEBs on Ubuntu 10.04, 
and the packaging looks mainly good to me (although the patch seems pretty 
messed up when trying to apply it). A few questions / nitpicks:

* It doesn't look like there are any tarball releases, and we're just building 
from a tarball of the master branch. Are there plans at Phoenix to cut a 
tarball release we can consume?
* Would this be the first time we're packaging a BSD-licensed  component? We've 
previously listed Apache licenses as requirements for inclusion, but I think 
BSD is close enough. I presume there are no hoops we need to jump through 
before distributing BSD-licensed bits as an Apache project?
* The package includes -tests and -sources JARs which we usually don't do. 
There's a versionless symlink for tests so it looks intentional - but what's 
the intention?
* There are 2 other JARs without versionless symlinks. We might as well do all 
of them since it's handy when scripting infrastructure around Bigtop.
* We're creating an empty /usr/lib/phoenix/bin directory. Maybe clean it up? 
Better yet, we could include a wrapper around the sqlline.sh CLI client they 
bundle :)
                
> 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
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to