Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
HBase >> mail # user >> Announcing Phoenix: A SQL layer over HBase


Copy link to this message
-
Re: Announcing Phoenix: A SQL layer over HBase
Congrats guys !!! This is something that was sorely missing in what I am
trying to build... will definitely try it out... just out of curiosity,
what kind of projects/tools at SalesForce uses this library ?

On Wed, Jan 30, 2013 at 5:55 PM, Huanyou Chang <[EMAIL PROTECTED]>wrote:

> Great tool,I will try it later. thanks for sharing!
>
>
> 2013/1/31 Devaraj Das <[EMAIL PROTECTED]>
>
> > Congratulations, James. We will surely benefit from this tool.
> >
> > On Wed, Jan 30, 2013 at 1:04 PM, James Taylor <[EMAIL PROTECTED]>
> > wrote:
> > > We are pleased to announce the immediate availability of a new open
> > source
> > > project, Phoenix, a SQL layer over HBase that powers the HBase use
> cases
> > at
> > > Salesforce.com. We put the SQL back in the NoSQL:
> > >
> > >  * Available on GitHub at https://github.com/forcedotcom/phoenix
> > >  * Embedded JDBC driver implements the majority of java.sql interfaces,
> > >    including the metadata APIs.
> > >  * Built for low latency queries through parallelization, the use of
> > >    native HBase APIs, coprocessors, and custom filters.
> > >  * Allows columns to be modelled as a multi-part row key or key/value
> > >    cells.
> > >  * Full query support with predicate push down and optimal scan key
> > >    formation.
> > >  * DDL support: CREATE TABLE, DROP TABLE, and ALTER TABLE for
> > >    adding/removing columns.
> > >  * Versioned schema repository. Snapshot queries use the schema that
> > >    was in place when data was written.
> > >  * DML support: UPSERT VALUES for row-by-row insertion, UPSERT SELECT
> > >    for mass data transfer between the same or different tables, and
> > >    DELETE for deleting rows.
> > >  * Limited transaction support through client-side batching.
> > >  * Single table only - no joins yet and secondary indexes are a work in
> > >    progress.
> > >  * Follows ANSI SQL standards whenever possible
> > >  * Requires HBase v 0.94.2 or above
> > >  * BSD-like license
> > >  * 100% Java
> > >
> > > Join our user groups:
> > >     Phoenix HBase User:
> > > https://groups.google.com/forum/#!forum/phoenix-hbase-user
> > >     Phoenix HBase Dev:
> > > https://groups.google.com/forum/#!forum/phoenix-hbase-dev
> > > and check out our roadmap:
> > > https://github.com/forcedotcom/phoenix/wiki#wiki-roadmap
> > >
> > > We welcome feedback and contributions from the community to Phoenix and
> > look
> > > forward to working together.
> > >
> > > Regards,
> > >
> > > James Taylor
> > > @JamesPlusPlus
> >
>