We are pleased to announce the immediate availability of Phoenix v 1.1,
with support for HBase v 0.94.4 and above. Phoenix is a SQL layer on top
of HBase. For details, see our announcement here:
http://phoenix-hbase.blogspot.com/2013/02/annoucing-phoenix-v-11-support-for.html

Thanks,

James Taylor
https://github.com/forcedotcom/phoenix
@JamesPlusPlus

I ran test suite and they passed:

Tests run: 452, Failures: 0, Errors: 0, Skipped: 0

[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESS
Good job.

On Mon, Feb 25, 2013 at 9:35 AM, James Taylor <[EMAIL PROTECTED]>wrote:

> We are pleased to announce the immediate availability of Phoenix v 1.1,
> with support for HBase v 0.94.4 and above. Phoenix is a SQL layer on top of
> HBase. For details, see our announcement here:
> http://phoenix-hbase.blogspot.**com/2013/02/annoucing-phoenix-**
> v-11-support-for.html<http://phoenix-hbase.blogspot.com/2013/02/annoucing-phoenix-v-11-support-for.html>
>
> Thanks,
>
> James Taylor
> https://github.com/**forcedotcom/phoenix<https://github.com/forcedotcom/phoenix>
> @JamesPlusPlus
>

Looks great.

It seems SQL in Hbase is becoming a trend (not complaining) , how does this
compare to Cloudera's Impala

On Mon, Feb 25, 2013 at 5:09 PM, Ted Yu <[EMAIL PROTECTED]> wrote:

> I ran test suite and they passed:
>
> Tests run: 452, Failures: 0, Errors: 0, Skipped: 0
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD SUCCESS
>
>
> Good job.
>
> On Mon, Feb 25, 2013 at 9:35 AM, James Taylor <[EMAIL PROTECTED]
> >wrote:
>
> > We are pleased to announce the immediate availability of Phoenix v 1.1,
> > with support for HBase v 0.94.4 and above. Phoenix is a SQL layer on top
> of
> > HBase. For details, see our announcement here:
> > http://phoenix-hbase.blogspot.**com/2013/02/annoucing-phoenix-**
> > v-11-support-for.html<
> http://phoenix-hbase.blogspot.com/2013/02/annoucing-phoenix-v-11-support-for.html
> >
> >
> > Thanks,
> >
> > James Taylor
> > https://github.com/**forcedotcom/phoenix<
> https://github.com/forcedotcom/phoenix>
> > @JamesPlusPlus
> >
>

--
--- Get your facts first, then you can distort them as you please.--

Both Phoenix and Impala provide SQL as a way to get at your data. Here
are some of the high-level similarities and differences I can think of:
- Phoenix is targeting the support of ANSI SQL, while Impala supports
HiveQL.
- Phoenix works with HBase data only, while Impala works with HDFS and
HBase data.
- Phoenix is faster against HBase data (take a look at our Performance
Page here: https://github.com/forcedotcom/phoenix/wiki/Performance)
- Both are open source: Phoenix is written in Java while Impala is
written mostly in C++
- Phoenix doesn't yet support joins, while Impala does
- Phoenix doesn't require running additional servers, processes, or
daemons, while Impala does

Regards,
James

On 02/26/2013 04:49 AM, Rita wrote:
> Looks great.
>
> It seems SQL in Hbase is becoming a trend (not complaining) , how does this
> compare to Cloudera's Impala
>
> On Mon, Feb 25, 2013 at 5:09 PM, Ted Yu <[EMAIL PROTECTED]> wrote:
>
>> I ran test suite and they passed:
>>
>> Tests run: 452, Failures: 0, Errors: 0, Skipped: 0
>>
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] BUILD SUCCESS
>>
>>
>> Good job.
>>
>> On Mon, Feb 25, 2013 at 9:35 AM, James Taylor <[EMAIL PROTECTED]
>>> wrote:
>>> We are pleased to announce the immediate availability of Phoenix v 1.1,
>>> with support for HBase v 0.94.4 and above. Phoenix is a SQL layer on top
>> of
>>> HBase. For details, see our announcement here:
>>> http://phoenix-hbase.blogspot.**com/2013/02/annoucing-phoenix-**
>>> v-11-support-for.html<
>> http://phoenix-hbase.blogspot.com/2013/02/annoucing-phoenix-v-11-support-for.html
>>>
>>> Thanks,
>>>
>>> James Taylor
>>> https://github.com/**forcedotcom/phoenix<
>> https://github.com/forcedotcom/phoenix>
>>> @JamesPlusPlus
>>>
>
>

In the first graph on the performance page, what does 'key filter'
represent ?

Thanks

On Tue, Feb 26, 2013 at 9:53 AM, James Taylor <[EMAIL PROTECTED]>wrote:

> Both Phoenix and Impala provide SQL as a way to get at your data. Here are
> some of the high-level similarities and differences I can think of:
> - Phoenix is targeting the support of ANSI SQL, while Impala supports
> HiveQL.
> - Phoenix works with HBase data only, while Impala works with HDFS and
> HBase data.
> - Phoenix is faster against HBase data (take a look at our Performance
> Page here: https://github.com/**forcedotcom/phoenix/wiki/**Performance<https://github.com/forcedotcom/phoenix/wiki/Performance>
> )
> - Both are open source: Phoenix is written in Java while Impala is written
> mostly in C++
> - Phoenix doesn't yet support joins, while Impala does
> - Phoenix doesn't require running additional servers, processes, or
> daemons, while Impala does
>
> Regards,
> James
>
>
> On 02/26/2013 04:49 AM, Rita wrote:
>
>> Looks great.
>>
>> It seems SQL in Hbase is becoming a trend (not complaining) , how does
>> this
>> compare to Cloudera's Impala
>>
>> On Mon, Feb 25, 2013 at 5:09 PM, Ted Yu <[EMAIL PROTECTED]> wrote:
>>
>>  I ran test suite and they passed:
>>>
>>> Tests run: 452, Failures: 0, Errors: 0, Skipped: 0
>>>
>>> [INFO]
>>> ------------------------------**------------------------------**
>>> ------------
>>> [INFO] BUILD SUCCESS
>>>
>>>
>>> Good job.
>>>
>>> On Mon, Feb 25, 2013 at 9:35 AM, James Taylor <[EMAIL PROTECTED]
>>>
>>>> wrote:
>>>> We are pleased to announce the immediate availability of Phoenix v 1.1,
>>>> with support for HBase v 0.94.4 and above. Phoenix is a SQL layer on top
>>>>
>>> of
>>>
>>>> HBase. For details, see our announcement here:
>>>> http://phoenix-hbase.blogspot.****com/2013/02/annoucing-**phoenix-**
>>>> v-11-support-for.html<
>>>>
>>> http://phoenix-hbase.blogspot.**com/2013/02/annoucing-phoenix-**
>>> v-11-support-for.html<http://phoenix-hbase.blogspot.com/2013/02/annoucing-phoenix-v-11-support-for.html>
>>>
>>>>
>>>> Thanks,
>>>>
>>>> James Taylor
>>>> https://github.com/****forcedotcom/phoenix<https://github.com/**forcedotcom/phoenix>
>>>> <
>>>>
>>> https://github.com/**forcedotcom/phoenix<https://github.com/forcedotcom/phoenix>
>>> >
>>>
>>>> @JamesPlusPlus
>>>>
>>>>
>>
>>
>

The 'key filter' are cases in which Phoenix doesn't have to do a full
table scan (the orange line), while the red line is where it does. This
depends on how many of your row key columns you specify in the where
clause of your query.  For example, given a query like this:

SELECT host, created_date FROM web_stat WHERE host='salesforce.com' AND
create_date=to_date('2013-02-25 12:00:00')

Assuming that host and created_date are the columns making up the row
key, this query would be close to the orange line. While this query:

SELECT host, created_date FROM web_stat WHERE host='salesforce.com'
would be between the orange and red line, depending on the data
distribution.

If you had no where clause at all, you'd be at the red line. This is
somewhat over simplified, given all the factors of multiple column
families, wide rows, narrow rows, data distribution, etc., but it
illustrates the idea.

On 02/26/2013 09:59 AM, Ted Yu wrote:
> In the first graph on the performance page, what does 'key filter'
> represent ?
>
> Thanks
>
> On Tue, Feb 26, 2013 at 9:53 AM, James Taylor <[EMAIL PROTECTED]>wrote:
>
>> Both Phoenix and Impala provide SQL as a way to get at your data. Here are
>> some of the high-level similarities and differences I can think of:
>> - Phoenix is targeting the support of ANSI SQL, while Impala supports
>> HiveQL.
>> - Phoenix works with HBase data only, while Impala works with HDFS and
>> HBase data.
>> - Phoenix is faster against HBase data (take a look at our Performance
>> Page here: https://github.com/**forcedotcom/phoenix/wiki/**Performance<https://github.com/forcedotcom/phoenix/wiki/Performance>
>> )
>> - Both are open source: Phoenix is written in Java while Impala is written
>> mostly in C++
>> - Phoenix doesn't yet support joins, while Impala does
>> - Phoenix doesn't require running additional servers, processes, or
>> daemons, while Impala does
>>
>> Regards,
>> James
>>
>>
>> On 02/26/2013 04:49 AM, Rita wrote:
>>
>>> Looks great.
>>>
>>> It seems SQL in Hbase is becoming a trend (not complaining) , how does
>>> this
>>> compare to Cloudera's Impala
>>>
>>> On Mon, Feb 25, 2013 at 5:09 PM, Ted Yu <[EMAIL PROTECTED]> wrote:
>>>
>>>   I ran test suite and they passed:
>>>> Tests run: 452, Failures: 0, Errors: 0, Skipped: 0
>>>>
>>>> [INFO]
>>>> ------------------------------**------------------------------**
>>>> ------------
>>>> [INFO] BUILD SUCCESS
>>>>
>>>>
>>>> Good job.
>>>>
>>>> On Mon, Feb 25, 2013 at 9:35 AM, James Taylor <[EMAIL PROTECTED]
>>>>
>>>>> wrote:
>>>>> We are pleased to announce the immediate availability of Phoenix v 1.1,
>>>>> with support for HBase v 0.94.4 and above. Phoenix is a SQL layer on top
>>>>>
>>>> of
>>>>
>>>>> HBase. For details, see our announcement here:
>>>>> http://phoenix-hbase.blogspot.****com/2013/02/annoucing-**phoenix-**
>>>>> v-11-support-for.html<
>>>>>
>>>> http://phoenix-hbase.blogspot.**com/2013/02/annoucing-phoenix-**
>>>> v-11-support-for.html<http://phoenix-hbase.blogspot.com/2013/02/annoucing-phoenix-v-11-support-for.html>
>>>>
>>>>> Thanks,
>>>>>
>>>>> James Taylor
>>>>> https://github.com/****forcedotcom/phoenix<https://github.com/**forcedotcom/phoenix>
>>>>> <
>>>>>
>>>> https://github.com/**forcedotcom/phoenix<https://github.com/forcedotcom/phoenix>
>>>>> @JamesPlusPlus
>>>>>
>>>>>
>>>

James,

Are you or anyone involved with Phoenix going to be at the Strata conf in
Santa Clara this week ?

regards,
Graeme Wallace
CTO
Farecompare.com
On Tuesday, February 26, 2013, James Taylor wrote:

> Both Phoenix and Impala provide SQL as a way to get at your data. Here are
> some of the high-level similarities and differences I can think of:
> - Phoenix is targeting the support of ANSI SQL, while Impala supports
> HiveQL.
> - Phoenix works with HBase data only, while Impala works with HDFS and
> HBase data.
> - Phoenix is faster against HBase data (take a look at our Performance
> Page here: https://github.com/**forcedotcom/phoenix/wiki/**Performance<https://github.com/forcedotcom/phoenix/wiki/Performance>
> )
> - Both are open source: Phoenix is written in Java while Impala is written
> mostly in C++
> - Phoenix doesn't yet support joins, while Impala does
> - Phoenix doesn't require running additional servers, processes, or
> daemons, while Impala does
>
> Regards,
> James
>
> On 02/26/2013 04:49 AM, Rita wrote:
>
>> Looks great.
>>
>> It seems SQL in Hbase is becoming a trend (not complaining) , how does
>> this
>> compare to Cloudera's Impala
>>
>> On Mon, Feb 25, 2013 at 5:09 PM, Ted Yu <[EMAIL PROTECTED]> wrote:
>>
>>  I ran test suite and they passed:
>>>
>>> Tests run: 452, Failures: 0, Errors: 0, Skipped: 0
>>>
>>> [INFO]
>>> ------------------------------**------------------------------**
>>> ------------
>>> [INFO] BUILD SUCCESS
>>>
>>>
>>> Good job.
>>>
>>> On Mon, Feb 25, 2013 at 9:35 AM, James Taylor <[EMAIL PROTECTED]
>>>
>>>> wrote:
>>>> We are pleased to announce the immediate availability of Phoenix v 1.1,
>>>> with support for HBase v 0.94.4 and above. Phoenix is a SQL layer on top
>>>>
>>> of
>>>
>>>> HBase. For details, see our announcement here:
>>>> http://phoenix-hbase.blogspot.****com/2013/02/annoucing-**phoenix-**
>>>> v-11-support-for.html<
>>>>
>>> http://phoenix-hbase.blogspot.**com/2013/02/annoucing-phoenix-**
>>> v-11-support-for.html<http://phoenix-hbase.blogspot.com/2013/02/annoucing-phoenix-v-11-support-for.html>
>>>
>>>>
>>>> Thanks,
>>>>
>>>> James Taylor
>>>> https://github.com/****forcedotcom/phoenix<https://github.com/**forcedotcom/phoenix>
>>>> <
>>>>
>>> https://github.com/**forcedotcom/phoenix<https://github.com/forcedotcom/phoenix>
>>> >
>>>
>>>> @JamesPlusPlus
>>>>
>>>>
>>
>>
>

--
Graeme Wallace
CTO
FareCompare.com
O: 972 588 1414
M: 214 681 9018

On Tue, Feb 26, 2013 at 10:02 AM, Graeme Wallace <
[EMAIL PROTECTED]> wrote:

> James,
>
> Are you or anyone involved with Phoenix going to be at the Strata conf in
> Santa Clara this week ?
>

You might want to attend the hbase meetup where James will be talking
Phoenix at the Intel Campus near Strata:
http://www.meetup.com/hbaseusergroup/events/96584102/

St.Ack

Cool !!! This is really good. I have a quick question though, is it
possible to use Phoenix over existing tables ? I doubt it but just thought
I will ask it on the list.

On Tue, Feb 26, 2013 at 11:17 AM, Stack <[EMAIL PROTECTED]> wrote:

> On Tue, Feb 26, 2013 at 10:02 AM, Graeme Wallace <
> [EMAIL PROTECTED]> wrote:
>
> > James,
> >
> > Are you or anyone involved with Phoenix going to be at the Strata conf in
> > Santa Clara this week ?
> >
>
> You might want to attend the hbase meetup where James will be talking
> Phoenix at the Intel Campus near Strata:
> http://www.meetup.com/hbaseusergroup/events/96584102/
>
> St.Ack
>

You can query existing tables if the data is serialized in the way that
Phoenix expects.  For more detailed information and options, check out
my response to this issue:
https://github.com/forcedotcom/phoenix/issues/30 and check out our Data
Type language reference here:
http://forcedotcom.github.com/phoenix/datatypes.html

On 02/26/2013 01:08 PM, Viral Bajaria wrote:
> Cool !!! This is really good. I have a quick question though, is it
> possible to use Phoenix over existing tables ? I doubt it but just thought
> I will ask it on the list.
>
> On Tue, Feb 26, 2013 at 11:17 AM, Stack <[EMAIL PROTECTED]> wrote:
>
>> On Tue, Feb 26, 2013 at 10:02 AM, Graeme Wallace <
>> [EMAIL PROTECTED]> wrote:
>>
>>> James,
>>>
>>> Are you or anyone involved with Phoenix going to be at the Strata conf in
>>> Santa Clara this week ?
>>>
>> You might want to attend the hbase meetup where James will be talking
>> Phoenix at the Intel Campus near Strata:
>> http://www.meetup.com/hbaseusergroup/events/96584102/
>>
>> St.Ack
>>

Sweet.
St.Ack
On Mon, Feb 25, 2013 at 9:35 AM, James Taylor <[EMAIL PROTECTED]>wrote:

> We are pleased to announce the immediate availability of Phoenix v 1.1,
> with support for HBase v 0.94.4 and above. Phoenix is a SQL layer on top of
> HBase. For details, see our announcement here:
> http://phoenix-hbase.blogspot.**com/2013/02/annoucing-phoenix-**
> v-11-support-for.html<http://phoenix-hbase.blogspot.com/2013/02/annoucing-phoenix-v-11-support-for.html>
>
> Thanks,
>
> James Taylor
> https://github.com/**forcedotcom/phoenix<https://github.com/forcedotcom/phoenix>
> @JamesPlusPlus
>