|
James Taylor
2013-01-30, 21:04
Stack
2013-01-30, 21:23
Gary Helmling
2013-01-30, 21:42
Andrew Purtell
2013-01-30, 21:50
Enis Söztutar
2013-01-30, 22:45
Devaraj Das
2013-01-30, 22:58
Huanyou Chang
2013-01-31, 01:55
Viral Bajaria
2013-01-31, 02:15
James Taylor
2013-02-01, 16:49
|
-
Announcing Phoenix: A SQL layer over HBaseJames Taylor 2013-01-30, 21:04
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
-
Re: Announcing Phoenix: A SQL layer over HBaseStack 2013-01-30, 21:23
Congrats lads!
St.Ack 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<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<https://groups.google.com/forum/#!forum/phoenix-hbase-user> > Phoenix HBase Dev: https://groups.google.com/** > forum/#!forum/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<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 >
-
Re: Announcing Phoenix: A SQL layer over HBaseGary Helmling 2013-01-30, 21:42
Great stuff! I've been waiting for this. Congrats on open sourcing and
thanks for sharing! 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<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<https://groups.google.com/forum/#!forum/phoenix-hbase-user> > Phoenix HBase Dev: https://groups.google.com/** > forum/#!forum/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<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 >
-
Re: Announcing Phoenix: A SQL layer over HBaseAndrew Purtell 2013-01-30, 21:50
Wow.
Thanks so much for open sourcing this. 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<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<https://groups.google.com/forum/#!forum/phoenix-hbase-user> > Phoenix HBase Dev: https://groups.google.com/** > forum/#!forum/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<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 > -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
-
Re: Announcing Phoenix: A SQL layer over HBaseEnis Söztutar 2013-01-30, 22:45
Cool. Will play a bit later on. Was waiting for it to appear.
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<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<https://groups.google.com/forum/#!forum/phoenix-hbase-user> > Phoenix HBase Dev: https://groups.google.com/** > forum/#!forum/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<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 >
-
Re: Announcing Phoenix: A SQL layer over HBaseDevaraj Das 2013-01-30, 22:58
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
-
Re: Announcing Phoenix: A SQL layer over HBaseHuanyou Chang 2013-01-31, 01:55
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 >
-
Re: Announcing Phoenix: A SQL layer over HBaseViral Bajaria 2013-01-31, 02:15
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 > > >
-
Re: Announcing Phoenix: A SQL layer over HBaseJames Taylor 2013-02-01, 16:49
Thanks, everyone, and sorry to keep you waiting :-)
We're using Phoenix in lots of different use cases and product areas at Salesforce: Product Metrics Data Archival Server Metrics and Monitoring Trending over time-series data Reporting I'll go into more detail on a future post at my blog: http://phoenix-hbase.blogspot.com. Was thinking to start with the topic of "Performance Tuning of Phoenix (i.e. what are all the knobs and dials)", then "How to add your own built-in function". I folks have other topics of interest drop me a line over there. Regards, James On 01/30/2013 06:15 PM, Viral Bajaria wrote: > 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 |