Re: [VOTE] Accept Tephra into the Apache Incubator
+1 This message optimized for indexing by NSA PRISM On Fri, Mar 18, 2016 at 2:53 PM, Stack <st...@duboce.net> wrote: > I'm late, but let me add my +1 anyways. > St.Ack > > On Thu, Mar 3, 2016 at 5:29 PM, Poorna Chandra <poo...@apache.org> wrote: > > > Hi All, > > > > Tephra proposal was sent out for discussion last week. The proposal is > > available at https://wiki.apache.org/incubator/TephraProposal > > > > Please vote to accept Tephra into the Apache Incubator. The vote will be > > open for the next 72 hours. > > > > [ ] +1 Accept Tephra as an Apache Incubator podling. > > [ ] +0 Abstain. > > [ ] -1 Don’t accept Tephra as an Apache Incubator podling because ... > > > > Thanks, > > Poorna. > > > > -- > > > > = Abstract = > > > > Tephra is a system for providing globally consistent transactions on > > top of Apache HBase and other storage engines. > > > > = Proposal = > > > > Tephra is a transaction engine for distributed data stores like Apache > > HBase. > > It provides ACID semantics for concurrent data operations that span over > > region > > boundaries in HBase using Optimistic Concurrency Control. > > > > = Background = > > > > HBase provides strong consistency with row- or region-level ACID > > operations. However, it sacrifices cross-region and cross-table > > consistency in favor of scalability. This trade-off requires application > > developers to handle the complexity of ensuring consistency when their > > modifications span region boundaries. By providing support for global > > transactions that span regions, tables, or multiple RPCs, > > Tephra simplifies application development on top of HBase, without a > > significant impact on performance or scalability for many workloads. > > > > Tephra leverages HBase’s native data versioning to provide > multi-versioned > > concurrency control (MVCC) for transactional reads and writes. > > With MVCC capability, each transaction sees its own consistent “snapshot” > > of > > data, providing snapshot isolation of concurrent transactions. > > MVCC along with conflict detection and handling enables Optimistic > > Concurrency > > Control. > > > > Tephra consists of three main components: > > * Transaction Server – maintains global view of transaction state, > assigns > >new transaction IDs and performs conflict detection; > > * Transaction Client – coordinates start, commit, and rollback of > > transactions; and > > * Transaction Processor Coprocessor – applies filtering to the data read > > (based > >on a given transaction’s state) and cleans up any data from old > >(no longer visible) transactions. > > > > Although Tephra only supports HBase now, it can be extended to support > > transactions on any store that has multi-versioning and rollback > > support. The transactions > > can span over multiple stores and storage paradigms. > > > > = Rationale = > > > > Tephra has simple abstractions which can be used by an application to > > add transaction support over HBase. By abstracting away transaction > > handling using Tephra, the application is freed of > > transaction logic, and the application developer can focus on the use > case. > > Also, Tephra can be extended to support transactions on data sources > other > > than HBase. > > > > By making Tephra an Apache open source project, we believe that there > will > > be wider adoption and more opportunities for Tephra to be integrated > > into other Apache projects. > > > > = Current Status = > > > > Tephra was built at Cask Data Inc. initially as part of > > open-source framework Cask Data Application Platform (CDAP) > > [[http://cdap.io/]]. > > It was later converted into an independent open source project with > > Apache 2.0 License [[https://github.com/caskdata/tephra]]. > > > > Tephra is used in CDAP as the transaction engine. As part of CDAP, Tephra > > has been deployed at multiple companies. > > > > Apache Phoenix is using Tephra as transaction engine in the next release. > > > > == Meritocracy == > > > > Our intent with this incubator proposal is to start building a diverse > > developer community around Tephra following the Apache meritocracy model. > > Since Tephra was initially developed in early 2013, we have had fast > > adoption and contributions within Cask Data. We are looking forward to > > new contributors. We wish to build a community based
Re: [VOTE] Accept Tephra into the Apache Incubator
I'm late, but let me add my +1 anyways. St.Ack On Thu, Mar 3, 2016 at 5:29 PM, Poorna Chandra <poo...@apache.org> wrote: > Hi All, > > Tephra proposal was sent out for discussion last week. The proposal is > available at https://wiki.apache.org/incubator/TephraProposal > > Please vote to accept Tephra into the Apache Incubator. The vote will be > open for the next 72 hours. > > [ ] +1 Accept Tephra as an Apache Incubator podling. > [ ] +0 Abstain. > [ ] -1 Don’t accept Tephra as an Apache Incubator podling because ... > > Thanks, > Poorna. > > -- > > = Abstract = > > Tephra is a system for providing globally consistent transactions on > top of Apache HBase and other storage engines. > > = Proposal = > > Tephra is a transaction engine for distributed data stores like Apache > HBase. > It provides ACID semantics for concurrent data operations that span over > region > boundaries in HBase using Optimistic Concurrency Control. > > = Background = > > HBase provides strong consistency with row- or region-level ACID > operations. However, it sacrifices cross-region and cross-table > consistency in favor of scalability. This trade-off requires application > developers to handle the complexity of ensuring consistency when their > modifications span region boundaries. By providing support for global > transactions that span regions, tables, or multiple RPCs, > Tephra simplifies application development on top of HBase, without a > significant impact on performance or scalability for many workloads. > > Tephra leverages HBase’s native data versioning to provide multi-versioned > concurrency control (MVCC) for transactional reads and writes. > With MVCC capability, each transaction sees its own consistent “snapshot” > of > data, providing snapshot isolation of concurrent transactions. > MVCC along with conflict detection and handling enables Optimistic > Concurrency > Control. > > Tephra consists of three main components: > * Transaction Server – maintains global view of transaction state, assigns >new transaction IDs and performs conflict detection; > * Transaction Client – coordinates start, commit, and rollback of > transactions; and > * Transaction Processor Coprocessor – applies filtering to the data read > (based >on a given transaction’s state) and cleans up any data from old >(no longer visible) transactions. > > Although Tephra only supports HBase now, it can be extended to support > transactions on any store that has multi-versioning and rollback > support. The transactions > can span over multiple stores and storage paradigms. > > = Rationale = > > Tephra has simple abstractions which can be used by an application to > add transaction support over HBase. By abstracting away transaction > handling using Tephra, the application is freed of > transaction logic, and the application developer can focus on the use case. > Also, Tephra can be extended to support transactions on data sources other > than HBase. > > By making Tephra an Apache open source project, we believe that there will > be wider adoption and more opportunities for Tephra to be integrated > into other Apache projects. > > = Current Status = > > Tephra was built at Cask Data Inc. initially as part of > open-source framework Cask Data Application Platform (CDAP) > [[http://cdap.io/]]. > It was later converted into an independent open source project with > Apache 2.0 License [[https://github.com/caskdata/tephra]]. > > Tephra is used in CDAP as the transaction engine. As part of CDAP, Tephra > has been deployed at multiple companies. > > Apache Phoenix is using Tephra as transaction engine in the next release. > > == Meritocracy == > > Our intent with this incubator proposal is to start building a diverse > developer community around Tephra following the Apache meritocracy model. > Since Tephra was initially developed in early 2013, we have had fast > adoption and contributions within Cask Data. We are looking forward to > new contributors. We wish to build a community based on Apache's > meritocracy principles, working with those who contribute significantly to > the project and welcoming them to be committers both during the incubation > process and beyond. > > == Community == > > Core developers of Tephra are at Cask Data. Recently the developer > community > has expanded to include folks from Apache Phoenix. We hope to extend our > contributor base significantly and we will invite all who are interested > in working on distributed transaction engine. > > == Core Developers == > > A few engineers from Cask Data and outside have developed Tephra: > Andreas Neumann,
Re: [VOTE] Accept Tephra into the Apache Incubator
+1 (non binding) Regards, Uma On 3/3/16, 5:29 PM, "Poorna Chandra" <poo...@apache.org> wrote: >Hi All, > >Tephra proposal was sent out for discussion last week. The proposal is >available at https://wiki.apache.org/incubator/TephraProposal > >Please vote to accept Tephra into the Apache Incubator. The vote will be >open for the next 72 hours. > >[ ] +1 Accept Tephra as an Apache Incubator podling. >[ ] +0 Abstain. >[ ] -1 Don¹t accept Tephra as an Apache Incubator podling because ... > >Thanks, >Poorna. > >-- > >= Abstract = > >Tephra is a system for providing globally consistent transactions on >top of Apache HBase and other storage engines. > >= Proposal = > >Tephra is a transaction engine for distributed data stores like Apache >HBase. >It provides ACID semantics for concurrent data operations that span over >region >boundaries in HBase using Optimistic Concurrency Control. > >= Background = > >HBase provides strong consistency with row- or region-level ACID >operations. However, it sacrifices cross-region and cross-table >consistency in favor of scalability. This trade-off requires application >developers to handle the complexity of ensuring consistency when their >modifications span region boundaries. By providing support for global >transactions that span regions, tables, or multiple RPCs, >Tephra simplifies application development on top of HBase, without a >significant impact on performance or scalability for many workloads. > >Tephra leverages HBase¹s native data versioning to provide multi-versioned >concurrency control (MVCC) for transactional reads and writes. >With MVCC capability, each transaction sees its own consistent ³snapshot² >of >data, providing snapshot isolation of concurrent transactions. >MVCC along with conflict detection and handling enables Optimistic >Concurrency >Control. > >Tephra consists of three main components: > * Transaction Server maintains global view of transaction state, >assigns > new transaction IDs and performs conflict detection; > * Transaction Client coordinates start, commit, and rollback of >transactions; and > * Transaction Processor Coprocessor applies filtering to the data read >(based > on a given transaction¹s state) and cleans up any data from old > (no longer visible) transactions. > >Although Tephra only supports HBase now, it can be extended to support >transactions on any store that has multi-versioning and rollback >support. The transactions >can span over multiple stores and storage paradigms. > >= Rationale = > >Tephra has simple abstractions which can be used by an application to >add transaction support over HBase. By abstracting away transaction >handling using Tephra, the application is freed of >transaction logic, and the application developer can focus on the use >case. >Also, Tephra can be extended to support transactions on data sources other >than HBase. > >By making Tephra an Apache open source project, we believe that there will >be wider adoption and more opportunities for Tephra to be integrated >into other Apache projects. > >= Current Status = > >Tephra was built at Cask Data Inc. initially as part of >open-source framework Cask Data Application Platform (CDAP) >[[http://cdap.io/]]. >It was later converted into an independent open source project with >Apache 2.0 License [[https://github.com/caskdata/tephra]]. > >Tephra is used in CDAP as the transaction engine. As part of CDAP, Tephra >has been deployed at multiple companies. > >Apache Phoenix is using Tephra as transaction engine in the next release. > >== Meritocracy == > >Our intent with this incubator proposal is to start building a diverse >developer community around Tephra following the Apache meritocracy model. >Since Tephra was initially developed in early 2013, we have had fast >adoption and contributions within Cask Data. We are looking forward to >new contributors. We wish to build a community based on Apache's >meritocracy principles, working with those who contribute significantly to >the project and welcoming them to be committers both during the incubation >process and beyond. > >== Community == > >Core developers of Tephra are at Cask Data. Recently the developer >community >has expanded to include folks from Apache Phoenix. We hope to extend our >contributor base significantly and we will invite all who are interested >in working on distributed transaction engine. > >== Core Developers == > >A few engineers from Cask Data and outside have developed Tephra: >Andreas Neumann, Terence Yim, Gary Helmling, Andrew Purtell and >Poorna Chandra. > > >== Alignment == > &
[RESULT] [VOTE] Accept Tephra into the Apache Incubator
Hi All, Thanks to all who voted! The vote has passed with the following tallies: +1 Binding (7 total) Henry Saputra James Taylor Andrew Purtell Jean-Baptiste Onofré Alan Gates Julian Hyde Lars Hofhansl +1 Non-binding (4 total) Ramakrishna Vasudevan Terence Yim Andreas Neumann Naresh Agarwal We'll work with the mentors to get the project bootstrapped. Thanks, Poorna.
Re: [VOTE] Accept Tephra into the Apache Incubator
+1 (non-binding) Looking forward to this project. Thanks Naresh Agarwal On 7 Mar 2016 02:09, <la...@apache.org> wrote: > +1 (binding) > Exciting! > > From: Poorna Chandra <poo...@apache.org> > To: general@incubator.apache.org > Sent: Thursday, March 3, 2016 5:29 PM > Subject: [VOTE] Accept Tephra into the Apache Incubator > > Hi All, > > Tephra proposal was sent out for discussion last week. The proposal is > available at https://wiki.apache.org/incubator/TephraProposal > > Please vote to accept Tephra into the Apache Incubator. The vote will be > open for the next 72 hours. > > [ ] +1 Accept Tephra as an Apache Incubator podling. > [ ] +0 Abstain. > [ ] -1 Don’t accept Tephra as an Apache Incubator podling because ... > > Thanks, > Poorna. > > -- > > = Abstract = > > Tephra is a system for providing globally consistent transactions on > top of Apache HBase and other storage engines. > > = Proposal = > > Tephra is a transaction engine for distributed data stores like Apache > HBase. > It provides ACID semantics for concurrent data operations that span over > region > boundaries in HBase using Optimistic Concurrency Control. > > = Background = > > HBase provides strong consistency with row- or region-level ACID > operations. However, it sacrifices cross-region and cross-table > consistency in favor of scalability. This trade-off requires application > developers to handle the complexity of ensuring consistency when their > modifications span region boundaries. By providing support for global > transactions that span regions, tables, or multiple RPCs, > Tephra simplifies application development on top of HBase, without a > significant impact on performance or scalability for many workloads. > > Tephra leverages HBase’s native data versioning to provide multi-versioned > concurrency control (MVCC) for transactional reads and writes. > With MVCC capability, each transaction sees its own consistent “snapshot” > of > data, providing snapshot isolation of concurrent transactions. > MVCC along with conflict detection and handling enables Optimistic > Concurrency > Control. > > Tephra consists of three main components: > * Transaction Server – maintains global view of transaction state, assigns > new transaction IDs and performs conflict detection; > * Transaction Client – coordinates start, commit, and rollback of > transactions; and > * Transaction Processor Coprocessor – applies filtering to the data read > (based > on a given transaction’s state) and cleans up any data from old > (no longer visible) transactions. > > Although Tephra only supports HBase now, it can be extended to support > transactions on any store that has multi-versioning and rollback > support. The transactions > can span over multiple stores and storage paradigms. > > = Rationale = > > Tephra has simple abstractions which can be used by an application to > add transaction support over HBase. By abstracting away transaction > handling using Tephra, the application is freed of > transaction logic, and the application developer can focus on the use case. > Also, Tephra can be extended to support transactions on data sources other > than HBase. > > By making Tephra an Apache open source project, we believe that there will > be wider adoption and more opportunities for Tephra to be integrated > into other Apache projects. > > = Current Status = > > Tephra was built at Cask Data Inc. initially as part of > open-source framework Cask Data Application Platform (CDAP) > [[http://cdap.io/]]. > It was later converted into an independent open source project with > Apache 2.0 License [[https://github.com/caskdata/tephra]]. > > Tephra is used in CDAP as the transaction engine. As part of CDAP, Tephra > has been deployed at multiple companies. > > Apache Phoenix is using Tephra as transaction engine in the next release. > > == Meritocracy == > > Our intent with this incubator proposal is to start building a diverse > developer community around Tephra following the Apache meritocracy model. > Since Tephra was initially developed in early 2013, we have had fast > adoption and contributions within Cask Data. We are looking forward to > new contributors. We wish to build a community based on Apache's > meritocracy principles, working with those who contribute significantly to > the project and welcoming them to be committers both during the incubation > process and beyond. > > == Community == > > Core developers of Tephra are at Cask Data. Recently the developer > community > has expanded to include folks from Apache Phoenix. We hope to extend our > contributor base significantly
Re: [VOTE] Accept Tephra into the Apache Incubator
+1 (binding) Exciting! From: Poorna Chandra <poo...@apache.org> To: general@incubator.apache.org Sent: Thursday, March 3, 2016 5:29 PM Subject: [VOTE] Accept Tephra into the Apache Incubator Hi All, Tephra proposal was sent out for discussion last week. The proposal is available at https://wiki.apache.org/incubator/TephraProposal Please vote to accept Tephra into the Apache Incubator. The vote will be open for the next 72 hours. [ ] +1 Accept Tephra as an Apache Incubator podling. [ ] +0 Abstain. [ ] -1 Don’t accept Tephra as an Apache Incubator podling because ... Thanks, Poorna. -- = Abstract = Tephra is a system for providing globally consistent transactions on top of Apache HBase and other storage engines. = Proposal = Tephra is a transaction engine for distributed data stores like Apache HBase. It provides ACID semantics for concurrent data operations that span over region boundaries in HBase using Optimistic Concurrency Control. = Background = HBase provides strong consistency with row- or region-level ACID operations. However, it sacrifices cross-region and cross-table consistency in favor of scalability. This trade-off requires application developers to handle the complexity of ensuring consistency when their modifications span region boundaries. By providing support for global transactions that span regions, tables, or multiple RPCs, Tephra simplifies application development on top of HBase, without a significant impact on performance or scalability for many workloads. Tephra leverages HBase’s native data versioning to provide multi-versioned concurrency control (MVCC) for transactional reads and writes. With MVCC capability, each transaction sees its own consistent “snapshot” of data, providing snapshot isolation of concurrent transactions. MVCC along with conflict detection and handling enables Optimistic Concurrency Control. Tephra consists of three main components: * Transaction Server – maintains global view of transaction state, assigns new transaction IDs and performs conflict detection; * Transaction Client – coordinates start, commit, and rollback of transactions; and * Transaction Processor Coprocessor – applies filtering to the data read (based on a given transaction’s state) and cleans up any data from old (no longer visible) transactions. Although Tephra only supports HBase now, it can be extended to support transactions on any store that has multi-versioning and rollback support. The transactions can span over multiple stores and storage paradigms. = Rationale = Tephra has simple abstractions which can be used by an application to add transaction support over HBase. By abstracting away transaction handling using Tephra, the application is freed of transaction logic, and the application developer can focus on the use case. Also, Tephra can be extended to support transactions on data sources other than HBase. By making Tephra an Apache open source project, we believe that there will be wider adoption and more opportunities for Tephra to be integrated into other Apache projects. = Current Status = Tephra was built at Cask Data Inc. initially as part of open-source framework Cask Data Application Platform (CDAP) [[http://cdap.io/]]. It was later converted into an independent open source project with Apache 2.0 License [[https://github.com/caskdata/tephra]]. Tephra is used in CDAP as the transaction engine. As part of CDAP, Tephra has been deployed at multiple companies. Apache Phoenix is using Tephra as transaction engine in the next release. == Meritocracy == Our intent with this incubator proposal is to start building a diverse developer community around Tephra following the Apache meritocracy model. Since Tephra was initially developed in early 2013, we have had fast adoption and contributions within Cask Data. We are looking forward to new contributors. We wish to build a community based on Apache's meritocracy principles, working with those who contribute significantly to the project and welcoming them to be committers both during the incubation process and beyond. == Community == Core developers of Tephra are at Cask Data. Recently the developer community has expanded to include folks from Apache Phoenix. We hope to extend our contributor base significantly and we will invite all who are interested in working on distributed transaction engine. == Core Developers == A few engineers from Cask Data and outside have developed Tephra: Andreas Neumann, Terence Yim, Gary Helmling, Andrew Purtell and Poorna Chandra. == Alignment == The ASF is the natural choice to host the Tephra project as its goal of encouraging community-driven open source projects fits with our vision for Tephra. Additionally, many other projects with which we are familiar and expect Tephra to integrate with, such as Phoenix, Zookeeper, HDFS, log4j, and others mentioned in the External Dependencies section are Apache projects, and Tephra will benefit by
Re: [VOTE] Accept Tephra into the Apache Incubator
+1 (binding) > On Mar 4, 2016, at 12:57 PM, Alan Gates <alanfga...@gmail.com> wrote: > > +1 (binding). > > Alan. > >> On Mar 3, 2016, at 17:29, Poorna Chandra <poo...@apache.org> wrote: >> >> Hi All, >> >> Tephra proposal was sent out for discussion last week. The proposal is >> available at https://wiki.apache.org/incubator/TephraProposal >> >> Please vote to accept Tephra into the Apache Incubator. The vote will be >> open for the next 72 hours. >> >> [ ] +1 Accept Tephra as an Apache Incubator podling. >> [ ] +0 Abstain. >> [ ] -1 Don’t accept Tephra as an Apache Incubator podling because ... >> >> Thanks, >> Poorna. >> >> -- >> >> = Abstract = >> >> Tephra is a system for providing globally consistent transactions on >> top of Apache HBase and other storage engines. >> >> = Proposal = >> >> Tephra is a transaction engine for distributed data stores like Apache HBase. >> It provides ACID semantics for concurrent data operations that span over >> region >> boundaries in HBase using Optimistic Concurrency Control. >> >> = Background = >> >> HBase provides strong consistency with row- or region-level ACID >> operations. However, it sacrifices cross-region and cross-table >> consistency in favor of scalability. This trade-off requires application >> developers to handle the complexity of ensuring consistency when their >> modifications span region boundaries. By providing support for global >> transactions that span regions, tables, or multiple RPCs, >> Tephra simplifies application development on top of HBase, without a >> significant impact on performance or scalability for many workloads. >> >> Tephra leverages HBase’s native data versioning to provide multi-versioned >> concurrency control (MVCC) for transactional reads and writes. >> With MVCC capability, each transaction sees its own consistent “snapshot” of >> data, providing snapshot isolation of concurrent transactions. >> MVCC along with conflict detection and handling enables Optimistic >> Concurrency >> Control. >> >> Tephra consists of three main components: >> * Transaction Server – maintains global view of transaction state, assigns >> new transaction IDs and performs conflict detection; >> * Transaction Client – coordinates start, commit, and rollback of >> transactions; and >> * Transaction Processor Coprocessor – applies filtering to the data read >> (based >> on a given transaction’s state) and cleans up any data from old >> (no longer visible) transactions. >> >> Although Tephra only supports HBase now, it can be extended to support >> transactions on any store that has multi-versioning and rollback >> support. The transactions >> can span over multiple stores and storage paradigms. >> >> = Rationale = >> >> Tephra has simple abstractions which can be used by an application to >> add transaction support over HBase. By abstracting away transaction >> handling using Tephra, the application is freed of >> transaction logic, and the application developer can focus on the use case. >> Also, Tephra can be extended to support transactions on data sources other >> than HBase. >> >> By making Tephra an Apache open source project, we believe that there will >> be wider adoption and more opportunities for Tephra to be integrated >> into other Apache projects. >> >> = Current Status = >> >> Tephra was built at Cask Data Inc. initially as part of >> open-source framework Cask Data Application Platform (CDAP) >> [[http://cdap.io/]]. >> It was later converted into an independent open source project with >> Apache 2.0 License [[https://github.com/caskdata/tephra]]. >> >> Tephra is used in CDAP as the transaction engine. As part of CDAP, Tephra >> has been deployed at multiple companies. >> >> Apache Phoenix is using Tephra as transaction engine in the next release. >> >> == Meritocracy == >> >> Our intent with this incubator proposal is to start building a diverse >> developer community around Tephra following the Apache meritocracy model. >> Since Tephra was initially developed in early 2013, we have had fast >> adoption and contributions within Cask Data. We are looking forward to >> new contributors. We wish to build a community based on Apache's >> meritocracy principles, working with those who contribute significantly to >> the project and welcoming them to be committers both during the in
Re: [VOTE] Accept Tephra into the Apache Incubator
+1 (binding). Alan. > On Mar 3, 2016, at 17:29, Poorna Chandra <poo...@apache.org> wrote: > > Hi All, > > Tephra proposal was sent out for discussion last week. The proposal is > available at https://wiki.apache.org/incubator/TephraProposal > > Please vote to accept Tephra into the Apache Incubator. The vote will be > open for the next 72 hours. > > [ ] +1 Accept Tephra as an Apache Incubator podling. > [ ] +0 Abstain. > [ ] -1 Don’t accept Tephra as an Apache Incubator podling because ... > > Thanks, > Poorna. > > -- > > = Abstract = > > Tephra is a system for providing globally consistent transactions on > top of Apache HBase and other storage engines. > > = Proposal = > > Tephra is a transaction engine for distributed data stores like Apache HBase. > It provides ACID semantics for concurrent data operations that span over > region > boundaries in HBase using Optimistic Concurrency Control. > > = Background = > > HBase provides strong consistency with row- or region-level ACID > operations. However, it sacrifices cross-region and cross-table > consistency in favor of scalability. This trade-off requires application > developers to handle the complexity of ensuring consistency when their > modifications span region boundaries. By providing support for global > transactions that span regions, tables, or multiple RPCs, > Tephra simplifies application development on top of HBase, without a > significant impact on performance or scalability for many workloads. > > Tephra leverages HBase’s native data versioning to provide multi-versioned > concurrency control (MVCC) for transactional reads and writes. > With MVCC capability, each transaction sees its own consistent “snapshot” of > data, providing snapshot isolation of concurrent transactions. > MVCC along with conflict detection and handling enables Optimistic Concurrency > Control. > > Tephra consists of three main components: > * Transaction Server – maintains global view of transaction state, assigns > new transaction IDs and performs conflict detection; > * Transaction Client – coordinates start, commit, and rollback of > transactions; and > * Transaction Processor Coprocessor – applies filtering to the data read > (based > on a given transaction’s state) and cleans up any data from old > (no longer visible) transactions. > > Although Tephra only supports HBase now, it can be extended to support > transactions on any store that has multi-versioning and rollback > support. The transactions > can span over multiple stores and storage paradigms. > > = Rationale = > > Tephra has simple abstractions which can be used by an application to > add transaction support over HBase. By abstracting away transaction > handling using Tephra, the application is freed of > transaction logic, and the application developer can focus on the use case. > Also, Tephra can be extended to support transactions on data sources other > than HBase. > > By making Tephra an Apache open source project, we believe that there will > be wider adoption and more opportunities for Tephra to be integrated > into other Apache projects. > > = Current Status = > > Tephra was built at Cask Data Inc. initially as part of > open-source framework Cask Data Application Platform (CDAP) > [[http://cdap.io/]]. > It was later converted into an independent open source project with > Apache 2.0 License [[https://github.com/caskdata/tephra]]. > > Tephra is used in CDAP as the transaction engine. As part of CDAP, Tephra > has been deployed at multiple companies. > > Apache Phoenix is using Tephra as transaction engine in the next release. > > == Meritocracy == > > Our intent with this incubator proposal is to start building a diverse > developer community around Tephra following the Apache meritocracy model. > Since Tephra was initially developed in early 2013, we have had fast > adoption and contributions within Cask Data. We are looking forward to > new contributors. We wish to build a community based on Apache's > meritocracy principles, working with those who contribute significantly to > the project and welcoming them to be committers both during the incubation > process and beyond. > > == Community == > > Core developers of Tephra are at Cask Data. Recently the developer community > has expanded to include folks from Apache Phoenix. We hope to extend our > contributor base significantly and we will invite all who are interested > in working on distributed transaction engine. > > == Core Developers == > > A few engineers from Cask Data and outside have developed Tephra: > Andreas Neumann, Terence Yim, Gary Helmling, And
Re: [VOTE] Accept Tephra into the Apache Incubator
+1 (non-binding) -Andreas. On Fri, Mar 4, 2016 at 12:19 PM, Terence Yim <cht...@gmail.com> wrote: > +1 (non-binding) > > Terence > > On Fri, Mar 4, 2016 at 1:13 AM, Jean-Baptiste Onofré <j...@nanthrax.net> > wrote: > > > +1 (binding) > > > > Regards > > JB > > > > > > On 03/04/2016 02:29 AM, Poorna Chandra wrote: > > > >> Hi All, > >> > >> Tephra proposal was sent out for discussion last week. The proposal is > >> available at https://wiki.apache.org/incubator/TephraProposal > >> > >> Please vote to accept Tephra into the Apache Incubator. The vote will be > >> open for the next 72 hours. > >> > >> [ ] +1 Accept Tephra as an Apache Incubator podling. > >> [ ] +0 Abstain. > >> [ ] -1 Don’t accept Tephra as an Apache Incubator podling because ... > >> > >> Thanks, > >> Poorna. > >> > >> -- > >> > >> = Abstract = > >> > >> Tephra is a system for providing globally consistent transactions on > >> top of Apache HBase and other storage engines. > >> > >> = Proposal = > >> > >> Tephra is a transaction engine for distributed data stores like Apache > >> HBase. > >> It provides ACID semantics for concurrent data operations that span over > >> region > >> boundaries in HBase using Optimistic Concurrency Control. > >> > >> = Background = > >> > >> HBase provides strong consistency with row- or region-level ACID > >> operations. However, it sacrifices cross-region and cross-table > >> consistency in favor of scalability. This trade-off requires application > >> developers to handle the complexity of ensuring consistency when their > >> modifications span region boundaries. By providing support for global > >> transactions that span regions, tables, or multiple RPCs, > >> Tephra simplifies application development on top of HBase, without a > >> significant impact on performance or scalability for many workloads. > >> > >> Tephra leverages HBase’s native data versioning to provide > multi-versioned > >> concurrency control (MVCC) for transactional reads and writes. > >> With MVCC capability, each transaction sees its own consistent > “snapshot” > >> of > >> data, providing snapshot isolation of concurrent transactions. > >> MVCC along with conflict detection and handling enables Optimistic > >> Concurrency > >> Control. > >> > >> Tephra consists of three main components: > >> * Transaction Server – maintains global view of transaction state, > >> assigns > >> new transaction IDs and performs conflict detection; > >> * Transaction Client – coordinates start, commit, and rollback of > >> transactions; and > >> * Transaction Processor Coprocessor – applies filtering to the data > >> read (based > >> on a given transaction’s state) and cleans up any data from old > >> (no longer visible) transactions. > >> > >> Although Tephra only supports HBase now, it can be extended to support > >> transactions on any store that has multi-versioning and rollback > >> support. The transactions > >> can span over multiple stores and storage paradigms. > >> > >> = Rationale = > >> > >> Tephra has simple abstractions which can be used by an application to > >> add transaction support over HBase. By abstracting away transaction > >> handling using Tephra, the application is freed of > >> transaction logic, and the application developer can focus on the use > >> case. > >> Also, Tephra can be extended to support transactions on data sources > other > >> than HBase. > >> > >> By making Tephra an Apache open source project, we believe that there > will > >> be wider adoption and more opportunities for Tephra to be integrated > >> into other Apache projects. > >> > >> = Current Status = > >> > >> Tephra was built at Cask Data Inc. initially as part of > >> open-source framework Cask Data Application Platform (CDAP) > >> [[http://cdap.io/]]. > >> It was later converted into an independent open source project with > >> Apache 2.0 License [[https://github.com/caskdata/tephra]]. > >> > >> Tephra is used in CDAP as the transaction engine. As part of CDAP, > Tephra > >> has been deployed at multiple companies. > >> >
Re: [VOTE] Accept Tephra into the Apache Incubator
+1 (non-binding) Terence On Fri, Mar 4, 2016 at 1:13 AM, Jean-Baptiste Onofré <j...@nanthrax.net> wrote: > +1 (binding) > > Regards > JB > > > On 03/04/2016 02:29 AM, Poorna Chandra wrote: > >> Hi All, >> >> Tephra proposal was sent out for discussion last week. The proposal is >> available at https://wiki.apache.org/incubator/TephraProposal >> >> Please vote to accept Tephra into the Apache Incubator. The vote will be >> open for the next 72 hours. >> >> [ ] +1 Accept Tephra as an Apache Incubator podling. >> [ ] +0 Abstain. >> [ ] -1 Don’t accept Tephra as an Apache Incubator podling because ... >> >> Thanks, >> Poorna. >> >> -- >> >> = Abstract = >> >> Tephra is a system for providing globally consistent transactions on >> top of Apache HBase and other storage engines. >> >> = Proposal = >> >> Tephra is a transaction engine for distributed data stores like Apache >> HBase. >> It provides ACID semantics for concurrent data operations that span over >> region >> boundaries in HBase using Optimistic Concurrency Control. >> >> = Background = >> >> HBase provides strong consistency with row- or region-level ACID >> operations. However, it sacrifices cross-region and cross-table >> consistency in favor of scalability. This trade-off requires application >> developers to handle the complexity of ensuring consistency when their >> modifications span region boundaries. By providing support for global >> transactions that span regions, tables, or multiple RPCs, >> Tephra simplifies application development on top of HBase, without a >> significant impact on performance or scalability for many workloads. >> >> Tephra leverages HBase’s native data versioning to provide multi-versioned >> concurrency control (MVCC) for transactional reads and writes. >> With MVCC capability, each transaction sees its own consistent “snapshot” >> of >> data, providing snapshot isolation of concurrent transactions. >> MVCC along with conflict detection and handling enables Optimistic >> Concurrency >> Control. >> >> Tephra consists of three main components: >> * Transaction Server – maintains global view of transaction state, >> assigns >> new transaction IDs and performs conflict detection; >> * Transaction Client – coordinates start, commit, and rollback of >> transactions; and >> * Transaction Processor Coprocessor – applies filtering to the data >> read (based >> on a given transaction’s state) and cleans up any data from old >> (no longer visible) transactions. >> >> Although Tephra only supports HBase now, it can be extended to support >> transactions on any store that has multi-versioning and rollback >> support. The transactions >> can span over multiple stores and storage paradigms. >> >> = Rationale = >> >> Tephra has simple abstractions which can be used by an application to >> add transaction support over HBase. By abstracting away transaction >> handling using Tephra, the application is freed of >> transaction logic, and the application developer can focus on the use >> case. >> Also, Tephra can be extended to support transactions on data sources other >> than HBase. >> >> By making Tephra an Apache open source project, we believe that there will >> be wider adoption and more opportunities for Tephra to be integrated >> into other Apache projects. >> >> = Current Status = >> >> Tephra was built at Cask Data Inc. initially as part of >> open-source framework Cask Data Application Platform (CDAP) >> [[http://cdap.io/]]. >> It was later converted into an independent open source project with >> Apache 2.0 License [[https://github.com/caskdata/tephra]]. >> >> Tephra is used in CDAP as the transaction engine. As part of CDAP, Tephra >> has been deployed at multiple companies. >> >> Apache Phoenix is using Tephra as transaction engine in the next release. >> >> == Meritocracy == >> >> Our intent with this incubator proposal is to start building a diverse >> developer community around Tephra following the Apache meritocracy model. >> Since Tephra was initially developed in early 2013, we have had fast >> adoption and contributions within Cask Data. We are looking forward to >> new contributors. We wish to build a community based on Apache's >> meritocracy principles, working with those who contribute significantly to >> the project and welcoming them to be committers bo
Re: [VOTE] Accept Tephra into the Apache Incubator
+1 (binding) Regards JB On 03/04/2016 02:29 AM, Poorna Chandra wrote: Hi All, Tephra proposal was sent out for discussion last week. The proposal is available at https://wiki.apache.org/incubator/TephraProposal Please vote to accept Tephra into the Apache Incubator. The vote will be open for the next 72 hours. [ ] +1 Accept Tephra as an Apache Incubator podling. [ ] +0 Abstain. [ ] -1 Don’t accept Tephra as an Apache Incubator podling because ... Thanks, Poorna. -- = Abstract = Tephra is a system for providing globally consistent transactions on top of Apache HBase and other storage engines. = Proposal = Tephra is a transaction engine for distributed data stores like Apache HBase. It provides ACID semantics for concurrent data operations that span over region boundaries in HBase using Optimistic Concurrency Control. = Background = HBase provides strong consistency with row- or region-level ACID operations. However, it sacrifices cross-region and cross-table consistency in favor of scalability. This trade-off requires application developers to handle the complexity of ensuring consistency when their modifications span region boundaries. By providing support for global transactions that span regions, tables, or multiple RPCs, Tephra simplifies application development on top of HBase, without a significant impact on performance or scalability for many workloads. Tephra leverages HBase’s native data versioning to provide multi-versioned concurrency control (MVCC) for transactional reads and writes. With MVCC capability, each transaction sees its own consistent “snapshot” of data, providing snapshot isolation of concurrent transactions. MVCC along with conflict detection and handling enables Optimistic Concurrency Control. Tephra consists of three main components: * Transaction Server – maintains global view of transaction state, assigns new transaction IDs and performs conflict detection; * Transaction Client – coordinates start, commit, and rollback of transactions; and * Transaction Processor Coprocessor – applies filtering to the data read (based on a given transaction’s state) and cleans up any data from old (no longer visible) transactions. Although Tephra only supports HBase now, it can be extended to support transactions on any store that has multi-versioning and rollback support. The transactions can span over multiple stores and storage paradigms. = Rationale = Tephra has simple abstractions which can be used by an application to add transaction support over HBase. By abstracting away transaction handling using Tephra, the application is freed of transaction logic, and the application developer can focus on the use case. Also, Tephra can be extended to support transactions on data sources other than HBase. By making Tephra an Apache open source project, we believe that there will be wider adoption and more opportunities for Tephra to be integrated into other Apache projects. = Current Status = Tephra was built at Cask Data Inc. initially as part of open-source framework Cask Data Application Platform (CDAP) [[http://cdap.io/]]. It was later converted into an independent open source project with Apache 2.0 License [[https://github.com/caskdata/tephra]]. Tephra is used in CDAP as the transaction engine. As part of CDAP, Tephra has been deployed at multiple companies. Apache Phoenix is using Tephra as transaction engine in the next release. == Meritocracy == Our intent with this incubator proposal is to start building a diverse developer community around Tephra following the Apache meritocracy model. Since Tephra was initially developed in early 2013, we have had fast adoption and contributions within Cask Data. We are looking forward to new contributors. We wish to build a community based on Apache's meritocracy principles, working with those who contribute significantly to the project and welcoming them to be committers both during the incubation process and beyond. == Community == Core developers of Tephra are at Cask Data. Recently the developer community has expanded to include folks from Apache Phoenix. We hope to extend our contributor base significantly and we will invite all who are interested in working on distributed transaction engine. == Core Developers == A few engineers from Cask Data and outside have developed Tephra: Andreas Neumann, Terence Yim, Gary Helmling, Andrew Purtell and Poorna Chandra. == Alignment == The ASF is the natural choice to host the Tephra project as its goal of encouraging community-driven open source projects fits with our vision for Tephra. Additionally, many other projects with which we are familiar and expect Tephra to integrate with, such as Phoenix, Zookeeper, HDFS, log4j, and others mentioned in the External Dependencies section are Apache projects, and Tephra will benefit by close proximity to them. = Known Risks = == Orphaned Products == There is very little risk of Tephra being orphaned
RE: [VOTE] Accept Tephra into the Apache Incubator
+1 (non-binding) Regards Ram -Original Message- From: Andrew Purtell [mailto:andrew.purt...@gmail.com] Sent: Friday, March 4, 2016 11:55 AM To: general@incubator.apache.org Subject: Re: [VOTE] Accept Tephra into the Apache Incubator +1 (binding) > On Mar 3, 2016, at 5:29 PM, Poorna Chandra <poo...@apache.org> wrote: > > Hi All, > > Tephra proposal was sent out for discussion last week. The proposal is > available at https://wiki.apache.org/incubator/TephraProposal > > Please vote to accept Tephra into the Apache Incubator. The vote will > be open for the next 72 hours. > > [ ] +1 Accept Tephra as an Apache Incubator podling. > [ ] +0 Abstain. > [ ] -1 Don’t accept Tephra as an Apache Incubator podling because ... > > Thanks, > Poorna. > > -- > > = Abstract = > > Tephra is a system for providing globally consistent transactions on > top of Apache HBase and other storage engines. > > = Proposal = > > Tephra is a transaction engine for distributed data stores like Apache HBase. > It provides ACID semantics for concurrent data operations that span > over region boundaries in HBase using Optimistic Concurrency Control. > > = Background = > > HBase provides strong consistency with row- or region-level ACID > operations. However, it sacrifices cross-region and cross-table > consistency in favor of scalability. This trade-off requires > application developers to handle the complexity of ensuring > consistency when their modifications span region boundaries. By > providing support for global transactions that span regions, tables, > or multiple RPCs, Tephra simplifies application development on top of > HBase, without a significant impact on performance or scalability for many > workloads. > > Tephra leverages HBase’s native data versioning to provide > multi-versioned concurrency control (MVCC) for transactional reads and writes. > With MVCC capability, each transaction sees its own consistent > “snapshot” of data, providing snapshot isolation of concurrent transactions. > MVCC along with conflict detection and handling enables Optimistic > Concurrency Control. > > Tephra consists of three main components: > * Transaction Server – maintains global view of transaction state, assigns > new transaction IDs and performs conflict detection; > * Transaction Client – coordinates start, commit, and rollback of > transactions; and > * Transaction Processor Coprocessor – applies filtering to the data read > (based > on a given transaction’s state) and cleans up any data from old > (no longer visible) transactions. > > Although Tephra only supports HBase now, it can be extended to support > transactions on any store that has multi-versioning and rollback > support. The transactions can span over multiple stores and storage > paradigms. > > = Rationale = > > Tephra has simple abstractions which can be used by an application to > add transaction support over HBase. By abstracting away transaction > handling using Tephra, the application is freed of transaction logic, > and the application developer can focus on the use case. > Also, Tephra can be extended to support transactions on data sources > other than HBase. > > By making Tephra an Apache open source project, we believe that there > will be wider adoption and more opportunities for Tephra to be > integrated into other Apache projects. > > = Current Status = > > Tephra was built at Cask Data Inc. initially as part of open-source > framework Cask Data Application Platform (CDAP) [[http://cdap.io/]]. > It was later converted into an independent open source project with > Apache 2.0 License [[https://github.com/caskdata/tephra]]. > > Tephra is used in CDAP as the transaction engine. As part of CDAP, > Tephra has been deployed at multiple companies. > > Apache Phoenix is using Tephra as transaction engine in the next release. > > == Meritocracy == > > Our intent with this incubator proposal is to start building a diverse > developer community around Tephra following the Apache meritocracy model. > Since Tephra was initially developed in early 2013, we have had fast > adoption and contributions within Cask Data. We are looking forward to > new contributors. We wish to build a community based on Apache's > meritocracy principles, working with those who contribute > significantly to the project and welcoming them to be committers both > during the incubation process and beyond. > > == Community == > > Core developers of Tephra are at Cask Data. Recently the developer > community has expanded to include folks from Apache Phoenix. We hope > to extend our contributor base sig
RE: [VOTE] Accept Tephra into the Apache Incubator
+1(non-binding) Regards Ram -Original Message- From: Andrew Purtell [mailto:andrew.purt...@gmail.com] Sent: Friday, March 4, 2016 11:55 AM To: general@incubator.apache.org Subject: Re: [VOTE] Accept Tephra into the Apache Incubator +1 (binding) > On Mar 3, 2016, at 5:29 PM, Poorna Chandra <poo...@apache.org> wrote: > > Hi All, > > Tephra proposal was sent out for discussion last week. The proposal is > available at https://wiki.apache.org/incubator/TephraProposal > > Please vote to accept Tephra into the Apache Incubator. The vote will > be open for the next 72 hours. > > [ ] +1 Accept Tephra as an Apache Incubator podling. > [ ] +0 Abstain. > [ ] -1 Don’t accept Tephra as an Apache Incubator podling because ... > > Thanks, > Poorna. > > -- > > = Abstract = > > Tephra is a system for providing globally consistent transactions on > top of Apache HBase and other storage engines. > > = Proposal = > > Tephra is a transaction engine for distributed data stores like Apache HBase. > It provides ACID semantics for concurrent data operations that span > over region boundaries in HBase using Optimistic Concurrency Control. > > = Background = > > HBase provides strong consistency with row- or region-level ACID > operations. However, it sacrifices cross-region and cross-table > consistency in favor of scalability. This trade-off requires > application developers to handle the complexity of ensuring > consistency when their modifications span region boundaries. By > providing support for global transactions that span regions, tables, > or multiple RPCs, Tephra simplifies application development on top of > HBase, without a significant impact on performance or scalability for many > workloads. > > Tephra leverages HBase’s native data versioning to provide > multi-versioned concurrency control (MVCC) for transactional reads and writes. > With MVCC capability, each transaction sees its own consistent > “snapshot” of data, providing snapshot isolation of concurrent transactions. > MVCC along with conflict detection and handling enables Optimistic > Concurrency Control. > > Tephra consists of three main components: > * Transaction Server – maintains global view of transaction state, assigns > new transaction IDs and performs conflict detection; > * Transaction Client – coordinates start, commit, and rollback of > transactions; and > * Transaction Processor Coprocessor – applies filtering to the data read > (based > on a given transaction’s state) and cleans up any data from old > (no longer visible) transactions. > > Although Tephra only supports HBase now, it can be extended to support > transactions on any store that has multi-versioning and rollback > support. The transactions can span over multiple stores and storage > paradigms. > > = Rationale = > > Tephra has simple abstractions which can be used by an application to > add transaction support over HBase. By abstracting away transaction > handling using Tephra, the application is freed of transaction logic, > and the application developer can focus on the use case. > Also, Tephra can be extended to support transactions on data sources > other than HBase. > > By making Tephra an Apache open source project, we believe that there > will be wider adoption and more opportunities for Tephra to be > integrated into other Apache projects. > > = Current Status = > > Tephra was built at Cask Data Inc. initially as part of open-source > framework Cask Data Application Platform (CDAP) [[http://cdap.io/]]. > It was later converted into an independent open source project with > Apache 2.0 License [[https://github.com/caskdata/tephra]]. > > Tephra is used in CDAP as the transaction engine. As part of CDAP, > Tephra has been deployed at multiple companies. > > Apache Phoenix is using Tephra as transaction engine in the next release. > > == Meritocracy == > > Our intent with this incubator proposal is to start building a diverse > developer community around Tephra following the Apache meritocracy model. > Since Tephra was initially developed in early 2013, we have had fast > adoption and contributions within Cask Data. We are looking forward to > new contributors. We wish to build a community based on Apache's > meritocracy principles, working with those who contribute > significantly to the project and welcoming them to be committers both > during the incubation process and beyond. > > == Community == > > Core developers of Tephra are at Cask Data. Recently the developer > community has expanded to include folks from Apache Phoenix. We hope > to extend our contributor base sig
Re: [VOTE] Accept Tephra into the Apache Incubator
+1 (binding) > On Mar 3, 2016, at 5:29 PM, Poorna Chandra <poo...@apache.org> wrote: > > Hi All, > > Tephra proposal was sent out for discussion last week. The proposal is > available at https://wiki.apache.org/incubator/TephraProposal > > Please vote to accept Tephra into the Apache Incubator. The vote will be > open for the next 72 hours. > > [ ] +1 Accept Tephra as an Apache Incubator podling. > [ ] +0 Abstain. > [ ] -1 Don’t accept Tephra as an Apache Incubator podling because ... > > Thanks, > Poorna. > > -- > > = Abstract = > > Tephra is a system for providing globally consistent transactions on > top of Apache HBase and other storage engines. > > = Proposal = > > Tephra is a transaction engine for distributed data stores like Apache HBase. > It provides ACID semantics for concurrent data operations that span over > region > boundaries in HBase using Optimistic Concurrency Control. > > = Background = > > HBase provides strong consistency with row- or region-level ACID > operations. However, it sacrifices cross-region and cross-table > consistency in favor of scalability. This trade-off requires application > developers to handle the complexity of ensuring consistency when their > modifications span region boundaries. By providing support for global > transactions that span regions, tables, or multiple RPCs, > Tephra simplifies application development on top of HBase, without a > significant impact on performance or scalability for many workloads. > > Tephra leverages HBase’s native data versioning to provide multi-versioned > concurrency control (MVCC) for transactional reads and writes. > With MVCC capability, each transaction sees its own consistent “snapshot” of > data, providing snapshot isolation of concurrent transactions. > MVCC along with conflict detection and handling enables Optimistic Concurrency > Control. > > Tephra consists of three main components: > * Transaction Server – maintains global view of transaction state, assigns > new transaction IDs and performs conflict detection; > * Transaction Client – coordinates start, commit, and rollback of > transactions; and > * Transaction Processor Coprocessor – applies filtering to the data read > (based > on a given transaction’s state) and cleans up any data from old > (no longer visible) transactions. > > Although Tephra only supports HBase now, it can be extended to support > transactions on any store that has multi-versioning and rollback > support. The transactions > can span over multiple stores and storage paradigms. > > = Rationale = > > Tephra has simple abstractions which can be used by an application to > add transaction support over HBase. By abstracting away transaction > handling using Tephra, the application is freed of > transaction logic, and the application developer can focus on the use case. > Also, Tephra can be extended to support transactions on data sources other > than HBase. > > By making Tephra an Apache open source project, we believe that there will > be wider adoption and more opportunities for Tephra to be integrated > into other Apache projects. > > = Current Status = > > Tephra was built at Cask Data Inc. initially as part of > open-source framework Cask Data Application Platform (CDAP) > [[http://cdap.io/]]. > It was later converted into an independent open source project with > Apache 2.0 License [[https://github.com/caskdata/tephra]]. > > Tephra is used in CDAP as the transaction engine. As part of CDAP, Tephra > has been deployed at multiple companies. > > Apache Phoenix is using Tephra as transaction engine in the next release. > > == Meritocracy == > > Our intent with this incubator proposal is to start building a diverse > developer community around Tephra following the Apache meritocracy model. > Since Tephra was initially developed in early 2013, we have had fast > adoption and contributions within Cask Data. We are looking forward to > new contributors. We wish to build a community based on Apache's > meritocracy principles, working with those who contribute significantly to > the project and welcoming them to be committers both during the incubation > process and beyond. > > == Community == > > Core developers of Tephra are at Cask Data. Recently the developer community > has expanded to include folks from Apache Phoenix. We hope to extend our > contributor base significantly and we will invite all who are interested > in working on distributed transaction engine. > > == Core Developers == > > A few engineers from Cask Data and outside have developed Tephra: > Andreas Neumann, Terence Yim, Gary Helmling, Andrew Purtell
Re: [VOTE] Accept Tephra into the Apache Incubator
+1 (binding) On Thursday, March 3, 2016, Henry Saputra <henry.sapu...@gmail.com> wrote: > +1 (binding) > > On Thu, Mar 3, 2016 at 5:29 PM, Poorna Chandra <poo...@apache.org > <javascript:;>> wrote: > > > Hi All, > > > > Tephra proposal was sent out for discussion last week. The proposal is > > available at https://wiki.apache.org/incubator/TephraProposal > > > > Please vote to accept Tephra into the Apache Incubator. The vote will be > > open for the next 72 hours. > > > > [ ] +1 Accept Tephra as an Apache Incubator podling. > > [ ] +0 Abstain. > > [ ] -1 Don’t accept Tephra as an Apache Incubator podling because ... > > > > Thanks, > > Poorna. > > > > -- > > > > = Abstract = > > > > Tephra is a system for providing globally consistent transactions on > > top of Apache HBase and other storage engines. > > > > = Proposal = > > > > Tephra is a transaction engine for distributed data stores like Apache > > HBase. > > It provides ACID semantics for concurrent data operations that span over > > region > > boundaries in HBase using Optimistic Concurrency Control. > > > > = Background = > > > > HBase provides strong consistency with row- or region-level ACID > > operations. However, it sacrifices cross-region and cross-table > > consistency in favor of scalability. This trade-off requires application > > developers to handle the complexity of ensuring consistency when their > > modifications span region boundaries. By providing support for global > > transactions that span regions, tables, or multiple RPCs, > > Tephra simplifies application development on top of HBase, without a > > significant impact on performance or scalability for many workloads. > > > > Tephra leverages HBase’s native data versioning to provide > multi-versioned > > concurrency control (MVCC) for transactional reads and writes. > > With MVCC capability, each transaction sees its own consistent “snapshot” > > of > > data, providing snapshot isolation of concurrent transactions. > > MVCC along with conflict detection and handling enables Optimistic > > Concurrency > > Control. > > > > Tephra consists of three main components: > > * Transaction Server – maintains global view of transaction state, > assigns > >new transaction IDs and performs conflict detection; > > * Transaction Client – coordinates start, commit, and rollback of > > transactions; and > > * Transaction Processor Coprocessor – applies filtering to the data read > > (based > >on a given transaction’s state) and cleans up any data from old > >(no longer visible) transactions. > > > > Although Tephra only supports HBase now, it can be extended to support > > transactions on any store that has multi-versioning and rollback > > support. The transactions > > can span over multiple stores and storage paradigms. > > > > = Rationale = > > > > Tephra has simple abstractions which can be used by an application to > > add transaction support over HBase. By abstracting away transaction > > handling using Tephra, the application is freed of > > transaction logic, and the application developer can focus on the use > case. > > Also, Tephra can be extended to support transactions on data sources > other > > than HBase. > > > > By making Tephra an Apache open source project, we believe that there > will > > be wider adoption and more opportunities for Tephra to be integrated > > into other Apache projects. > > > > = Current Status = > > > > Tephra was built at Cask Data Inc. initially as part of > > open-source framework Cask Data Application Platform (CDAP) > > [[http://cdap.io/]]. > > It was later converted into an independent open source project with > > Apache 2.0 License [[https://github.com/caskdata/tephra]]. > > > > Tephra is used in CDAP as the transaction engine. As part of CDAP, Tephra > > has been deployed at multiple companies. > > > > Apache Phoenix is using Tephra as transaction engine in the next release. > > > > == Meritocracy == > > > > Our intent with this incubator proposal is to start building a diverse > > developer community around Tephra following the Apache meritocracy model. > > Since Tephra was initially developed in early 2013, we have had fast > > adoption and contributions within Cask Data. We are looking forward to > > new contributors. We wish to build a community based on Apache's > > meritocracy principles,
Re: [VOTE] Accept Tephra into the Apache Incubator
+1 (binding) On Thu, Mar 3, 2016 at 5:29 PM, Poorna Chandra <poo...@apache.org> wrote: > Hi All, > > Tephra proposal was sent out for discussion last week. The proposal is > available at https://wiki.apache.org/incubator/TephraProposal > > Please vote to accept Tephra into the Apache Incubator. The vote will be > open for the next 72 hours. > > [ ] +1 Accept Tephra as an Apache Incubator podling. > [ ] +0 Abstain. > [ ] -1 Don’t accept Tephra as an Apache Incubator podling because ... > > Thanks, > Poorna. > > -- > > = Abstract = > > Tephra is a system for providing globally consistent transactions on > top of Apache HBase and other storage engines. > > = Proposal = > > Tephra is a transaction engine for distributed data stores like Apache > HBase. > It provides ACID semantics for concurrent data operations that span over > region > boundaries in HBase using Optimistic Concurrency Control. > > = Background = > > HBase provides strong consistency with row- or region-level ACID > operations. However, it sacrifices cross-region and cross-table > consistency in favor of scalability. This trade-off requires application > developers to handle the complexity of ensuring consistency when their > modifications span region boundaries. By providing support for global > transactions that span regions, tables, or multiple RPCs, > Tephra simplifies application development on top of HBase, without a > significant impact on performance or scalability for many workloads. > > Tephra leverages HBase’s native data versioning to provide multi-versioned > concurrency control (MVCC) for transactional reads and writes. > With MVCC capability, each transaction sees its own consistent “snapshot” > of > data, providing snapshot isolation of concurrent transactions. > MVCC along with conflict detection and handling enables Optimistic > Concurrency > Control. > > Tephra consists of three main components: > * Transaction Server – maintains global view of transaction state, assigns >new transaction IDs and performs conflict detection; > * Transaction Client – coordinates start, commit, and rollback of > transactions; and > * Transaction Processor Coprocessor – applies filtering to the data read > (based >on a given transaction’s state) and cleans up any data from old >(no longer visible) transactions. > > Although Tephra only supports HBase now, it can be extended to support > transactions on any store that has multi-versioning and rollback > support. The transactions > can span over multiple stores and storage paradigms. > > = Rationale = > > Tephra has simple abstractions which can be used by an application to > add transaction support over HBase. By abstracting away transaction > handling using Tephra, the application is freed of > transaction logic, and the application developer can focus on the use case. > Also, Tephra can be extended to support transactions on data sources other > than HBase. > > By making Tephra an Apache open source project, we believe that there will > be wider adoption and more opportunities for Tephra to be integrated > into other Apache projects. > > = Current Status = > > Tephra was built at Cask Data Inc. initially as part of > open-source framework Cask Data Application Platform (CDAP) > [[http://cdap.io/]]. > It was later converted into an independent open source project with > Apache 2.0 License [[https://github.com/caskdata/tephra]]. > > Tephra is used in CDAP as the transaction engine. As part of CDAP, Tephra > has been deployed at multiple companies. > > Apache Phoenix is using Tephra as transaction engine in the next release. > > == Meritocracy == > > Our intent with this incubator proposal is to start building a diverse > developer community around Tephra following the Apache meritocracy model. > Since Tephra was initially developed in early 2013, we have had fast > adoption and contributions within Cask Data. We are looking forward to > new contributors. We wish to build a community based on Apache's > meritocracy principles, working with those who contribute significantly to > the project and welcoming them to be committers both during the incubation > process and beyond. > > == Community == > > Core developers of Tephra are at Cask Data. Recently the developer > community > has expanded to include folks from Apache Phoenix. We hope to extend our > contributor base significantly and we will invite all who are interested > in working on distributed transaction engine. > > == Core Developers == > > A few engineers from Cask Data and outside have developed Tephra: > Andreas Neumann, Terence Yim, Gary Helmling, Andrew Purtell an
[VOTE] Accept Tephra into the Apache Incubator
Hi All, Tephra proposal was sent out for discussion last week. The proposal is available at https://wiki.apache.org/incubator/TephraProposal Please vote to accept Tephra into the Apache Incubator. The vote will be open for the next 72 hours. [ ] +1 Accept Tephra as an Apache Incubator podling. [ ] +0 Abstain. [ ] -1 Don’t accept Tephra as an Apache Incubator podling because ... Thanks, Poorna. -- = Abstract = Tephra is a system for providing globally consistent transactions on top of Apache HBase and other storage engines. = Proposal = Tephra is a transaction engine for distributed data stores like Apache HBase. It provides ACID semantics for concurrent data operations that span over region boundaries in HBase using Optimistic Concurrency Control. = Background = HBase provides strong consistency with row- or region-level ACID operations. However, it sacrifices cross-region and cross-table consistency in favor of scalability. This trade-off requires application developers to handle the complexity of ensuring consistency when their modifications span region boundaries. By providing support for global transactions that span regions, tables, or multiple RPCs, Tephra simplifies application development on top of HBase, without a significant impact on performance or scalability for many workloads. Tephra leverages HBase’s native data versioning to provide multi-versioned concurrency control (MVCC) for transactional reads and writes. With MVCC capability, each transaction sees its own consistent “snapshot” of data, providing snapshot isolation of concurrent transactions. MVCC along with conflict detection and handling enables Optimistic Concurrency Control. Tephra consists of three main components: * Transaction Server – maintains global view of transaction state, assigns new transaction IDs and performs conflict detection; * Transaction Client – coordinates start, commit, and rollback of transactions; and * Transaction Processor Coprocessor – applies filtering to the data read (based on a given transaction’s state) and cleans up any data from old (no longer visible) transactions. Although Tephra only supports HBase now, it can be extended to support transactions on any store that has multi-versioning and rollback support. The transactions can span over multiple stores and storage paradigms. = Rationale = Tephra has simple abstractions which can be used by an application to add transaction support over HBase. By abstracting away transaction handling using Tephra, the application is freed of transaction logic, and the application developer can focus on the use case. Also, Tephra can be extended to support transactions on data sources other than HBase. By making Tephra an Apache open source project, we believe that there will be wider adoption and more opportunities for Tephra to be integrated into other Apache projects. = Current Status = Tephra was built at Cask Data Inc. initially as part of open-source framework Cask Data Application Platform (CDAP) [[http://cdap.io/]]. It was later converted into an independent open source project with Apache 2.0 License [[https://github.com/caskdata/tephra]]. Tephra is used in CDAP as the transaction engine. As part of CDAP, Tephra has been deployed at multiple companies. Apache Phoenix is using Tephra as transaction engine in the next release. == Meritocracy == Our intent with this incubator proposal is to start building a diverse developer community around Tephra following the Apache meritocracy model. Since Tephra was initially developed in early 2013, we have had fast adoption and contributions within Cask Data. We are looking forward to new contributors. We wish to build a community based on Apache's meritocracy principles, working with those who contribute significantly to the project and welcoming them to be committers both during the incubation process and beyond. == Community == Core developers of Tephra are at Cask Data. Recently the developer community has expanded to include folks from Apache Phoenix. We hope to extend our contributor base significantly and we will invite all who are interested in working on distributed transaction engine. == Core Developers == A few engineers from Cask Data and outside have developed Tephra: Andreas Neumann, Terence Yim, Gary Helmling, Andrew Purtell and Poorna Chandra. == Alignment == The ASF is the natural choice to host the Tephra project as its goal of encouraging community-driven open source projects fits with our vision for Tephra. Additionally, many other projects with which we are familiar and expect Tephra to integrate with, such as Phoenix, Zookeeper, HDFS, log4j, and others mentioned in the External Dependencies section are Apache projects, and Tephra will benefit by close proximity to them. = Known Risks = == Orphaned Products == There is very little risk of Tephra being orphaned, as it is a key part of Cask Data’s products. The core Tephra developers plan to continue
