Re: [VOTE] Release of Apache Tephra-0.9.0-incubating [rc1]

[larsh]

+1
- Built from v0.9.0-incubating tag.- ran tests. All pass.- all good
-- Lars

  From: Poorna Chandra 
 To: general@incubator.apache.org 
 Sent: Thursday, September 15, 2016 10:44 PM
 Subject: [VOTE] Release of Apache Tephra-0.9.0-incubating [rc1]
   
Hi all,

This is a call for a vote on releasing Apache Tephra 0.9.0-incubating,
release candidate 1. This is the second release of Tephra.

Apache Tephra community has voted and approved the release.

Vote thread:
http://mail-archives.apache.org/mod_mbox/incubator-tephra-dev/201609.mbox/%3CCAC9o21R4KR-e%3DmzCsefvokpQWykOXTTnWt%2BZwt0CjiZz1MsqAg%40mail.gmail.com%3E

Result thread:
http://mail-archives.apache.org/mod_mbox/incubator-tephra-dev/201609.mbox/%3CCAC9o21Q9RJqDAo9n_AJWKaPm9_9iM4JoOL0bK9uh2thhS5Jn1g%40mail.gmail.com%3E

The source tarball, including signatures, digests, etc. can be found at:
https://dist.apache.org/repos/dist/dev/incubator/tephra/0.9.0-incubating-rc1/src

The tag to be voted upon is v0.9.0-incubating:
https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.git;a=shortlog;h=refs/tags/v0.9.0-incubating

The release hash is db235cdfa0d40d4e31bcd19ab350e9961719c79e:
https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.git;a=commit;h=db235cdfa0d40d4e31bcd19ab350e9961719c79e

The Nexus Staging URL:
https://repository.apache.org/content/repositories/orgapachetephra-1004

Release artifacts are signed with the following key:
http://people.apache.org/keys/committer/poorna

KEYS file available:
https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS

For information about the contents of this release, see:
https://dist.apache.org/repos/dist/dev/incubator/tephra/0.9.0-incubating-rc1/CHANGES.txt

Please vote on releasing this package as Apache Tephra 0.9.0-incubating

The vote will be open for 72 hours.

[ ] +1 Release this package as Apache Tephra 0.9.0-incubating
[ ] +0 no opinion
[ ] -1 Do not release this package because ...

Thanks,
Poorna.


   

Re: [VOTE] Release of Apache Tephra-0.8.0-incubating [rc1]

[larsh]

Thanks James,
I must have looked at the wrong branch/tag, now looked at the 0.8.0-incubating 
tag, and all looks clean there.

Sorry for the noise.
+1 (Binding)
Thanks.
-- Lars

  From: James Taylor 
 To: "general@incubator.apache.org" ; lars 
hofhansl  
 Sent: Sunday, May 22, 2016 1:49 PM
 Subject: Re: [VOTE] Release of Apache Tephra-0.8.0-incubating [rc1]
   
Lars - Would you consider changing your vote given the additional
information from Justin and myself? There is no third party code bundled in
the source release.

Thanks,
James

On Fri, May 20, 2016 at 10:45 PM,  wrote:

