+1 (non-binding) for incubation of Phoenix. This is already a very useful
project for HBase users, and it will be good to see it driven by a larger
community.
It may be also be good to get a legal opinion about the name, and/or check for
an alternative. There may be some existing software
A bit late to this, but another enthusiastic +1 for Phoenix.
Phoenix is an excellent addition to HBase. Data types, loose coupling between
your data schemas and applications making schema evolution easier, speedier
scans and a good set of aggregation functions - a lot of convenience for a
On Wed, Nov 13, 2013 at 12:43 PM, James Taylor jtay...@salesforce.com wrote:
Hi All,
We're pleased to share a draft ASF incubation proposal for Phoenix, a
SQL layer over HBase, initially developed at Salesforce.com and
subsequently open sourced on github
On Sun, Nov 17, 2013 at 5:59 PM, Roman Shaposhnik r...@apache.org wrote:
* I am sure with the name like Phoenix there's tons of clashes,
but perhaps Apache Phoenix should be fine
We'd be fine with Apache Phoenix.
* How tightly coupled is it with HBase? IOW, do you anticipate
+1. We are currently running phoenix with production traffic, and enjoying
the benefits.
Joris
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail:
On Wed, Nov 13, 2013 at 9:43 PM, James Taylor jtay...@salesforce.comwrote:
Hi All,
We're pleased to share a draft ASF incubation proposal for Phoenix, a
SQL layer over HBase, initially developed at Salesforce.com and
subsequently open sourced on github
On Wed, Nov 13, 2013 at 10:50 PM, Henry Saputra henry.sapu...@gmail.comwrote:
It is indeed very specific for HBase use I suppose. Would it be more
beneficial to make it sub-project of HBase to get full community
support from HBase?
I'm on the HBase PMC and am enthusiastically +1 for
Phoenix is a wonderful addition as sub-project of HBase and I use it
everyday in production.
+1 from me for sure.
— Patrick
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail:
Patrick Reilly preilly at php.net writes:
Phoenix is a wonderful addition as sub-project of HBase and I use it
everyday in production.
+1 from me for sure.
— Patrick
Sorry, I meant a top level project not a sub-project of HBase.
I apologize for the confusion.
— Patrick
On Thu, Nov 14, 2013 at 9:41 AM, Andrew Purtell apurt...@apache.org wrote:
On Wed, Nov 13, 2013 at 10:50 PM, Henry Saputra
henry.sapu...@gmail.comwrote:
It is indeed very specific for HBase use I suppose. Would it be more
beneficial to make it sub-project of HBase to get full community
+1 for Phoenix as well.
SQL access for HBase is a repeated thread in the community and while we
probably aren't at the point where there is a single answer for this - and
may never be - it would be nice to have a few preferred options, so to
speak, with robust communities around them. Also, per
Phoenix is a great addition as sub-project of HBase.
+1 from me.
Thanks,
Anil Gupta
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
It is indeed very specific for HBase use I suppose. Would it be more
beneficial to make it sub-project of HBase to get full community
support from HBase?
On Wed, Nov 13, 2013 at 12:43 PM, James Taylor jtay...@salesforce.com wrote:
Hi All,
We're pleased to share a draft ASF incubation proposal
Hi All,
I am sorry for the confusion. I didn't mean to say that Phoenix should be a
sub-project of Apache HBase.
My +1 for Phoenix as Top Level Project.
At Intuit, we have been extensively using Phoenix.
Thanks,
Anil Gupta
Software Engineer, Intuit Inc
On Wed, Nov 13, 2013 at 10:31 PM, Anil
14 matches
Mail list logo
