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