> Hmm...
> The source code still shows "Copyright © 2015 Cask Data, Inc." notices.The
> code is still organized in co.cask.tephra... packages. That should be
> org.apache.tephra..., right?
> There is no NOTICE file, and the LICENSE file only contains the Apache 2.0
> license. Is there any 3rd party code included under other (open source)
> licenses that we would need to include?
> I realize this may sound like nit-picking. But it is an important aspect
> of the incubation time.
>
> I have to vote  -1 .
>
> -- Lars
>
>      From: James Taylor 
>  To: "general@incubator.apache.org" 
>  Sent: Friday, May 20, 2016 3:48 PM
>  Subject: Re: [VOTE] Release of Apache Tephra-0.8.0-incubating [rc1]
>
> +1. Transferring my vote over from the previous vote thread.
>
> On Fri, May 20, 2016 at 3:47 PM, Poorna Chandra  wrote:
>
> > Hi all,
> >
> > This is a call for a vote on releasing Apache Tephra 0.8.0-incubating,
> > release candidate 1. This
> > is the first release of Tephra.
> >
> > Apache Tephra community has voted and approved the release.
> >
> > Vote thread:
> >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-tephra-dev/201605.mbox/%3CCAC9o21R1x-m1%2BbaV3oK39RmPbf2pToBQrSGkfzBmWz%3Dp8Ez5JQ%40mail.gmail.com%3E
> >
> > Result thread:
> >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-tephra-dev/201605.mbox/%3CCAC9o21TR5Ur4nu%2BxOoXB74vHSvRujtj1C6%2BsA2N75YQf4DXd8w%40mail.gmail.com%3E
> >
> > The source tarball, including signatures, digests, etc. can be found at:
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.8.0-incubating-rc1/src
> >
> > The tag to be voted upon is v0.8.0-incubating:
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.git;a=shortlog;h=refs/tags/v0.8.0-incubating
> >
> > The release hash is 0db528e3603393221472b89fa9bb30312cfd5470:
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.git;a=commit;h=0db528e3603393221472b89fa9bb30312cfd5470
> >
> > The Nexus Staging URL:
> > https://repository.apache.org/content/repositories/orgapachetephra-1001
> >
> > Release artifacts are signed with the following key:
> > http://pgp.mit.edu/pks/lookup?op=get=0x8EC4A2C60990A464
> >
> > KEYS file available:
> > https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS
> >
> > For information about the contents of this release, see:
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.8.0-incubating-rc1/CHANGES.txt
> >
> > Please vote on releasing this package as Apache Tephra 0.8.0-incubating
> >
> > The vote will be open for 72 hours.
> >
> > [ ] +1 Release this package as Apache Tephra 0.8.0-incubating
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because ...
> >
> > Thanks,
> > Poorna.
> >
>
>
>
>

  

Re: [VOTE] Release of Apache Tephra-0.8.0-incubating [rc1]

[larsh]

Hmm...
The source code still shows "Copyright © 2015 Cask Data, Inc." notices.The code 
is still organized in co.cask.tephra... packages. That should be 
org.apache.tephra..., right?
There is no NOTICE file, and the LICENSE file only contains the Apache 2.0 
license. Is there any 3rd party code included under other (open source) 
licenses that we would need to include?
I realize this may sound like nit-picking. But it is an important aspect of the 
incubation time.

I have to vote  -1 .

-- Lars

  From: James Taylor 
 To: "general@incubator.apache.org"  
 Sent: Friday, May 20, 2016 3:48 PM
 Subject: Re: [VOTE] Release of Apache Tephra-0.8.0-incubating [rc1]
   
+1. Transferring my vote over from the previous vote thread.

On Fri, May 20, 2016 at 3:47 PM, Poorna Chandra  wrote:

> Hi all,
>
> This is a call for a vote on releasing Apache Tephra 0.8.0-incubating,
> release candidate 1. This
> is the first release of Tephra.
>
> Apache Tephra community has voted and approved the release.
>
> Vote thread:
>
> http://mail-archives.apache.org/mod_mbox/incubator-tephra-dev/201605.mbox/%3CCAC9o21R1x-m1%2BbaV3oK39RmPbf2pToBQrSGkfzBmWz%3Dp8Ez5JQ%40mail.gmail.com%3E
>
> Result thread:
>
> http://mail-archives.apache.org/mod_mbox/incubator-tephra-dev/201605.mbox/%3CCAC9o21TR5Ur4nu%2BxOoXB74vHSvRujtj1C6%2BsA2N75YQf4DXd8w%40mail.gmail.com%3E
>
> The source tarball, including signatures, digests, etc. can be found at:
>
> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.8.0-incubating-rc1/src
>
> The tag to be voted upon is v0.8.0-incubating:
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.git;a=shortlog;h=refs/tags/v0.8.0-incubating
>
> The release hash is 0db528e3603393221472b89fa9bb30312cfd5470:
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.git;a=commit;h=0db528e3603393221472b89fa9bb30312cfd5470
>
> The Nexus Staging URL:
> https://repository.apache.org/content/repositories/orgapachetephra-1001
>
> Release artifacts are signed with the following key:
> http://pgp.mit.edu/pks/lookup?op=get=0x8EC4A2C60990A464
>
> KEYS file available:
> https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS
>
> For information about the contents of this release, see:
>
> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.8.0-incubating-rc1/CHANGES.txt
>
> Please vote on releasing this package as Apache Tephra 0.8.0-incubating
>
> The vote will be open for 72 hours.
>
> [ ] +1 Release this package as Apache Tephra 0.8.0-incubating
> [ ] +0 no opinion
> [ ] -1 Do not release this package because ...
>
> Thanks,
> Poorna.
>


  

Re: [VOTE] Accept Tephra into the Apache Incubator

[larsh]

+1 (binding)
Exciting!

  From: Poorna Chandra 
 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 close 

Re: [VOTE] Accept Concerted into the Apache Incubator

[larsh]

+1 (binding)
This is exciting!Thanks for putting this together Atri.
-- Lars
  From: Atri Sharma 
 To: general@incubator.apache.org 
 Sent: Friday, October 9, 2015 8:55 AM
 Subject: [VOTE] Accept Concerted into the Apache Incubator
   
Hi all,

Following the discussion about Concerted I would like to call a vote for
accepting Concerted as a new incubator project.

The proposal text is included below, and available on the wiki:

https://wiki.apache.org/incubator/ConcertedProposal

The vote is open for 72 hours:

[ ] +1 accept Concerted in the Incubator
[ ] ±0
[ ] -1 (please give reason)

Regards,

Atri

= Abstract =

Concerted is an in memory write less read more engine aimed to provide
extreme read performance with very high degree of concurrency and
scalability and focus on minimizing own resource footprint.

= Proposal =
Concerted is built on the principal that a new type of workload is
dominating the scene and is now needed to be supported. These are the large
data set analytical workloads being analyzed or used on large clusters or
high power machines. Large analytical workloads depend on the ability to
query large data sets efficiently and in high concurrency while maintaining
semantics such as immediate consistency. An in memory engine designed to
support extreme read queries while providing support for aggregation
through various features (such as multidimensional representation of
tuples) will accelerate many usecases around large scale analytics.

Concerted believes that best understanding of user application lies with
user application developer. The need for massive read scaling should be on
demand and should be flexible to the level that user can decide as to which
representation and access of data suits his/her current requirements.
Hence, Concerted is not built in a traditional client/server model.
Concerted provides users with an API which can be used to load, read,
update and delete data. User chooses which data structure has to be used
for his current requirements. All API access is covered by Concerted's
internal systems like lock manager, transaction manager and cache manager
which ensure that reads scale to high level in every API call.

Concerted is a Do It Yourself in memory platform for making in memory
supporting engines. The use case we think of is supporting big data
warehouses like Hive, but there are endless use cases for a custom, highly
scalable in memory platform.

The goal of this proposal is to leverage an existing code base available on
Github and licensed under the Apache License 2.0 to build a community
around the project. Currently the community consists of existing hackers of
Concerted as well as people who have been following and associated with the
project since a while as well as database experts who are excited about
building a project like this. We are hoping that entering into Apache would
help us attract more contributors as well as connect with existing big data
projects like Apache Hive, Apache HAWQ, Apache Storm, Apache Tajo, Apache
Spark, Apache Geode to leverage their community base while assisting in
their use cases with Concerted. We had a discussion with founders of Apache
Tajo and they showed interest in using Concerted for some of their use
cases.
= Background =
Relational databases were built with the cost of physical memory in mind.
The cost is no longer very relevant and physical memory is now available on
demand. Another driving factor behind Concerted is that there is a paradigm
shift with big data coming into picture. Disk IO speeds are more of a
bottleneck than ever before. Combining the read dominance of analytical
workload with the speed of in memory structures, Concerted fits the current
scene. Also, supporting OLAP workloads with in memory support for faster
read constant queries and joins will be useful.

= Rationale =
As explained above, large analytical workloads need an in memory
lightweight engine which supports massive read concurrency, ground level
support for aggregations and analytics, extreme scalability and high read
performance, along with the engine being very light itself. Concerted aims
to solve these needs. Concerted is designed and built with three goals as
objectives:


Performance
    To provide high performance access to data from a large number of rows,
Concerted uses efficient representation and in memory indexing of data
coupled with high performance transactions, custom transactions and
lightweight locking and lockless techniques and an intelligent locking
manager.

Scalability
    Concerted is built with extreme concurrency and scalability in mind.

Efficiency
    Concerted aims to give expected performance under vast variety of
workloads and aims to have as low footprint as possible.

= Initial Goals =
The initial goal is to leverage an existing code base and invest in
building a community around the project. We anticipate a lot of initial
restructuring of the existing code so that it becomes