Re: [PROPOSAL] Zipkin for Apache Incubator

[Stack]

+1

Glad to see zipkin showing up on the incubator doorstep. I echo Andrew's
remarks.

OpenZipkin is bringing not only code with vintage, but a healthy community
too. I foresee a short trip to TLP.

If you need mentors, I'd be a bit of an "absent dad", but could help around
setup at least or if there are questions Apach'ing.

Thanks,
St.Ack

P.S. The gitbox repo offerings should make it so you can retain your
github-based process.



On Fri, Aug 17, 2018 at 2:30 AM Adrian Cole  wrote:

> I would like to propose Zipkin as an Apache Incubator project.
>
> The text of the proposal can be found below as well as on the Incubator
> wiki:
>
> https://wiki.apache.org/incubator/ZipkinProposal
>
> I believe we should have 3 mentors.. currently we have 2 (plus Wu
> Sheng and I who are familiar but not mentor-grade :P). If another
> person can volunteer to mentor us, would be sweet.
>
> -Adrian
>
> = Abstract =
> Zipkin is a distributed tracing system. It helps gather timing data
> needed to troubleshoot latency problems in microservice architectures.
> It manages both the collection and lookup of this data. Zipkin’s
> design is based on the Google Dapper paper.
>
> = Proposal =
> Zipkin provides a defined data model and payload type for distributed
> trace data collection. It also provides an UI and http api for
> querying the data. Its server implements this api and includes
> abstractions for storage and transport of trace payloads. The
> combination of these parts avoid lock-in to a specific tracing
> backend. For example, Zipkin includes integration with different open
> source storage mechanisms like Apache Cassandra and Elasticsearch. It
> also includes bridges to convert collected data and forward it to
> service offerings such as Amazon X-Ray and Google Stackdriver.
> Ecosystem offering extend this portability further.
>
> While primarily focused on the system, Zipkin also includes tracing
> libraries which applications use to report timing information.
> Zipkin's core organization includes tracer libraries written in Java,
> Javascript, Go, PHP and Ruby. These libraries use the formats
> mentioned above to report data, as well "B3" which is a header format
> needed to send trace identifiers along with production requests. Many
> Zipkin libraries can also send data directly to other services such as
> Amazon X-Ray and Google Stackdriver, skipping any Zipkin
> infrastructure. There are also more Zipkin tracing libraries outside
> the core organization than inside it. This is due to the "OpenZipkin"
> culture of promoting ecosystem work.
>
> = Background =
> Zipkin began in 2012 at Twitter during a time they were investigating
> performance problems underlying the "fail whale" seen by users. The
> name Zipkin is from the Turkish word for harpoon: the harpoon that
> will kill the failures! Incidentally, Zipkin was not the first tracing
> system, it had roots in a former system at Twitter named
> BigBrotherBird. It is due to BigBrotherBird that the de-facto tracing
> headers we still use today include the prefix "X-B3".
>
> In 2015, a community of users noticed the project was not healthy in
> so far as it hadn't progressed and often didn't accept pull requests,
> and the Cassandra backend was stuck on an unmaintained library. For
> example, the Apache Incubator H-Trace project started in some ways as
> a reaction to the inability to customize the code. The root cause of
> this was Twitter moving to internal storage (Manhattan) and also the
> project not being managed as a product. By mid 2015, the community
> regrouped as OpenZipkin and the codebase moved from Twitter to an org
> also named OpenZipkin. This led to fast progress on concerns including
> initially a server rewrite and Docker based deployment.
>
> In 2018, the second version of the data model completed, and along the
> way, many new libraries became standard, including javascript, golang
> and PHP. The community is dramatically larger than 2015, and Zipkin
> remains the most popular tracing system despite heavy competition.
>
> = Rationale =
> Zipkin is a de-facto distributed tracing system, which is more
> important as architectures become more fine grained due to popularity
> of microservice or even serverless architectures. Applications
> transition to use more complex communication including asynchronous
> code and service mesh, increasing the need for tools that visualize
> the behavior of requests as they map across an architecture.
>
> Zipkin's server is focused only on distributed tracing. It is meant to
> be used alongside existing logging and metrics systems. Generally, the
> community optimizes brown field concerns such as interop over breaking
> changes such as experimental features. The combination of code and
> community make Zipkin a safe and easier choice for various sites to
> introduce or grow their observability practice.
>
> = Initial Goals =
> The initial goals are to mature OpenZipkin's community process. For
> example, while 

Re: [VOTE] Graduate the Apache Trafodion Project from Incubator to a TLP

[Stack]

+1 (mentor, binding)

St.Ack

On Tue, Nov 28, 2017 at 12:01 PM, Pierre Smits 
wrote:

> Hi all,
>
> The Trafodion community started an initial discussion graduating from the
> Incubator (see [1]) and had a consensus that the project is good to
> graduate. The community proceeded to draft the graduation resolution,
> discussed it [2], and voted on it [3]. The community vote passed with 42 +1
> votes (40 advisory, 2 binding votes), no -1 votes or  +0 (abstains) votes.
>
> The discussion on the graduation of the Apache Trafodion project and the
> proposed draft resolution proceeded to the general mailing list of the
> Apache Incubator project [4], and advice was provided about some wording in
> the draft resolution. The proposed changes to that draft are incorporated
> into the graduation resolution shown below. I would now like to call for a
> recommendation vote to present the Board of The Apache Software Foundation
> with the resolution solution to graduate from incubation and establish
> Apache Trafodion as a top-level project.
>
> Apache Trafodion entered incubation in May 2015. Since then the project has
> produced several releases and has grown the community, the committer pool
> and the PPMC. For each release source artefacts have been voted on and made
> available to the public on the Apache Distribution Network. Given all the
> feedback provided in various discussions about our progress and graduation,
> we feel confident that the project is ready to graduate from incubation.
>
> Please vote on whether to graduate Apache Trafodion from incubation and
> recommend the graduation resolution below to the ASF Board.
>
> [  ] +1 Graduate the Apache Trafodion Project from the Incubator
> [  ] +0 Abstain
> [  ] -1 Don't graduate the Apache Trafodion Project from the Incubator
> because...
>
> This vote will be open for at least 72 hours. Thanks to all Trafodion
> Mentors, all Trafodion Contributors for their support and contributions and
> all in the Apache Incubator Project who took the time to provide their
> insights and support.
>
> The full text of the resolution from [5] is below. The resolution will
> be submitted
> to the Board of Directors of The Apache Software Foundation for their
> consideration upon approval by the Apache Incubator PMC members.
>
> [1] [DISCUSSION] Graduation of The (incubating) Apache Trafodion Project
>  3ad86ff21839e98e0ae68520e3@%3Cdev.trafodion.apache.org%3E>
> [2] [VOTE] Graduate from Incubator and become a top-level project
>  03a1585d398d7820b26be9a255@%3Cdev.trafodion.apache.org%3E>
> [3]  [RESULT][VOTE] Graduate from Incubator and become a top-level project
>  56302cf98fe212909fefb8e76f@%3Cdev.trafodion.apache.org%3E>
> [4] [DISCUSS] Resolution to graduate the incubating Apache Trafodion
> Project
>  69b9e08b6e4cc69fafdc21531e@%3Cgeneral.incubator.apache.org%3E>
>
>
> Best Regards,
>
> Pierre Smits
>
> -
>
> Establish the Apache Trafodion Project
>
>
> WHEREAS, the Board of Directors deems it to be in the best interests of
>
> the Foundation and consistent with the Foundation's purpose to establish
>
> a Project Management Committee charged with the creation and maintenance
>
> of open-source software, for distribution at no charge to the public,
>
> related to a webscale SQL-on-Hadoop solution enabling transactional or
>
> operational workloads.
>
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>
> (PMC), to be known as the "Apache Trafodion Project", be and hereby is
>
> established pursuant to Bylaws of the Foundation; and be it further
>
>
> RESOLVED, that the Apache Trafodion Project be and hereby is responsible
>
> for the creation and maintenance of software related to a webscale
>
> SQL-on-Hadoop solution enabling transactional or operational workloads;
>
> and be it further
>
>
> RESOLVED, that the office of "Vice President, Apache Trafodion" be and
>
> hereby is created, the person holding such office to serve at the
>
> direction of the Board of Directors as the chair of the Apache Trafodion
>
> Project, and to have primary responsibility for management of the
>
> projects within the scope of responsibility of the Apache Trafodion
>
> Project; and be it further
>
>
> RESOLVED, that the persons listed immediately below be and hereby are
>
> appointed to serve as the initial members of the Apache Trafodion
>
> Project:
>
>
>  * Amanda K Moran 
>
>  * Dave Birdsall  
>
>  * Gunnar Tapper  
>
>  * Ming Liu   
>
>  * Pierre Smits   
>
>  * Roberta Marton 
>
>  * Selva 

Re: Where to edit a podling's data for whimsey?

[Stack]

On Fri, Mar 24, 2017 at 4:00 PM, Daniel Gruno <humbed...@apache.org> wrote:

> On 03/24/2017 11:18 PM, Stack wrote:
> > I am having trouble finding where to edit to fix a podling's whimsey
> view?
> > Pointers appreciated.
> > Thanks,
> > St.Ack
> >
>
> TL;DR: https://whimsy.apache.org/roster/ppmc/ ;)
>
>
Thanks Daniel. Thats what I wanted.
St.Ack



> With regards,
> Daniel
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Where to edit a podling's data for whimsey?

[Stack]

I am having trouble finding where to edit to fix a podling's whimsey view?
Pointers appreciated.
Thanks,
St.Ack

Re: [VOTE] Apache S2Graph(incubating) 0.1.0 release RC6

[Stack]

+1 binding

Checked hash and signature.
Poked around the untar'd src dir.
Ran RAT on top level. Got these complaints:

  ./.gitignore
  ./.rat-excludes

Then found your instructions for how to run RAT (smile) and all looks good.
Built from source. Had odd issue in hbase logs complaining couldn't find
ESAPI.properties
Then read your README and just ran the example.
Was able to see data in HBase

LGTM
St.Ack

On Fri, Oct 14, 2016 at 1:00 AM, DO YUNG YOON  wrote:

> Hi all
>
> This is a call for a releasing Apache S2Graph 0.1.0-incubating, release
> candidate 6.
> This is the first release of S2Graph.
>
> Apache S2Graph community has voted and approved the release.
>
> Vote thread:
> https://lists.apache.org/thread.html/3307d1414f00965b72776c79d409e3
> c6457df0a69e402d1f56b1e252@%3Cdev.s2graph.apache.org%3E
>
> Result thread:
> https://lists.apache.org/thread.html/a407ea2dcdc2872e0654545d9f4f94
> e1eae7adbe7fc31709b99b1879@%3Cdev.s2graph.apache.org%3E
>
> The source tarball, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/s2graph/0.
> 1.0-incubating-RC6/
>
> The tag to be voted upon is v0.1.0-incubating-rc6:
> https://git-wip-us.apache.org/repos/asf?p=incubator-s2graph.
> git;a=shortlog;h=refs/tags/v0.1.0-incubating-rc6
>
> The release hash is 4325ff1303ce606909bc16b5cbee53c8a5b23653:
> https://git-wip-us.apache.org/repos/asf?p=incubator-s2graph.
> git;a=commit;h=4325ff1303ce606909bc16b5cbee53c8a5b23653
>
> Release artifacts are signed with the following key:
> http://people.apache.org/keys/committer/steamshon
>
> KEYS file available:
> https://dist.apache.org/repos/dist/dev/incubator/s2graph/KEYS
>
> For information about the contents of this release, see:
> https://dist.apache.org/repos/dist/dev/incubator/s2graph/0.
> 1.0-incubating-RC6/CHANGES
>
> The vote will be open for 72 hours.
>
> [ ] +1 Release this package as 0.1.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>
> Thanks,
> DOYUNG YOON.
>

Re: [VOTE] Accept Spot into the Apache Incubator

[Stack]

+1 (binding)
St.Ack

On Tue, Sep 20, 2016 at 11:15 AM, Doug Cutting  wrote:

> Following the discussion thread, I would like to call a vote on
> accepting Spot into the Apache Incubator.
>
> [] +1 Accept Spot into the Apache Incubator
> [] +0 Abstain.
> [] -1 Do not accept Spot into the Apache Incubator because ...
>
> This vote will run for the usual 72 hours.
>
> The proposal is attached, but you can also access it on the wiki:
>https://wiki.apache.org/incubator/SpotProposal
>
> Thanks,
>
> Doug
>
> = SpotProposal =
>
> == Abstract ==
>
> Spot is an open source platform for network telemetry (packet, flow,
> and proxy at the moment) built on an open data model and Apache
> Hadoop.
>
> == Proposal ==
>
> Spot (formerly Open Network Insight, or ONI) is an open source
> solution for network telemetry (packet, flow, and proxy at the moment)
> built on an open data model and Apache Hadoop. It provides ingestion
> and transformation of binary data, scalable machine learning, and
> interactive visualization for identifying threats in network flows and
> DNS packets.
>
> Spot has a pluggable architecture that can accommodate multiple open
> data models. Although cybersecurity/network-intrusion analysis is the
> initial use case for Spot, we are actively encouraging the
> contribution of new models that will enable other adjacent
> applications, such as fraud detection or IT-operational analytics such
> as performance and health monitoring. Because these models are open,
> users maintain control of their own data.
>
> More information on Spot can be found at the existing project website
> at http://open-network-insight.org/.
>
> == Background ==
>
> It almost goes without saying that cybersecurity is an acute and
> paramount concern globally, for organizations of all types and
> sizes. Fortunately, thanks to the availability of massively scalable
> (in the PBs) data infrastructure, security professionals can now make
> authentically data-driven decisions about how they protect their
> assets. For example, records of network traffic, captured as network
> flows, are often stored and analyzed for use in network management,
> and this same information can provide valuable insights into network
> vulnerabilities.
>
> Cybersecurity is just one example, however: There are other examples
> of adjacent use cases, such as user fraud detection or IT-operations
> analytics, that would benefit from the combination of Spot
> functionality and PB-scale data sets for analysis.
>
> == Rationale ==
>
> Although cybersecurity is its initial use case/data model, Spot is
> intended to more generally tackle the dual challenges of facilitating
> the development of big data-driven analytic solutions, while helping
> vendors avoid having to create one/off infrastructure for each use
> case. Spot will eliminate issues related to vendor data models that
> create silos between solutions, and that make it difficult for users
> to consume these innovations from multiple vendors. In summary, Spot
> will accelerate the development of new massively scalable analytic
> applications that give users more flexibility, and more choices.
>
> As an initial effort, we are now seeking to build an ecosystem of
> developers, data scientists, and security professionals to make Spot
> the open, community-driven, cybersecurity platform standard it needs
> to become. By bringing Spot to Apache, we hope to galvanize these
> groups to cooperate in this highly matrixed effort, and to build a
> global, and diverse, Spot community.
>
> == Initial Goals ==
>
> Move the existing codebase, website, documentation, and mailing lists
> to Apache-hosted infrastructure Work with the infrastructure team to
> implement and approve our build and testing workflows in the context
> of the ASF Incremental development and releases per Apache guidelines
>
> == Current Status ==
>
> === Releases ===
>
> Spot has undergone one public release (1.0). This initial release was
> not performed in the typical ASF fashion; we will adopt the ASF source
> release process upon joining the incubator.
>
> === Source ===
>
> Spot’s source, including core platform and associated submodules, is
> currently hosted in several GitHub repositories under the indicated
> licenses:
>
>  * Core (Apache License 2.0)
>  * Oni-ingest (Apache License 2.0)
>  * Oni-ml (Apache License 2.0
>  * Oni-oa (BSD & MIT)
>  * Oni-setup (Apache License 2.0)
>  * Oni-nfdump (BSD)
>  * Oni-lda-c (GNU General Public License version 2)
>
> The repositories will be transitioned to Apache’s git hosting during
> incubation.  Issues related to GPL code will be resolved during
> incubation.
>
>
> === Issue Tracking ===
>
> Spot’s bug and feature tracking is hosted on Github at:
>
>  * https://github.com/Open-Network-Insight/open-network-insight/issues
>
> Issue tracking will be transitioned to Apache’s JIRA instance during
> incubation.
>
> === Code review ===
>
> Spot maintainers currently use “LGTM” 

Re: [VOTE] Release Apache Trafodion (incubating) release 2.0.1-incubating RC3

[Stack]

I do Roberta. Let me put it on the t8 dev list.
St.Ack

On Wed, Jul 6, 2016 at 7:38 AM, Roberta Marton <roberta.mar...@esgyn.com>
wrote:

> Thanks for trying out the release.
> Do you have the complete output from the make?  We can take a look and
> perhaps figure out what is happening.
> I will also look into the ~/.trafodion file issue you brought up.
>
> Regards,
> Roberta
>
> -Original Message-
> From: saint@gmail.com [mailto:saint@gmail.com] On Behalf Of Stack
> Sent: Tuesday, July 5, 2016 9:51 PM
> To: general@incubator.apache.org
> Subject: Re: [VOTE] Release Apache Trafodion (incubating) release
> 2.0.1-incubating RC3
>
> +1
>
> md5 and signing look good. Did RAT check using nice RAT_README.
>
> Poked around. All looks good.
>
> St.Ack
>
> Here are some notes on my experience trying to build:
>
> + I found myself a centos 6.6:
> $ more /etc/issue
> CentOS release 6.6 (Final)
> Kernel \r on an \m
>
> + Install doc is excellent (I said that before).
> + This bit of doc seems wrong from install because talks of .trafodion
> + but
> we are echo'ing to .bashrc from
>
> https://cwiki.apache.org/confluence/display/TRAFODION/Create+Build+Environment
>
>  Export TOOLSDIR in your environment or ~/.trafodion file.
>  export TOOLSDIR=$HOME/trafodion-build-tools
>  echo -en "export TOOLSDIR=$HOME/trafodion-build-tools\n" >> $HOME/.bashrc
>
> + make package-all and make all failed here for me:
>
> make[4]: Entering directory
> `/home/stack/apache-trafodion-2.0.1-incubating/core/sqf/src/tm/tools'
> ##(SQF)
> make[4]: Nothing to be done for `all'.  ##(SQF)
> make[4]: Leaving directory
> `/home/stack/apache-trafodion-2.0.1-incubating/core/sqf/src/tm/tools'
>  ##(SQF)
> make[3]: Leaving directory
> `/home/stack/apache-trafodion-2.0.1-incubating/core/sqf/src/tm'
> ##(SQF)
> make[2]: Leaving directory
> `/home/stack/apache-trafodion-2.0.1-incubating/core/sqf'
> make[1]: *** [foundation] Error 2
> make[1]: Leaving directory
> `/home/stack/apache-trafodion-2.0.1-incubating/core'
> make: *** [package-all] Error 2
>
> ... then I ran out of time.
>
> Thanks,
> St.Ack
>
>
>
> On Wed, Jun 29, 2016 at 2:51 PM, Roberta Marton <roberta.mar...@esgyn.com>
> wrote:
>
> > Hello,
> >
> >
> >
> > This is a call to vote on Apache Trafodion patch release
> > 2.0.1-incubating
> > RC3 (Release Candidate 3).
> >
> >
> >
> > Apache Trafodion is a webscale SQL-on-Hadoop solution enabling
> > transactional or
> >
> > operational workloads on Hadoop.  Trafodion builds on the scalability,
> > elasticity, and
> >
> > flexibility of Hadoop. Trafodion extends Hadoop to provide guaranteed
> >
> > transactional integrity, enabling new kinds of big data applications
> > to run on
> >
> > Hadoop.
> >
> >
> >
> > The changes in this patch release address licensing issues found
> > during the
> >
> > Apache Trafodion release 2.0.1 RC1 (Release Candidate 1) voting cycle.
> >
> >
> >
> > Changes since 2.0.1 RC1:
> >
> >[TRAFODION-2068] Missing DISCLAIMER files for release package
> >
> >[TRAFODION-2082] BSD-4 license for swsprintf and swscanf unclear
> >
> >
> >
> > The Trafodion community has approved  this release:
> >
> >
> > http://mail-archives.apache.org/mod_mbox/incubator-trafodion-dev/20160
> > 6.mbox/ajax/%3Cab0bbe9228d5b7b487f4b9952f17ede5%40mail.gmail.com%3E
> >
> >
> >
> > The latest tag for this candidate is "2.0.1rc3". Git repository:
> > git://
> > git.apache.org/incubator-trafodion.git:
> >
> > *
> > https://git-wip-us.apache.org/repos/asf?p=incubator-trafodion.git;a=co
> > mmit;h=6357cb8f76ab399b451896c75273fd6f2e02d9c4
> > <
> > https://git-wip-us.apache.org/repos/asf?p=incubator-trafodion.git;a=co
> > mmit;h=6357cb8f76ab399b451896c75273fd6f2e02d9c4
> > >*
> >
> >
> >
> > Release artifacts are:
> >
> > *
> > https://dist.apache.org/repos/dist/dev/incubator/trafodion/trafodion-2
> > .0.1-RC3
> > <
> > https://dist.apache.org/repos/dist/dev/incubator/trafodion/trafodion-2
> > .0.1-RC3
> > >*
> >
> >
> >
> > Artifacts are signed with my key (A44C5A05), which is in
> > https://dist.apache.org/repos/dist/release/incubator/trafodion/KEYS
> >
> >
> >
> > Instructions:
> >
> >
> >
> > Setting up build environment:
> >
> > *
> > https://cwiki.apache.org/confluence/display/TRAFODION/Create+Build+Env
> > ironment
> > <
> > https://cwiki.apache.org/confluence/display/TRAFODION/Create+Build+Env
> > ironment
> > >*
> >
> >
> >
> > Building:
> >
> > https://cwiki.apache.org/confluence/display/TRAFODION/Build+Source
> >
> >
> >
> > The vote is open for at least 72 hours.
> >
> >
> >
> > [ ] +1 approve
> >
> > [ ] +0 no opinion
> >
> > [ ] -1 disapprove (and reason why)
> >
> >
> >
> >   Regards,
> >
> >   Roberta
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Trafodion (incubating) release 2.0.1-incubating RC3

[Stack]

+1

md5 and signing look good. Did RAT check using nice RAT_README.

Poked around. All looks good.

St.Ack

Here are some notes on my experience trying to build:

+ I found myself a centos 6.6:
$ more /etc/issue
CentOS release 6.6 (Final)
Kernel \r on an \m

+ Install doc is excellent (I said that before).
+ This bit of doc seems wrong from install because talks of .trafodion but
we are echo'ing to .bashrc from
https://cwiki.apache.org/confluence/display/TRAFODION/Create+Build+Environment

 Export TOOLSDIR in your environment or ~/.trafodion file.
 export TOOLSDIR=$HOME/trafodion-build-tools
 echo -en "export TOOLSDIR=$HOME/trafodion-build-tools\n" >> $HOME/.bashrc

+ make package-all and make all failed here for me:

make[4]: Entering directory
`/home/stack/apache-trafodion-2.0.1-incubating/core/sqf/src/tm/tools'
##(SQF)
make[4]: Nothing to be done for `all'.  ##(SQF)
make[4]: Leaving directory
`/home/stack/apache-trafodion-2.0.1-incubating/core/sqf/src/tm/tools'
 ##(SQF)
make[3]: Leaving directory
`/home/stack/apache-trafodion-2.0.1-incubating/core/sqf/src/tm'  ##(SQF)
make[2]: Leaving directory
`/home/stack/apache-trafodion-2.0.1-incubating/core/sqf'
make[1]: *** [foundation] Error 2
make[1]: Leaving directory
`/home/stack/apache-trafodion-2.0.1-incubating/core'
make: *** [package-all] Error 2

... then I ran out of time.

Thanks,
St.Ack



On Wed, Jun 29, 2016 at 2:51 PM, Roberta Marton <roberta.mar...@esgyn.com>
wrote:

> Hello,
>
>
>
> This is a call to vote on Apache Trafodion patch release 2.0.1-incubating
> RC3 (Release Candidate 3).
>
>
>
> Apache Trafodion is a webscale SQL-on-Hadoop solution enabling
> transactional or
>
> operational workloads on Hadoop.  Trafodion builds on the scalability,
> elasticity, and
>
> flexibility of Hadoop. Trafodion extends Hadoop to provide guaranteed
>
> transactional integrity, enabling new kinds of big data applications to run
> on
>
> Hadoop.
>
>
>
> The changes in this patch release address licensing issues found during the
>
> Apache Trafodion release 2.0.1 RC1 (Release Candidate 1) voting cycle.
>
>
>
> Changes since 2.0.1 RC1:
>
>[TRAFODION-2068] Missing DISCLAIMER files for release package
>
>[TRAFODION-2082] BSD-4 license for swsprintf and swscanf unclear
>
>
>
> The Trafodion community has approved  this release:
>
>
> http://mail-archives.apache.org/mod_mbox/incubator-trafodion-dev/201606.mbox/ajax/%3Cab0bbe9228d5b7b487f4b9952f17ede5%40mail.gmail.com%3E
>
>
>
> The latest tag for this candidate is "2.0.1rc3". Git repository: git://
> git.apache.org/incubator-trafodion.git:
>
> *
> https://git-wip-us.apache.org/repos/asf?p=incubator-trafodion.git;a=commit;h=6357cb8f76ab399b451896c75273fd6f2e02d9c4
> <
> https://git-wip-us.apache.org/repos/asf?p=incubator-trafodion.git;a=commit;h=6357cb8f76ab399b451896c75273fd6f2e02d9c4
> >*
>
>
>
> Release artifacts are:
>
> *
> https://dist.apache.org/repos/dist/dev/incubator/trafodion/trafodion-2.0.1-RC3
> <
> https://dist.apache.org/repos/dist/dev/incubator/trafodion/trafodion-2.0.1-RC3
> >*
>
>
>
> Artifacts are signed with my key (A44C5A05), which is in
> https://dist.apache.org/repos/dist/release/incubator/trafodion/KEYS
>
>
>
> Instructions:
>
>
>
> Setting up build environment:
>
> *
> https://cwiki.apache.org/confluence/display/TRAFODION/Create+Build+Environment
> <
> https://cwiki.apache.org/confluence/display/TRAFODION/Create+Build+Environment
> >*
>
>
>
> Building:
>
> https://cwiki.apache.org/confluence/display/TRAFODION/Build+Source
>
>
>
> The vote is open for at least 72 hours.
>
>
>
> [ ] +1 approve
>
> [ ] +0 no opinion
>
> [ ] -1 disapprove (and reason why)
>
>
>
>   Regards,
>
>   Roberta
>

Re: [VOTE] Apache Kudu (incubating) 0.9.0 RC1

[Stack]

+1 (binding, mentor)

Checked signature and hash. Poked around. Looks good. Ran Apache-RAT on the
tar ball.

$ python ./build-support/release/check-rat-report.py
build-support/release/rat_exclude_files.txt rat.xml
OK

Built it and ran unit tests.

The following tests FAILED for me but this seems to be known issue on mac
os x going by vote thread down in the podling:

102 - deltafile-test (Failed)
154 - client-test (Failed)
159 - alter_table-randomized-test (Failed)
165 - raft_consensus-itest (Failed)
167 - ts_recovery-itest (Failed)
169 - delete_table-test (Failed)
172 - all_types-itest (Failed)

St.Ack


On Mon, Jun 6, 2016 at 10:03 AM, Jean-Daniel Cryans 
wrote:

> Hi,
>
> The PPMC vote to release Apache Kudu (incubating) 0.9.0 RC1 passed and I'm
> now submitting this to the IPMC.
>
> Vote thread:
>
> http://mail-archives.apache.org/mod_mbox/incubator-kudu-dev/201606.mbox/%3CCAGpTDNduoQM0ktuZc1eW1XeXCcXhvPGftJ%3DLRB8Er5c2dZptvw%40mail.gmail.com%3E
>
> In the thread, folks noticed some unit test failures on OSX and Ubuntu
> 16.04, but nothing critical. Just a heads-up if you are on those OSes.
>
> Result:
>
> http://mail-archives.apache.org/mod_mbox/incubator-kudu-dev/201606.mbox/%3CCAGpTDNeJdU%2BoUF4ZJneZt%3DCfFHY-HoqKgORwVuWWUMHq5jBNzA%40mail.gmail.com%3E
>
> I'm expecting Chris Mattmann's +1 to carry over from the dev list vote.
>
> This is a source-only release. The artifacts were staged here:
> https://dist.apache.org/repos/dist/dev/incubator/kudu/0.9.0-RC1/
>
> It was built from this tag:
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-kudu.git;a=commit;h=5f2bf643d8ce3d042aa3903543a92841077a6874
>
> I'd like to call out one change we made related to Justin McLean's feedback
> on 0.8.0's voting thread:
>
> https://git1-us-west.apache.org/repos/asf?p=incubator-kudu.git;a=commit;h=3339ce06
>
> Please try the release and vote; vote will be open for at least 72 hours.
>
> Thanks,
>
> J-D
>

DISCUSS: Trafodion for TLP

[Stack]

We'd like to solicit feedback on whether the Trafodiion project is ready to
go TLP. I am the project Champion writing on behalf of the project PMC.

Our clutch report is nice and healthy [2]. Our up-to-date status page can
be found here [1.]. Development is brisk. We've made two releases out of
incubator up to this (with another up for vote). We have taken on new
committers since we entered incubation about a year ago.

The main downside that we see is that we have few users -- going by traffic
up on the mailing list -- and that near all committers are from a single
company, Esgyn (Three committers are not Esgyn employees).

Feedback/opinions appreciated.

Yours,
St.Ack

1. http://incubator.apache.org/projects/trafodion.html
2. http://incubator.apache.org/clutch.html

Re: [VOTE] Apache Kudu (incubating) 0.8.0 RC1

[Stack]

+1 (binding, mentor)

+ Checked sig and hash
+ Ran build on macox. Ran nice and smooth.
+ Ran unit tests. Ran into KUDU-1394. Added addr2line to my path and gdb.
Got further but still a few test failures. Added my experience to KUDU-1394.
+ Ran rat on java subdir
+ Poked around the layout; looks good.

St.Ack


On Wed, Apr 6, 2016 at 2:52 PM, Jean-Daniel Cryans 
wrote:

> Hi,
>
> The PPMC vote to release Apache Kudu (incubating) 0.8.0 RC1 passed and I'm
> now submitting this to the IPMC.
>
> Vote thread:
>
> http://mail-archives.apache.org/mod_mbox/incubator-kudu-dev/201604.mbox/%3CCAGpTDNfA-hsv6xkeNcvwBGarP1sri%2BvBYqYNt70YWeH44_QPSw%40mail.gmail.com%3E
>
> Result:
>
> http://mail-archives.apache.org/mod_mbox/incubator-kudu-dev/201604.mbox/%3CCAGpTDNfYy-AUYGL6h%2BVUi25nGRC0BkTcG20PmywffeGmRgOmQg%40mail.gmail.com%3E
>
> The is a source-only release. The artifacts were staged here:
> https://dist.apache.org/repos/dist/dev/incubator/kudu/0.8.0-RC1/
>
> It was built from this tag:
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-kudu.git;a=commit;h=7874185b07198267229c1cc921b21549ea16cf53
>
> I'd like to call out two specific changes we made related to Justin
> McLean's feedback on 0.7.1's voting thread:
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-kudu.git;a=commit;h=51463bcf6cca7e99439bb796a35d43560bfc9bcc
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-kudu.git;a=commit;h=429311c5ef09e34bd8d1b11148822908aa31b0f8
>
> Please try the release and vote; vote will be open for at least 72 hours.
>
> Thanks,
>
> J-D
>

Re: [DISCUSS] [PROPOSAL] Omid for Apache Incubator

[Stack]

+1 (binding)
Good luck lads,
St.Ack

On Thu, Mar 17, 2016 at 1:17 PM, Daniel Dai  wrote:

> Hi,
>
> I would like to propose Omid as an Apache Incubator project:
>
> https://wiki.apache.org/incubator/OmidProposal
>
> I've posted posted the text of the proposal below:
>
> Thanks,
> Daniel
>
> = Omid Proposal =
>
> === Abstract ===
>
> Omid is a flexible, reliable, high performant and scalable ACID
> transactional framework that allows client applications to execute
> transactions on top of MVCC key/value-based NoSQL datastores
> (currently Apache HBase) providing Snapshot Isolation guarantees on
> the accessed data.
>
>
> === Proposal ===
>
> Omid is a flexible open-source transactional framework that provides
> ACID transactions with Snapshot Isolation guarantees on top of NoSQL
> datastores. In particular, the current codebase brings the concept of
> transactions to the popular Apache HBase datastore. Omid offers great
> performance, it is highly available, and scalable. Omid's current
> version is able to scale to thousands of clients triggering concurrent
> transactions on application data stored in HBase. Omid can scale
> beyond 100K transactions per second on mid-range hardware while
> incurring in a minimal impact on the speed of data access in the
> datastore. We’re currently experimenting with a prototype version that
> can improve the performance up to ~380K TPS.
>
>
> Omid has been publicly available as an open-source project in Github
> under Apache License Version 2.0 since 2011 [1]. During these years,
> it has generated certain interest in the open source community,
> especially since the public presentation of the first version in
> Hadoop Summit 2013 [2]. Currently the Github project has 241 Stars and
> 93 forks. Yahoo Inc. submits this proposal to the Apache Software
> Foundation with the aim to transfer the Omid project -including its
> source code and documentation- to Apache in order to start the build
> of a stable open source community around it.
>
>
> [1] https://github.com/yahoo/omid
>
> [2] Omid presentation at Hadoop Summit 2013:
>
> https://www.youtube.com/watch?v=Rhdmo9pVGgU=68=PLSAiKuajRe2luyqLU464Nxz4aQe7EPBus
>
>
> === Background ===
>
> An Omid prototype was first released as an open-source project back in
> 2011. Inspired by Google Percolator [1], it offered a lock-free
> approach to transactions in NoSQL datastores (See [2]). However,
> during these years, the design of Omid has evolved significantly.
> Whilst the current open-sourced version maintains many aspects of the
> original implementation, it is the result of a major redesign of the
> first prototype released in 2011.
>
>
> Omid has now a more decentralized design that does not sacrifice the
> consistency and performance of the original version. The current
> design also enables Omid to scale to thousands of clients executing
> transactions concurrently on application data stored in HBase.
> Internally, Omid still utilizes a lock-free approach to support
> multiple concurrent clients. Its design also relies on a centralized
> conflict detection component, the TSO, which now resolves in an
> efficient manner writeset collisions among concurrent transactions
> without having to piggyback commit information to the clients. Another
> important benefit of Omid is that it doesn't require any modification
> of the underlying key-value datastore, HBase in this case. Moreover,
> the recently added high availability algorithm allows to eliminate the
> single point of failure represented by the TSO in those system
> deployments requiring a higher degree of dependability. Last but not
> least, the provided user API is very simple, mimicking transaction
> managers in the relational world: begin, commit, rollback.
>
>
> Omid is used internally at Yahoo. Sieve, Yahoo’s web-scale content
> management platform powering some of next-generation search and
> personalization products is using Omid as a transaction manager in its
> processing pipeline. Sieve essentially acts as a huge processing hub
> between content feeds and serving systems. It provides an environment
> for highly customizable, real-time, streamed information processing,
> with typical discovery-to-service latencies of just a few seconds. In
> terms of scale and availability, Omid’s new design was largely driven
> by Sieve’s requirements.
>
>
> At Yahoo, we are also making an effort to disseminate the current
> status of the project through blog entries (See [3], [4] and [5]) and
> submissions to technical and academic conferences such as ATC 2016,
> Hadoop Summit 2016, HBaseConf 2016. Last but not least, Omid also
> appeared in a TechCrunch article in the last quarter of 2015 (See [6])
>
>
> [1] D. Peng and F. Dabek, Large-scale Incremental Processing Using
> Distributed Transactions and Notifications. USENIX Symposium on
> Operating Systems Design and Implementation, 2010
>
> [2] D. Gomez-Ferro, F. Junqueira, I. Kelly, B. Reed, and M. Yabandeh.
> 

Re: [VOTE] Accept Tephra into the Apache Incubator

[Stack]

I'm late, but let me add my +1 anyways.
St.Ack

On Thu, Mar 3, 2016 at 5:29 PM, 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 

Re: [VOTE] Apache Kudu (incubating) 0.7.1 RC2

[Stack]

+1 (binding)

Checked signature, hash, and compared tarball to git tag. Built it
successfully. Ran unit tests. Poked around. Licenses look good.

St.Ack

On Sun, Mar 6, 2016 at 10:20 AM, Jean-Daniel Cryans 
wrote:

> Hi,
>
> The PPMC vote to release Apache Kudu (incubating) 0.7.1 RC2 passed and I'm
> now submitting this to the IPMC.
>
> Vote thread:
>
> http://mail-archives.apache.org/mod_mbox/incubator-kudu-dev/201603.mbox/%3CCAGpTDNfBpLCqYEeArpDUFM0EUvW-aOUHDpCtCQARetHTY%2BUACw%40mail.gmail.com%3E
>
> Result:
>
> http://mail-archives.apache.org/mod_mbox/incubator-kudu-dev/201603.mbox/%3CCAGpTDNdH-pK_cmoxXzTag5T0G9Bm6jqN-7Bf%3DcQjX1vrrpnUxw%40mail.gmail.com%3E
>
> The is a source-only release. The artifacts were staged here:
> https://dist.apache.org/repos/dist/dev/incubator/kudu/0.7.1-RC2/
>
> Please try the release and vote; vote will be open for at least 72 hours.
>
> There's already one binding +1 from Todd Lipcon.
>
> Thanks,
>
> J-D
>

Re: [VOTE] Apache Kudu (incubating) 0.7.0 RC3

[Stack]

On Mon, Feb 22, 2016 at 12:05 PM, Marvin Humphrey 
wrote:

> On Mon, Feb 22, 2016 at 11:32 AM, Todd Lipcon  wrote:
> > Porting over my +1 from the podling vote. Not sure if it's binding in the
> > IPMC context if I already voted as PPMC.
>
> Traditionally such IPMC votes carry over. It's good (but not a
> requirement) for the release manager to list the Mentor/IPMC votes
> they expect to carry over from the PPMC vote.
>

Thanks Marvin. I won't bother porting my +1 over then (smile).
St.Ack

Re: [VOTE] Release Apache Trafodion (incubating) 1.3.0-incubating

[Stack]

+1 (binding)

Vote ported from the trafodion dev list.

St.Ack

On Mon, Jan 4, 2016 at 2:41 PM, Roberta Marton 
wrote:

> Hello,
>
>
>
> The Apache Trafodion community has voted on and approved its first release
>
> – Apache Trafodion 1.3.0 –incubating (release candidate 5)
>
>
>
> Vote request on dev list:
>
>
> http://mail-archives.apache.org/mod_mbox/incubator-trafodion-dev/201512.mbox/ajax/%3C835f19bc6267f402358a71221c2b6afc%40mail.gmail.com%3E
>
>
>
> Vote result on dev list:
>
>
> http://mail-archives.apache.org/mod_mbox/incubator-trafodion-dev/201601.mbox/ajax/%3Cf41e5961dcf6f0d0d86ee766a6a93833%40mail.gmail.com%3E
>
>
>
> The commit id is 6ae976fdc60a683e954d867dab6ff30c55146c8f which corresponds
> to tag 1.3.0rc5:
>
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-trafodion.git;a=tag;h=5af956f989f1f32664bbec768e4f354516daa96b
>
>
>
> The release artifacts can be downloaded from:
>
>
> https://dist.apache.org/repos/dist/dev/incubator/trafodion/apache-trafodion-1.3.0-incubating
>
>
>
> Instructions on how to build and run Apache Trafodion are described here:
>
> http://trafodion.apache.org/download.html
>
>
>
> The source tar file has been signed with pgp key A44C5A05 which is included
> in the download location’s KEYS file:
>
> https://dist.apache.org/repos/dist/dev/incubator/trafodion/KEYS
>
>
>
> For changes included in the release, please see the release notes:
>
> http://trafodion.apache.org/release-notes-1-3-0.html
>
>
>
> The RAT tool was run on the source and the excluded are defined in the
>
> RAT_README.txt file found in the top level source directory.
>
>
>
> The following is a list of issues found during the podling review. It was
> determined that these issues can be fixed in a subsequent release, Jira’s,
> as noted, were created for each issue.
>
>
>
> TRAFODION-1733: Incorrect information included in LICENSE file
>
>   The Facebook copyright is already Apache and does not need to be in the
> LICENSE file
>
>   Asciidocs is included but not used
>
> TRAFODION-1725: missing licenses for:
>
>   MooTools Framework MIT licensed Copyright Valerio Proietti
>
>   swscanf.cpp/swprintf.cpp BSD license copyright Chris Torek
>
>   JQuery files - JQuery Foundation, Inc
>
> TRAFODION-1734: Suggestions for licensing improvements:
>
>   Should specify the type of license in the LICENSE file instead of
> requiring a lookup in the corresponding license text.
>
>   Should copy all license text to Apache Trafodion instead of specifying an
> external link.  The external license could change.
>
> TRAFODION-1735: There was a concern that changes made to some of the BSD
> copyrighted files were more than minor so additional copyright information
> may be required.
>
>
>
>
>
> Pursuant to the Release section of the Incubation Policy and with the
>
> endorsement of our mentors we would now like to request the permission  of
>
> the Incubator PMC to publish the release.
>
>
>
> The vote will be open for 72 hours.
>
>
>
> [ ] +1 approve
>
> [ ] +0 no opinion
>
> [ ] -1 disapprove (and reason why)
>
>
>
>Regards,
>
> Roberta Marton
>

Re: [VOTE] Accept Kudu into the Apache Incubator

[stack]

mented.
>
> == Source and Intellectual Property Submission Plan ==
>
> The Kudu codebase and web site is currently hosted on GitHub and will be
> transitioned to the ASF repositories during incubation. Kudu is already
> licensed under the Apache 2.0 license.
>
>
>
> Some portions of the code are imported from other open source projects
> under the Apache 2.0, BSD, or MIT licenses, with copyrights held by authors
> other than the initial committers. These copyright notices are maintained
> in those files as well as a top-level NOTICE.txt file. We believe this to
> be permissible under the license terms and ASF policies, and confirmed via
> a recent thread on general@incubator.apache.org .
>
>
>
> The “Kudu” name is not a registered trademark, though before the initial
> release of the project, we performed a trademark search and Cloudera’s
> legal counsel deemed it acceptable in the context of a data storage engine.
> There exists an unrelated open source project by the same name related to
> deployments on Microsoft’s Azure cloud service. We have been in contact
> with legal counsel from Microsoft and have obtained their approval for the
> use of the Kudu name.
>
>
>
> Cloudera currently owns several domain names related to Kudu (getkudu.io,
> kududb.io, et al) which will be transferred to the ASF and redirected to
> the official page during incubation.
>
>
>
> Portions of Kudu are protected by pending or published patents owned by
> Cloudera. Given the protections already granted by the Apache License, we
> do not anticipate any explicit licensing or transfer of this intellectual
> property.
>
> == External Dependencies ==
>
> The full set of dependencies and licenses are listed in
> https://github.com/cloudera/kudu/blob/master/LICENSE.txt
>
> and summarized here:
>
>  * '''Twitter Bootstrap''': Apache 2.0
>  * '''d3''': BSD 3-clause
>  * '''epoch JS library''': MIT
>  * '''lz4''': BSD 2-clause
>  * '''gflags''': BSD 3-clause
>  * '''glog''': BSD 3-clause
>  * '''gperftools''': BSD 3-clause
>  * '''libev''': BSD 2-clause
>  * '''squeasel''':MIT license
>  * '''protobuf''': BSD 3-clause
>  * '''rapidjson''': MIT
>  * '''snappy''': BSD 3-clause
>  * '''trace-viewer''': BSD 3-clause
>  * '''zlib''': zlib license
>  * '''llvm''': University of Illinois/NCSA Open Source (BSD-alike)
>  * '''bitshuffle''': MIT
>  * '''boost''': Boost license
>  * '''curl''': MIT
>  * '''libunwind''': MIT
>  * '''nvml''': BSD 3-clause
>  * '''cyrus-sasl''': Cyrus SASL license (BSD-alike)
>  * '''openssl''': OpenSSL License (BSD-alike)
>
>  * '''Guava''': Apache 2.0
>  * '''StumbleUpon Async''': BSD
>  * '''Apache Hadoop''': Apache 2.0
>  * '''Apache log4j''': Apache 2.0
>  * '''Netty''': Apache 2.0
>  * '''slf4j''': MIT
>  * '''Apache Commons''': Apache 2.0
>  * '''murmur''': Apache 2.0
>
>
> '''Build/test-only dependencies''':
>
>  * '''CMake''': BSD 3-clause
>  * '''gcovr''': BSD 3-clause
>  * '''gmock''': BSD 3-clause
>  * '''Apache Maven''': Apache 2.0
>  * '''JUnit''': EPL
>  * '''Mockito''': MIT
>
> == Cryptography ==
>
> Kudu does not currently include any cryptography-related code.
>
> == Required Resources ==
>
> === Mailing lists ===
>
>  * priv...@kudu.incubator.apache.org (PMC)
>  * comm...@kudu.incubator.apache.org (git push emails)
>  * iss...@kudu.incubator.apache.org (JIRA issue feed)
>  * d...@kudu.incubator.apache.org (Gerrit code reviews plus dev discussion)
>  * u...@kudu.incubator.apache.org (User questions)
>
>
> === Repository ===
>
>  * git://git.apache.org/kudu
>
> === Gerrit ===
>
> We hope to continue using Gerrit for our code review and commit workflow.
> The Kudu team has already been in contact with Jake Farrell to start
> discussions on how Gerrit can fit into the ASF. We know that several other
> ASF projects and podlings are also interested in Gerrit.
>
>
>
> If the Infrastructure team does not have the bandwidth to support Gerrit,
> we will continue to support our own instance of Gerrit for Kudu, and make
> the necessary integrations such that commits are properly authenticated and
> maintain sufficient provenance to uphold the ASF standards (e.g. via the
> solution adopted by the AsterixDB podling).
>
> == Issue Tracking ==
>
> We would like to import our current JIRA project into the ASF JIRA, such
> that our historical commit messages and code comments continue to reference
> the appropriate bug numbers.
>
> == Initial Committers ==
>
>  * Adar Dembo a...@cloudera.com
>  * Alex Feinberg a...@strlen.net
>  * Andrew Wang w...@apache.org
>  * Dan Burkert d...@cloudera.com
>  * David Alves dral...@apache.org
>  * Jean-Daniel Cryans jdcry...@apache.org
>  * Mike Percy mpe...@apache.org
>  * Misty Stanley-Jones mi...@apache.org
>  * Todd Lipcon t...@apache.org
>
> The initial list of committers was seeded by listing those contributors who
> have contributed 20 or more patches in the last 12 months, indicating that
> they are active and have achieved merit through participation on the
> project. We chose not to include other contributors who either have not yet
> contributed a significant number of patches, or whose contributions are far
> in the past and we don’t expect to be active within the ASF.
>
> == Affiliations ==
>
>  * Adar Dembo - Cloudera
>  * Alex Feinberg - Forward Networks
>  * Andrew Wang - Cloudera
>  * Dan Burkert - Cloudera
>  * David Alves - Cloudera
>  * Jean-Daniel Cryans - Cloudera
>  * Mike Percy - Cloudera
>  * Misty Stanley-Jones - Cloudera
>  * Todd Lipcon - Cloudera
>
> == Sponsors ==
>
> === Champion ===
>
>  * Todd Lipcon
>
> === Nominated Mentors ===
>
>  * Jake Farrell - ASF Member and Infra team member, Acquia
>  * Brock Noland - ASF Member, StreamSets
>  * Michael Stack - ASF Member, Cloudera
>  * Jarek Jarcec Cecho - ASF Member, Cloudera
>  * Chris Mattmann - ASF Member, NASA JPL and USC
>  * Julien Le Dem - Incubator PMC, Dremio
>  * Carl Steinbach - ASF Member, LinkedIn
>
> === Sponsoring Entity ===
>
> The Apache Incubator
>

Re: [VOTE] Accept Impala into the Apache Incubator

[stack]

+1 (binding)
St.Ack
On Nov 24, 2015 1:04 PM, "Henry Robinson"  wrote:

> Hi -
>
> The [DISCUSS] thread has been quiet for a few days, so I think there's been
> sufficient opportunity for discussion around our proposal to bring Impala
> to the ASF Incubator.
>
> I'd like to call a VOTE on that proposal, which is on the wiki at
> https://wiki.apache.org/incubator/ImpalaProposal, and which I've pasted
> below.
>
> During the discussion period, the proposal has been amended to add Brock
> Noland as a new mentor, to add one missed committer from the list and to
> correct some issues with the dependency list.
>
> Please cast your votes as follows:
>
> [] +1, accept Impala into the Incubator
> [] +/-0, non-counted vote to express a disposition
> [] -1, do not accept Impala into the Incubator (please give your reason(s))
>
> As with the concurrent Kudu vote, I propose leaving the vote open for a
> full seven days (to close at Tuesday, December 1st at noon PST), due to the
> upcoming US holiday.
>
> Thanks,
> Henry
>
> 
>
> = Abstract =
> Impala is a high-performance C++ and Java SQL query engine for data stored
> in Apache Hadoop-based clusters.
>
> = Proposal =
>
> We propose to contribute the Impala codebase and associated artifacts (e.g.
> documentation, web-site content etc.) to the Apache Software Foundation
> with the intent of forming a productive, meritocratic and open community
> around Impala’s continued development, according to the ‘Apache Way’.
>
> Cloudera owns several trademarks regarding Impala, and proposes to transfer
> ownership of those trademarks in full to the ASF.
>
> = Background =
> Engineers at Cloudera developed Impala and released it as an
> Apache-licensed open-source project in Fall 2012. Impala was written as a
> brand-new, modern C++ SQL engine targeted from the start for data stored in
> Apache Hadoop clusters.
>
> Impala’s most important benefit to users is high-performance, making it
> extremely appropriate for common enterprise analytic and business
> intelligence workloads. This is achieved by a number of software
> techniques, including: native support for data stored in HDFS and related
> filesystems, just-in-time compilation and optimization of individual query
> plans, high-performance C++ codebase and massively-parallel distributed
> architecture. In benchmarks, Impala is routinely amongst the very highest
> performing SQL query engines.
>
> = Rationale =
>
> Despite the exciting innovation in the so-called ‘big-data’ space, SQL
> remains by far the most common interface for interacting with data in both
> traditional warehouses and modern ‘big-data’ clusters. There is clearly a
> need, as evidenced by the eager adoption of Impala and other SQL engines in
> enterprise contexts, for a query engine that offers the familiar SQL
> interface, but that has been specifically designed to operate in massive,
> distributed clusters rather than in traditional, fixed-hardware,
> warehouse-specific deployments. Impala is one such query engine.
>
> We believe that the ASF is the right venue to foster an open-source
> community around Impala’s development. We expect that Impala will benefit
> from more productive collaboration with related Apache projects, and under
> the auspices of the ASF will attract talented contributors who will push
> Impala’s development forward at pace.
>
> We believe that the timing is right for Impala’s development to move
> wholesale to the ASF: Impala is well-established, has been Apache-licensed
> open-source for more than three years, and the core project is relatively
> stable. We are excited to see where an ASF-based community can take Impala
> from this strong starting point.
>
> = Initial Goals =
> Our initial goals are as follows:
>
>  * Establish ASF-compatible engineering practices and workflows
>  * Refactor and publish existing internal build scripts and test
> infrastructure, in order to make them usable by any community member.
>  * Transfer source code, documentation and associated artifacts to the ASF.
>  * Grow the user and developer communities
>
> = Current Status =
>
> Impala is developed as an Apache-licensed open-source project. The source
> code is available at http://github.com/cloudera/Impala, and developer
> documentation is at https://github.com/cloudera/Impala/wiki. The majority
> of commits to the project have come from Cloudera-employed developers, but
> we have accepted some contributions from individuals from other
> organizations.
>
> All code reviews are done via a public instance of the Gerrit review tool
> at http://gerrit.cloudera.org:8080/, and discussed on a public mailing
> list. All patches must be reviewed before they are accepted into the
> codebase, via a voting mechanism that is similar to that used on Apache
> projects such as Hadoop and HBase.
>
> Before a patch is committed, it must pass a suite of pre-commit tests.
> These tests are currently run on Cloudera’s internal 

Re: [VOTE] Accept S2Graph into Apache Incubation

[Stack]

+1 (binding)

On Mon, Nov 23, 2015 at 4:53 PM, Hyunsik Choi  wrote:

> Hello folks,
>
> Thanks for all the feedback on the S2Graph Proposal.
>
> I would like to call for a [VOTE] on S2Graph joining the ASF as an
> incubation project.
>
> The vote is open for at least 72 hours:
>
> [ ] +1 accept S2Graph in the Incubator
> [ ] ±0
> [ ] -1 (please give reason)
>
> S2Graph provides a scalable distributed graph database engine over a
> key/value store such as HBase. S2Graph provides a fully asynchronous
> API to manipulate data as a property graph model and fast
> breadth-first-search queries over the graph. S2Graph is designed for
> OLTP-like workloads on graph data sets instead of batch processing,
> and it also provides INSERT/UPDATE operations on them.
>
> The proposal is available on the wiki here:
> https://wiki.apache.org/incubator/S2GraphProposal
>
> Best regards,
> Hyunsik
>
>
> 
>
> 
> = S2Graph Proposal =
>
> == Abstract ==
> S2Graph is a distributed and scalable OLTP graph database built on
> Apache HBase to support fast traversal of extremely large graphs.
>
> == Proposal ==
> S2Graph provides a scalable distributed graph database engine over a
> key/value store such as HBase. S2Graph provides a fully asynchronous
> API to manipulate data as a property graph model and fast
> breadth-first-search queries over the graph. S2Graph is designed for
> OLTP-like workloads on graph data sets instead of batch processing.
> Also, S2Graph provides INSERT/UPDATE operations. Its name 'S2Graph' is
> an abbreviated word of '''S'''uper '''S'''imple '''Graph''' Database.
>
> Here are additional materials to introduce S2Graph.
>  * HBaseCon 2015 - http://www.slideshare.net/HBaseCon/use-cases-session-5
>  * Apache: Big Data 2015 -
> http://schd.ws/hosted_files/apachebigdata2015/06/s2graph_apache_con.pdf
>
> == Background ==
> S2Graph initially started as an internal project at Kakao.com to
> efficiently store user relations and user activities as one large
> graph and to provide a unified query interface to traverse the graph.
> It was open sourced on Github about a 3 months ago in June 2015.
>
> Over time, S2Graph using HBase as the storage tier has begun by
> adapted into various applications, such as messaging, social feeds,
> and realtime recommendations at Kakao.
>
> Users can benefit by using S2Graph`s generalized high level graph
> abstraction API instead of querying via low-level key/value APIs, just
> as Apache Phoenix provides a SQL layer over HBase.
>
> == Rationale ==
> Graph data (highly interconnected data) is very abundant and important
> these days. When users have a multitude of relationships, each with
> complex properties associated with them, a graph model is more
> intuitive and efficient than tabular formats (RDBMS).
>
> There are many ASF projects that provide SQL tiers, but there is no
> ASF projects that provide a scalable graph layer on top of the
> existing hadoop ecosystem. When graph data grows to the trillion edge
> scale, the process of traversing takes a long time and can be costly.
> However, with the benefit of HBase`s scalable architecture, S2Graph
> can traverse large graphs in a breadth-first-search manner
> efficiently.
>
> S2Graph also interoperates with several existing Apache projects
> (HBase, Apache Spark) to provide means of merging real time events and
> batch processed data using the property graph data model.
>
> Many developers run their own domain specific API servers to serve
> their data products, but a graph model is general and the S2Graph API
> fully supports traversal of the graph, so it can be used as a scalable
> general purpose API serving layer for various domains. As long as data
> can be modeled as graph, then users can avoid tedious work developing
> customized API servers if they use S2Graph.
>
> == Initial Goals ==
> The initial goals will be to move the existing codebase to Apache and
> integrate with the Apache development process. Once this is
> accomplished, we plan for incremental development and releases that
> follow the Apache guidelines.
>
> == Current Status ==
>
> === Meritocracy ===
> S2Graph operated on meritocratic principles from the get go.
> Currently, all the discussions pertaining to S2Graph development are
> public on Github. The current incubation proposal includes the major
> code contributors to S2Graph. Several additional people have worked on
> the S2graph codebase for industry use cases and would be interested in
> becoming committers. We are starting with a small committer group and
> we plan to add additional committers following an open merit-based
> decision process during the incubation phase.
>
> === Community ===
> We have already begun building a community but at this time the
> community consists only of S2Graph developers – all Kakao employees –
> and prospective users. S2Graph seeks to develop developer 

Re: [DISCUSS] S2Graph Incubator Proposal

[Stack]

Good luck!

On Mon, Nov 23, 2015 at 4:31 PM, Hyunsik Choi <hyun...@apache.org> wrote:

> Stack,
>
> I greatly appreciate your reviews. I reflected almost all comments you
> gave to the proposal. I'll make a vote thread soon.
>
> Best regards,
> Hyunsik
>
> On Thu, Nov 19, 2015 at 2:57 PM, Hyunsik Choi <hyun...@apache.org> wrote:
> > Thank you Stack for your kind work. I just understood. I will improve
> > the proposal from your suggestion.
> >
> > Best regards,
> > Hyunsik
> >
> > On Thu, Nov 19, 2015 at 11:35 AM, Stack <st...@duboce.net> wrote:
> >> On Wed, Nov 18, 2015 at 5:04 PM, Hyunsik Choi <hyun...@apache.org>
> wrote:
> >>
> >>> Thank you very much Stack! It definitely looks better than just wiki.
> >>> It would be helpful to improve the proposal.
> >>>
> >>>
> >> To be clear, proposal needs to be on the wiki. I just moved it over so I
> >> could show my edits as 'suggested' rather than change the original. Take
> >> whatever edits you think improve the proposal and then apply them to the
> >> wiki.
> >> St.Ack
> >>
> >>
> >>
> >>
> >>> Best regards,
> >>> Hyunsik
> >>>
> >>> On Tue, Nov 17, 2015 at 10:20 PM, Stack <st...@duboce.net> wrote:
> >>> > Glad to see s2graph being put up as an incubator project.
> >>> >
> >>> > Here [1] are some suggested edits to try and help strengthen the
> proposal
> >>> > before it goes up for a vote. Hopefully they help.
> >>> >
> >>> > St.Ack
> >>> > 1.
> >>> >
> >>>
> https://docs.google.com/document/d/19iNc0u_-9ogb0kDC-WnLoWWg9J_LFeuSGB8GF_rQfEs/edit?usp=sharing
> >>> >
> >>> > On Tue, Nov 17, 2015 at 3:59 PM, Hyunsik Choi <hyun...@apache.org>
> >>> wrote:
> >>> >
> >>> >> Thank you Henry. Yes, we already had enough time to discuss the
> >>> >> S2Graph proposal. I'll make a vote thread soon.
> >>> >>
> >>> >> Best regards,
> >>> >> Hyunsik
> >>> >>
> >>> >> On Tue, Nov 17, 2015 at 2:22 PM, Henry Saputra <
> henry.sapu...@gmail.com
> >>> >
> >>> >> wrote:
> >>> >> > Looks like we have positive responses. I think it is time for VOTE
> >>> >> thread :)
> >>> >> >
> >>> >> > On Friday, November 6, 2015, Hyunsik Choi <hyun...@apache.org>
> wrote:
> >>> >> >
> >>> >> >> Hi folks,
> >>> >> >>
> >>> >> >> We would like to start a discussion on S2Graph as an incubation
> >>> project.
> >>> >> >>
> >>> >> >> S2Graph is a distributed and scalable OLTP graph database built
> on
> >>> >> >> HBase. It provides interactive queries for
> vertex/edge/sub-graphs on
> >>> >> >> extremely large graph data sets as well as insertion and update
> >>> >> >> operations.
> >>> >> >>
> >>> >> >> S2Graph was already introduced in Apache BigData and HBaseCon
> this
> >>> year.
> >>> >> >>
> >>> >> >> The proposal is available at :
> >>> >> >> https://wiki.apache.org/incubator/S2GraphProposal
> >>> >> >>
> >>> >> >> We are looking forward to any feedback. In addition, we are
> looking
> >>> >> >> for volunteers as mentors.
> >>> >> >>
> >>> >> >> Best regards,
> >>> >> >> Hyunsik
> >>> >> >>
> >>> >> >>
> -
> >>> >> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >>> >> >> <javascript:;>
> >>> >> >> For additional commands, e-mail:
> general-h...@incubator.apache.org
> >>> >> >> <javascript:;>
> >>> >> >>
> >>> >> >>
> >>> >>
> >>> >>
> -
> >>> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >>> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>> >>
> >>> >>
> >>>
> >>> -
> >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >>> For additional commands, e-mail: general-h...@incubator.apache.org
> >>>
> >>>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] S2Graph Incubator Proposal

[Stack]

On Wed, Nov 18, 2015 at 5:04 PM, Hyunsik Choi <hyun...@apache.org> wrote:

> Thank you very much Stack! It definitely looks better than just wiki.
> It would be helpful to improve the proposal.
>
>
To be clear, proposal needs to be on the wiki. I just moved it over so I
could show my edits as 'suggested' rather than change the original. Take
whatever edits you think improve the proposal and then apply them to the
wiki.
St.Ack




> Best regards,
> Hyunsik
>
> On Tue, Nov 17, 2015 at 10:20 PM, Stack <st...@duboce.net> wrote:
> > Glad to see s2graph being put up as an incubator project.
> >
> > Here [1] are some suggested edits to try and help strengthen the proposal
> > before it goes up for a vote. Hopefully they help.
> >
> > St.Ack
> > 1.
> >
> https://docs.google.com/document/d/19iNc0u_-9ogb0kDC-WnLoWWg9J_LFeuSGB8GF_rQfEs/edit?usp=sharing
> >
> > On Tue, Nov 17, 2015 at 3:59 PM, Hyunsik Choi <hyun...@apache.org>
> wrote:
> >
> >> Thank you Henry. Yes, we already had enough time to discuss the
> >> S2Graph proposal. I'll make a vote thread soon.
> >>
> >> Best regards,
> >> Hyunsik
> >>
> >> On Tue, Nov 17, 2015 at 2:22 PM, Henry Saputra <henry.sapu...@gmail.com
> >
> >> wrote:
> >> > Looks like we have positive responses. I think it is time for VOTE
> >> thread :)
> >> >
> >> > On Friday, November 6, 2015, Hyunsik Choi <hyun...@apache.org> wrote:
> >> >
> >> >> Hi folks,
> >> >>
> >> >> We would like to start a discussion on S2Graph as an incubation
> project.
> >> >>
> >> >> S2Graph is a distributed and scalable OLTP graph database built on
> >> >> HBase. It provides interactive queries for vertex/edge/sub-graphs on
> >> >> extremely large graph data sets as well as insertion and update
> >> >> operations.
> >> >>
> >> >> S2Graph was already introduced in Apache BigData and HBaseCon this
> year.
> >> >>
> >> >> The proposal is available at :
> >> >> https://wiki.apache.org/incubator/S2GraphProposal
> >> >>
> >> >> We are looking forward to any feedback. In addition, we are looking
> >> >> for volunteers as mentors.
> >> >>
> >> >> Best regards,
> >> >> Hyunsik
> >> >>
> >> >> -
> >> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> >> <javascript:;>
> >> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >> >> <javascript:;>
> >> >>
> >> >>
> >>
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] S2Graph Incubator Proposal

[Stack]

Glad to see s2graph being put up as an incubator project.

Here [1] are some suggested edits to try and help strengthen the proposal
before it goes up for a vote. Hopefully they help.

St.Ack
1.
https://docs.google.com/document/d/19iNc0u_-9ogb0kDC-WnLoWWg9J_LFeuSGB8GF_rQfEs/edit?usp=sharing

On Tue, Nov 17, 2015 at 3:59 PM, Hyunsik Choi  wrote:

> Thank you Henry. Yes, we already had enough time to discuss the
> S2Graph proposal. I'll make a vote thread soon.
>
> Best regards,
> Hyunsik
>
> On Tue, Nov 17, 2015 at 2:22 PM, Henry Saputra 
> wrote:
> > Looks like we have positive responses. I think it is time for VOTE
> thread :)
> >
> > On Friday, November 6, 2015, Hyunsik Choi  wrote:
> >
> >> Hi folks,
> >>
> >> We would like to start a discussion on S2Graph as an incubation project.
> >>
> >> S2Graph is a distributed and scalable OLTP graph database built on
> >> HBase. It provides interactive queries for vertex/edge/sub-graphs on
> >> extremely large graph data sets as well as insertion and update
> >> operations.
> >>
> >> S2Graph was already introduced in Apache BigData and HBaseCon this year.
> >>
> >> The proposal is available at :
> >> https://wiki.apache.org/incubator/S2GraphProposal
> >>
> >> We are looking forward to any feedback. In addition, we are looking
> >> for volunteers as mentors.
> >>
> >> Best regards,
> >> Hyunsik
> >>
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> 
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >> 
> >>
> >>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache htrace-4.0.1-incubating

[Stack]

Carry-over from the htrace dev list, +1 (binding)
St.Ack

On Tue, Sep 22, 2015 at 9:37 PM, Colin P. McCabe  wrote:

> Apache HTrace (incubating), has voted to release the below referenced
> Apache HTrace 4.0.1-incubating release candidate.
>
> Dear IPMC, please vote on our second release candidate as an Apache
> Incubator project.
>
> The source tarball, hashes, and signing are here:
> http://people.apache.org/~cmccabe/htrace/releases/4.0.1/rc1
>
> The jars have been staged here:
> https://repository.apache.org/content/repositories/orgapachehtrace-1020
>
> The KEYS file with the key used signing is available here:
> https://dist.apache.org/repos/dist/release/incubator/htrace/KEYS
>
> 12 issues were resolved in this release:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12333550=Html=12315924
>
> The vote will run for 3 days.
>
> [ ] +1 Release this package as Apache HTrace 4.0.1-incubating
> [ ] +0 no opinion
> [ ] -1 Do not release this package because ...
>
> best,
> Colin
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Graduate Calcite from the Apache Incubator

[Stack]

+1 (binding)
St.Ack

On Mon, Sep 14, 2015 at 6:56 PM, Julian Hyde  wrote:

> This is a vote for Calcite to become a top-level project.
>
> Since joining the Incubator in May, 2014, the Calcite
> community has:
> * Produced eight IPMC-approved releases under two release
>   managers;
> * Added five new committers and one new PPMC member;
> * Collaborated successfully with several other Apache
> projects (Drill, Hive, Kylin, Phoenix, Samza);
> * Grown into an active community (typical monthly activity
>   is 100 emails, 30 commits and 20 issues fixed);
> * Conducted a successful community vote to graduate with
>   20 +1 votes, of which 2 were from our mentors, 12 were
>   from committers, and 6 were from IPMC members.
>
> Further information: the discussion on the dev list [1],
> vote thread [2] and result [3]. Also relevant are the
> incubation status page [4] and a thread on this list
> requesting review of whether Calcite met the criteria to
> graduate [5].
>
> Below is our proposed resolution for the Board.
>
> Please vote:
>
> [ ] +1 Graduate Apache Calcite as a top-level project
> [ ] +0
> [ ] -1 Do not graduate Apache Calcite because…
>
> Here is my vote:
> +1 (binding)
>
> Voting will last 72 hours, ending at 19:00 Pacific on
> September 17th.
>
> Julian Hyde, on behalf of Calcite PPMC
>
> [1] http://s.apache.org/ZPC
> [2] http://s.apache.org/rvB
> [3] http://s.apache.org/sv
> [4] http://incubator.apache.org/projects/calcite.html
> [5] http://s.apache.org/itP
>
> - - - snip - - -
>
> WHEREAS, the Board of Directors deems it to be in the best
> interests of the Foundation and consistent with the
> Foundation's purpose to establish a Project Management
> Committee charged with the creation and maintenance of
> open-source software, for distribution at no charge to the
> public, related to parsing and planning queries on data in a
> wide variety of formats.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache Calcite
> Project", be and hereby is established pursuant to Bylaws of
> the Foundation; and be it further
>
> RESOLVED, that the Apache Calcite Project be and hereby is
> responsible for the creation and maintenance of software
> related to parsing and planning queries on data in a wide
> variety of formats; and be it further
>
> RESOLVED, that the office of "Vice President, Apache
> Calcite" be and hereby is created, the person holding such
> office to serve at the direction of the Board of Directors
> as the chair of the Apache Calcite Project, and to have
> primary responsibility for management of the projects within
> the scope of responsibility of the Apache Calcite Project;
> and be it further
>
> RESOLVED, that the persons listed immediately below be and
> hereby are appointed to serve as the initial members of the
> Apache Calcite Project:
>
> * Alan Gates 
> * Aman Sinha 
> * Ashutosh Chauhan 
> * James R. Taylor 
> * Jacques Nadeau 
> * Jesús Camacho Rodríguez 
> * Jinfeng Ni 
> * John Pullokkaran 
> * Julian Hyde 
> * Nick Dimiduk 
> * Steven Noels 
> * Ted Dunning 
> * Vladimir Sitnikov 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Julian Hyde be
> appointed to the office of Vice President, Apache Calcite,
> to serve in accordance with and subject to the direction of
> the Board of Directors and the Bylaws of the Foundation
> until death, resignation, retirement, removal or
> disqualification, or until a successor is appointed; and be
> it further
>
> RESOLVED, that the Apache Calcite Project be and hereby is
> tasked with the migration and rationalization of the Apache
> Incubator Calcite podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache
> Incubator Calcite podling encumbered upon the Apache
> Incubator Project are hereafter discharged.
>
> - - - end - - -
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache htrace-4.0.0-incubating

[Stack]

+1

(Carry-over from the htrace dev list)

St.Ack

On Wed, Sep 9, 2015 at 4:45 PM, Colin P. McCabe  wrote:

> Apache HTrace (incubating), has voted to release the below referenced
> Apache HTrace 4.0.0-incubating release candidate.
>
> Dear IPMC, please vote on our second release candidate as an Apache
> Incubator project.
>
> The source tarball, hashes, and signing are here:
> http://people.apache.org/~cmccabe/htrace/releases/4.0.0/rc0/
>
> Related maven artifacts are posted here:
> https://repository.apache.org/content/repositories/orgapachehtrace-1017
>
> The tag for the RC is here:
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-htrace.git;a=commit;h=8cf1e01967f2ad10f7c6d5d099b724c520613a7d
>
> The KEYS file with the key used signing is available here:
> https://dist.apache.org/repos/dist/release/incubator/htrace/KEYS
>
> 60 issues were resolved in this release:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315924=12333022
>
> The vote will be open for 72 hours.
>
> [ ] +1 Release this package as Apache HTrace 4.0.0-incubating
> [ ] +0 no opinion
> [ ] -1 Do not release this package because ...
>
> best,
> Colin
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

[RESULT][VOTE] Accept Trafodion into Apache Incubator

[Stack]

WIth 10 binding +1 votes and 7 non-binding +1 votes, and with no votes
against, the vote passes.

Thanks to all who voted.

Let us start in on the work getting Trafodiion set up as an incubator
podling.

Yours,
St.Ack

P.S. Here is a link to the vote thread:
http://mail-archives.apache.org/mod_mbox/incubator-general/201505.mbox/%3CCADcMMgGO-WXFc75U1E%2BcvpF%3D%3Dv%2BPEaTfoOycy%3D-tDPLLvG3irA%40mail.gmail.com%3E


On Tue, May 19, 2015 at 2:27 PM, Stack st...@duboce.net wrote:

 Following the discussion earlier in the thread [1], I would like to call
 a VOTE to accept Trafodion as a new Apache Incubator project.

 The proposal is available on the wiki at [2] and is also attached to this
 mail.

 The VOTE is open for at least the next 72 hours:

  [ ] +1 accept Trafodion into the Apache Incubator
  [ ] ±0 Abstain
  [ ] -1 because...

 I am +1 (binding)

 Thank you,
 St.Ack

 1.
 http://mail-archives.apache.org/mod_mbox/incubator-general/201505.mbox/%3CCADcMMgG4NHtmFZ519iqgZLA8Lj-E7VmaQ%3Dr8C011LuS5pR0Vkw%40mail.gmail.com%3E
 2.  https://wiki.apache.org/incubator/TrafodionProposal
 https://wiki.apache.org/incubator/TrafodionProposal#preview



 Trafodion Apache Incubator Proposal

 Abstract

 Trafodion is a webscale SQL-on-Hadoop solution enabling transactional or
 operational workloads on Hadoop.

 Proposal

 Apache Trafodion builds on the scalability, elasticity, and flexibility of
 Hadoop. Trafodion extends Hadoop to provide guaranteed transactional
 integrity, enabling new kinds of big data applications to run on Hadoop. Key
 features of Apache Trafodion include:

 * Full-functioned ANSI SQL language support
 * JDBC/ODBC connectivity for Linux/Windows clients
 * Distributed ACID transaction protection across multiple statements,
 tables and rows
 * Performance improvements for OLTP workloads with compile-time and
 run-time optimizations
 * Support for large data sets using a parallel-aware query optimizer
 * ANSI SQL security and data integrity constraints including referential
 integrity

 Hewlett-Packard Company submits this proposal to donate its Apache
 License, Version 2.0 open source project known as Trafodion, its source
 code, documentation, and web site content to the Apache Software Foundation
 in order to build an open source community

 Background

 Trafodion is an open source project sponsored by HP, incubated at HP Labs
 and HP-IT, to develop an enterprise-class SQL-on-Hadoop solution targeting
 big data transactional or operational workloads. HP publically announced
 the open source project and uploaded the source code to GitHub in June 2014.

 The SQL compiler, optimizer and executor components of Trafodion have a
 rich heritage. Under development since 1993, they were released as
 commercial closed source software in various flavors such as HP NonStop
 SQL/MX and HP Neoview. NonStop SQL/MX was designed for online transaction
 processing on HP’s NonStop (formerly Tandem) fault-tolerant servers and is
 known for its high availability, scalability, and performance. Hundreds of
 companies and thousands of servers are running mission-critical
 applications today on NonStop SQL/MX. In addition, much of these components
 today are running internal to HP as the core of its Enterprise Data
 Warehouse (EDW), managing over a PB of data.

 Starting in 2013, the software was modified to run on HBase and a new
 distributed transaction manager was written to run as an HBase co-processor.

 Unlike most NOSQL and other SQL-on-Hadoop open source projects, Trafodion
 provides comprehensive ANSI SQL language support including full-functioned
 data definition (DDL), data manipulation (DML), transaction control (TCL)
 and database utility support.

 Trafodion provides comprehensive and standard SQL data manipulation
 support including SELECT, INSERT, UPDATE, DELETE, and UPSERT/MERGE syntax
 with language options including join variants, unions, where predicates,
 aggregations (group by and having), sort ordering, sampling, correlated and
 nested sub-queries, cursors, and many SQL functions.

 Utilities are provided for updating table statistics used by the optimizer
 for costing (i.e. selectivity/cardinality estimates) plan alternatives, for
 displaying the chosen SQL execution plan, plan shaping, backup and
 restoring the database, data loading and unloading, and a command line
 utility for interfacing with the database engine.

 Explicit control statements are provided to allow applications to define
 transaction boundaries and to abort transactions when warranted, including
 BEGIN WORK, COMMIT WORK, ROLLBACK WORK and SET TRANSACTION.

 Trafodion supports ANSI’s grant/revoke semantics to define user and role
 privileges in terms of managing and accessing the database objects.

 Rationale

 The name “Trafodion” (the Welsh word for transactions, pronounced
 “Tra-vod-eee-on”) was chosen specifically to emphasize the differentiation
 that Trafodion provides in closing a critical gap in the Hadoop ecosystem

[VOTE] Accept Trafodion into Apache Incubator

[Stack]

, such as Apache Hive, Apache Drill, and Apache Phoenix. These
are more focused on reporting and analytics across data structures
supported on HDFS. In comparison to all of these technologies Trafodion
provides a very complete implementation of ANSI SQL, one of the most
sophisticated optimizers for such workloads, a completely parallel data
flow architecture that does not materialize intermediate results unless
necessary, full ACID transactional support, ANSI GRANT/REVOKE security, and
other capabilities that would take decades to build in these products. On
the other hand currently Trafodion is just focused on HBase and querying
Hive, whereas Hive and Drill provide access to other data formats in HDFS.

An Excessive Fascination with the Apache Brand

We understand the reputation and value of the Apache brand, and no doubt
believe that it will help us attract contributors and users. Our primary
goal is to follow a proven, open source development and community building
model that will make Trafodion successful and enable better collaboration
with other Apache projects in the Hadoop ecosystem. We also understand the
rules and guidelines about the use of the Apache brand and intend to follow
them.

Documentation

Documentation and technical details on Trafodion can be found at:
http://www.trafodion.org/

Initial Source

The source is available today in a public github repository:
https://github.com/trafodion/trafodion.

Source and Intellectual Property Submission Plan

The source code has already been released under the Apache License, Version
2. The manuals have been released in Adobe PDF format. As part of the
submission process, the source for the manuals will be converted from a
proprietary DocBook XML format to AsciiDoc.

External Dependencies

Two dependencies do not have Apache compatible licenses and will be
addressed as we enter incubation. One dependency is log4cpp, which is
licensed under the LGPL. A compatible alternative might be Apache incubator
project log4cxx. The other dependency is unixodbc, which is used as the
ODBC driver manager. We will look into how Apache Hive manages being able
to use this incompatible software and do similar. All other dependencies
have Apache compatible licenses, including Apache 2.0, MIT/X11, MIT, and
BSD.

Cryptography

Trafodion does not contain any cryptographic code. It does call
cryptographic libraries: OpenSSL for C++ code and Java Cryptography
Extension (JCE) for Java code.

Required Resources

Mailing Lists

priv...@trafodion.incubator.apache.org
d...@trafodion.incubator.apache.org comm...@trafodion.incubator.apache.org

Git Repository

https://git-wip-us.apache.org/repos/afs/incubator-trafodion.git

Issue Tracking

JIRA: JIRA Trafodion (Trafodion)


Initial Committers and Affiliation

Dave Birdsall, Hewlett-Packard Company, Dave.BirdsallAThpDOTcom
Matt Brown, Hewlett-Packard Company, mattbrownAThpDOTcom
Tharak Capirala, Hewlett-Packard Company, Tharak.CapiralaAThpDOTcom
Alice Chen, Hewlett-Packard Company, Alice.ChenAThpDOTcom
John DeRoo, Hewlett-Packard Company, John.DerooAThpDOTcom
Roberta Marton, Hewlett-Packard Company, Roberta.MartonAThpDOTcom
Amanda Moran, Hewlett-Packard Company, Amanda.Kay.MoranAThpDOTcom
Suresh Subbiah, Hewlett-Packard Company, Suresh.SubbiahAThpDOTcom
Sandyha Sundaresan, Hewlett-Packard Company,
Sandhya.SundaresanAThpDOTcom

Sponsors

Champion

Michael Stack, StackATapacheDOTorg

Nominated Mentors

Andrew Purtell apurtellATapacheDOTorg
Devaraj Das, ddasATapacheDOTor
Enis Söztutar, EnisATapacheDOTorg
Lars Hofhansl, larshATapacheDOTorg
Michael Stack, StackATapacheDOTorg
Roman Shaposhnik, rshaposhnikATpivotalDOTio

Sponsoring Entity

Apache Incubator PMC

Re: [DISCUSS] Trafodion Incubation Proposal

[Stack]

On Mon, May 18, 2015 at 2:49 PM, Roman Shaposhnik ro...@shaposhnik.org
wrote:

 On Mon, May 18, 2015 at 1:25 PM, Stack st...@duboce.net wrote:
  Unless there are other comments on the proposal, I will move to start a
  VOTE on accepting Trafodion into incubator tomorrow.

 Given that there were a few folks volunteering as mentors (thanks!!!)
 should we have the updated version of the proposal posted on this
 thread before opening up a VOTE?

 Thanks,
 Roman.

 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org


Sounds good. I added volunteers Andy, Devaraj, Lars, and Enis. I left off
Konstantin since he seems well-loaded mentoring other projects for now. I
also removed the sentence soliciting mentors.

Will put up VOTE tomorrow.

St.Ack


Trafodion Apache Incubator Proposal

Abstract

Trafodion is a webscale SQL-on-Hadoop solution enabling transactional or
operational workloads on Hadoop.

Proposal

Apache Trafodion builds on the scalability, elasticity, and flexibility of
Hadoop. Trafodion extends Hadoop to provide guaranteed transactional
integrity, enabling new kinds of big data applications to run on Hadoop. Key
features of Apache Trafodion include:

* Full-functioned ANSI SQL language support
* JDBC/ODBC connectivity for Linux/Windows clients
* Distributed ACID transaction protection across multiple statements,
tables and rows
* Performance improvements for OLTP workloads with compile-time and
run-time optimizations
* Support for large data sets using a parallel-aware query optimizer
* ANSI SQL security and data integrity constraints including referential
integrity

Hewlett-Packard Company submits this proposal to donate its Apache License,
Version 2.0 open source project known as Trafodion, its source code,
documentation, and web site content to the Apache Software Foundation in
order to build an open source community

Background

Trafodion is an open source project sponsored by HP, incubated at HP Labs
and HP-IT, to develop an enterprise-class SQL-on-Hadoop solution targeting
big data transactional or operational workloads. HP publically announced
the open source project and uploaded the source code to GitHub in June 2014.

The SQL compiler, optimizer and executor components of Trafodion have a
rich heritage. Under development since 1993, they were released as
commercial closed source software in various flavors such as HP NonStop
SQL/MX and HP Neoview. NonStop SQL/MX was designed for online transaction
processing on HP’s NonStop (formerly Tandem) fault-tolerant servers and is
known for its high availability, scalability, and performance. Hundreds of
companies and thousands of servers are running mission-critical
applications today on NonStop SQL/MX. In addition, much of these components
today are running internal to HP as the core of its Enterprise Data
Warehouse (EDW), managing over a PB of data.

Starting in 2013, the software was modified to run on HBase and a new
distributed transaction manager was written to run as an HBase co-processor.

Unlike most NOSQL and other SQL-on-Hadoop open source projects, Trafodion
provides comprehensive ANSI SQL language support including full-functioned
data definition (DDL), data manipulation (DML), transaction control (TCL)
and database utility support.

Trafodion provides comprehensive and standard SQL data manipulation support
including SELECT, INSERT, UPDATE, DELETE, and UPSERT/MERGE syntax with
language options including join variants, unions, where predicates,
aggregations (group by and having), sort ordering, sampling, correlated and
nested sub-queries, cursors, and many SQL functions.

Utilities are provided for updating table statistics used by the optimizer
for costing (i.e. selectivity/cardinality estimates) plan alternatives, for
displaying the chosen SQL execution plan, plan shaping, backup and
restoring the database, data loading and unloading, and a command line
utility for interfacing with the database engine.

Explicit control statements are provided to allow applications to define
transaction boundaries and to abort transactions when warranted, including
BEGIN WORK, COMMIT WORK, ROLLBACK WORK and SET TRANSACTION.

Trafodion supports ANSI’s grant/revoke semantics to define user and role
privileges in terms of managing and accessing the database objects.

Rationale

The name “Trafodion” (the Welsh word for transactions, pronounced
“Tra-vod-eee-on”) was chosen specifically to emphasize the differentiation
that Trafodion provides in closing a critical gap in the Hadoop ecosystem.
Trafodion builds on the scalability, elasticity, and flexibility of Hadoop.
Trafodion extends Hadoop to provide guaranteed transactional integrity,
enabling new kinds of big data applications to run on Hadoop.

Current Status

HP released the Trafodion code under the Apache License, Version 2, in June
of 2014. Since

Re: [DISCUSS] Trafodion Incubation Proposal

[Stack]

Unless there are other comments on the proposal, I will move to start a
VOTE on accepting Trafodion into incubator tomorrow.
Thanks,
St.Ack

On Thu, May 14, 2015 at 8:02 PM, Venkat Ranganathan 
vranganat...@hortonworks.com wrote:

 Glad to see Trafodion submitted as an Apache Incubator project.

 Good luck

 Venkat


 On May 14, 2015, at 4:13 PM, Birdsall, Dave dave.birds...@hp.com
 wrote:

 Hi Lars,

 Glad to have you on the mentor list!

 Dave

 -Original Message-
 From: lars hofhansl [mailto:la...@apache.org]
 Sent: Thursday, May 14, 2015 3:39 PM
 To: general@incubator.apache.org
 Subject: Re: [DISCUSS] Trafodion Incubation Proposal

 Bit belated... I'd be happy and honored to be a mentor for Trafodian.
 -- Lars
   From: Stack st...@duboce.net
  To: general@incubator.apache.org
  Sent: Friday, May 8, 2015 2:59 PM
  Subject: [DISCUSS] Trafodion Incubation Proposal

 I would like to start up a discussion on Trafodion joining the ASF as an
 incubating project.

 Trafodion is a webscale SQL-on-Hadoop solution that enables transactional
 or operational workloads on Hadoop, .

 The proposal is available on the wiki here:
 https://wiki.apache.org/incubator/TrafodionProposal#preview

 The proposal text is also attached to the end of this email.

 Trafodion is a rich, storied SQL engine that has recently been ported to
 run on HBase and Hadoop. I think it would make for a fine addition to the
 Apache family of projects  It would be good to hear what others think.

 Thank you in advance for giving the proposal a read.

 Yours,
 St.Ack


 Trafodion Apache Incubator Proposal

 Abstract

 Trafodion is a webscale SQL-on-Hadoop solution enabling transactional or
 operational workloads on Hadoop.

 Proposal

 Apache Trafodion builds on the scalability, elasticity, and flexibility of
 Hadoop. Trafodion extends Hadoop to provide guaranteed transactional
 integrity, enabling new kinds of big data applications to run on Hadoop.
 Key features of Apache Trafodion include:

 * Full-functioned ANSI SQL language support
 * JDBC/ODBC connectivity for Linux/Windows clients
 * Distributed ACID transaction protection across multiple statements,
 tables and rows
 * Performance improvements for OLTP workloads with compile-time and
 run-time optimizations
 * Support for large data sets using a parallel-aware query optimizer
 * ANSI SQL security and data integrity constraints including referential
 integrity

 Hewlett-Packard Company submits this proposal to donate its Apache
 License, Version 2.0 open source project known as Trafodion, its source
 code, documentation, and web site content to the Apache Software Foundation
 in order to build an open source community

 Background

 Trafodion is an open source project sponsored by HP, incubated at HP Labs
 and HP-IT, to develop an enterprise-class SQL-on-Hadoop solution targeting
 big data transactional or operational workloads. HP publically announced
 the open source project and uploaded the source code to GitHub in June 2014.

 The SQL compiler, optimizer and executor components of Trafodion have a
 rich heritage. Under development since 1993, they were released as
 commercial closed source software in various flavors such as HP NonStop
 SQL/MX and HP Neoview. NonStop SQL/MX was designed for online transaction
 processing on HP’s NonStop (formerly Tandem) fault-tolerant servers and is
 known for its high availability, scalability, and performance. Hundreds of
 companies and thousands of servers are running mission-critical
 applications today on NonStop SQL/MX. In addition, much of these components
 today are running internal to HP as the core of its Enterprise Data
 Warehouse (EDW), managing over a PB of data.

 Starting in 2013, the software was modified to run on HBase and a new
 distributed transaction manager was written to run as an HBase co-processor.

 Unlike most NOSQL and other SQL-on-Hadoop open source projects, Trafodion
 provides comprehensive ANSI SQL language support including full-functioned
 data definition (DDL), data manipulation (DML), transaction control (TCL)
 and database utility support.

 Trafodion provides comprehensive and standard SQL data manipulation
 support including SELECT, INSERT, UPDATE, DELETE, and UPSERT/MERGE syntax
 with language options including join variants, unions, where predicates,
 aggregations (group by and having), sort ordering, sampling, correlated and
 nested sub-queries, cursors, and many SQL functions.

 Utilities are provided for updating table statistics used by the optimizer
 for costing (i.e. selectivity/cardinality estimates) plan alternatives, for
 displaying the chosen SQL execution plan, plan shaping, backup and
 restoring the database, data loading and unloading, and a command line
 utility for interfacing with the database engine.

 Explicit control statements are provided to allow applications to define
 transaction boundaries and to abort transactions when warranted, including
 BEGIN WORK, COMMIT WORK

Re: [DISCUSS] Trafodion Incubation Proposal

[Stack]

On Sun, May 10, 2015 at 7:13 PM, Konstantin Boudnik c...@apache.org wrote:

 I think it'd be great to have SQL platform for Hadoop

 +1

 I am mentoring 4 projects at the moment, but if you need a 1/2 time mentor
 -
 count me in ;)

 Cos


We'll take you up on your kind offer if we can't get someone less loaded.

Thanks Cos,

St.Ack


 On Fri, May 08, 2015 at 02:59PM, Stack wrote:
  I would like to start up a discussion on Trafodion joining the ASF as an
  incubating project.
 
  Trafodion is a webscale SQL-on-Hadoop solution that enables transactional
  or operational workloads on Hadoop, .
 
  The proposal is available on the wiki here:
  https://wiki.apache.org/incubator/TrafodionProposal#preview
 
  The proposal text is also attached to the end of this email.
 
  Trafodion is a rich, storied SQL engine that has recently been ported to
  run on HBase and Hadoop. I think it would make for a fine addition to the
  Apache family of projects  It would be good to hear what others think.
 
  Thank you in advance for giving the proposal a read.
 
  Yours,
  St.Ack
 
 
  Trafodion Apache Incubator Proposal
 
  Abstract
 
  Trafodion is a webscale SQL-on-Hadoop solution enabling transactional or
  operational workloads on Hadoop.
 
  Proposal
 
  Apache Trafodion builds on the scalability, elasticity, and flexibility
 of
  Hadoop. Trafodion extends Hadoop to provide guaranteed transactional
  integrity, enabling new kinds of big data applications to run on Hadoop.
 Key
  features of Apache Trafodion include:
 
  * Full-functioned ANSI SQL language support
  * JDBC/ODBC connectivity for Linux/Windows clients
  * Distributed ACID transaction protection across multiple statements,
  tables and rows
  * Performance improvements for OLTP workloads with compile-time and
  run-time optimizations
  * Support for large data sets using a parallel-aware query optimizer
  * ANSI SQL security and data integrity constraints including referential
  integrity
 
  Hewlett-Packard Company submits this proposal to donate its Apache
 License,
  Version 2.0 open source project known as Trafodion, its source code,
  documentation, and web site content to the Apache Software Foundation in
  order to build an open source community
 
  Background
 
  Trafodion is an open source project sponsored by HP, incubated at HP Labs
  and HP-IT, to develop an enterprise-class SQL-on-Hadoop solution
 targeting
  big data transactional or operational workloads. HP publically announced
  the open source project and uploaded the source code to GitHub in June
 2014.
 
  The SQL compiler, optimizer and executor components of Trafodion have a
  rich heritage. Under development since 1993, they were released as
  commercial closed source software in various flavors such as HP NonStop
  SQL/MX and HP Neoview. NonStop SQL/MX was designed for online transaction
  processing on HP’s NonStop (formerly Tandem) fault-tolerant servers and
 is
  known for its high availability, scalability, and performance. Hundreds
 of
  companies and thousands of servers are running mission-critical
  applications today on NonStop SQL/MX. In addition, much of these
 components
  today are running internal to HP as the core of its Enterprise Data
  Warehouse (EDW), managing over a PB of data.
 
  Starting in 2013, the software was modified to run on HBase and a new
  distributed transaction manager was written to run as an HBase
 co-processor.
 
  Unlike most NOSQL and other SQL-on-Hadoop open source projects, Trafodion
  provides comprehensive ANSI SQL language support including
 full-functioned
  data definition (DDL), data manipulation (DML), transaction control (TCL)
  and database utility support.
 
  Trafodion provides comprehensive and standard SQL data manipulation
 support
  including SELECT, INSERT, UPDATE, DELETE, and UPSERT/MERGE syntax with
  language options including join variants, unions, where predicates,
  aggregations (group by and having), sort ordering, sampling, correlated
 and
  nested sub-queries, cursors, and many SQL functions.
 
  Utilities are provided for updating table statistics used by the
 optimizer
  for costing (i.e. selectivity/cardinality estimates) plan alternatives,
 for
  displaying the chosen SQL execution plan, plan shaping, backup and
  restoring the database, data loading and unloading, and a command line
  utility for interfacing with the database engine.
 
  Explicit control statements are provided to allow applications to define
  transaction boundaries and to abort transactions when warranted,
 including
  BEGIN WORK, COMMIT WORK, ROLLBACK WORK and SET TRANSACTION.
 
  Trafodion supports ANSI’s grant/revoke semantics to define user and role
  privileges in terms of managing and accessing the database objects.
 
  Rationale
 
  The name “Trafodion” (the Welsh word for transactions, pronounced
  “Tra-vod-eee-on”) was chosen specifically to emphasize the
 differentiation
  that Trafodion provides in closing a critical gap

Re: [VOTE] Release Apache htrace-3.2.0-incubating

[Stack]

On Sun, May 10, 2015 at 7:30 PM, Justin Mclean jus...@classsoftware.com
wrote:

 What do other incubator members think?


I think you are a good man for trying the candidate. Thanks Justin.

The compile fail is pretty ugly. Your suggestion of a banner warning on the
release email sounds like a good idea to me (otherwise, we sink the release
candidate).

Thanks,

St.Ack

Re: [VOTE] Release Apache htrace-3.2.0-incubating

[Stack]

On Sat, May 9, 2015 at 6:54 PM, Abraham Elmahrek a...@apache.org wrote:

 Apache HTrace (incubating), after 2 release candidates, has voted to
 release the below referenced Apache HTrace 3.2.0-incubating release
 candidate.

 Dear IPMC, please vote on our second release candidate as an Apache
 Incubator project.

 Here is the vote thread we ran on our dev list (Six binding +1 votes and no
 -1 votes) with
 a subject: [VOTE] HTrace 3.2.0 - Release Candidate 2, second release
 candidate

 *

 http://mail-archives.apache.org/mod_mbox/incubator-htrace-dev/201505.mbox/%3CCAOvM-ciKd82bt3ze7oZD9FnNUcss8T%2BufwwgEndrhpnnOdgMNA%40mail.gmail.com%3E
 

 http://mail-archives.apache.org/mod_mbox/incubator-htrace-dev/201505.mbox/%3CCAOvM-ciKd82bt3ze7oZD9FnNUcss8T%2BufwwgEndrhpnnOdgMNA%40mail.gmail.com%3E
 *

 The source tarball, hashes, and signing are here:

   http://people.apache.org/~abe/htrace/releases/3.2.0/rc1/

 (Over in htrace our RC number was zero based so RC1 == second RC)

 Related maven artifacts are posted here:

https://repository.apache.org/content/repositories/orgapachehtrace-1016

 The tag for the RC is here:

 https://git-wip-us.apache.org/repos/asf?p=incubator-htrace.git;a=tag;h=44fa6e0cd7456b5725b8557161f68b851fdf75d8

 The KEYS file with the key used signing is available here:

 *https://dist.apache.org/repos/dist/release/incubator/htrace/KEYS
 https://dist.apache.org/repos/dist/release/incubator/htrace/KEYS*


 75 issues were closed/resolved for this release:


 https://issues.apache.org/jira/issues/?jql=project%20%3D%20HTRACE%20AND%20status%20%3D%20resolved%20AND%20fixVersion%20%3D%203.2.0%20ORDER%20BY%20issuetype%20DESC


 The vote will be open for 96 hours.

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


 Thanks,
 Abe


Here is my vote carried over from htrace list VOTE:

+1

Downloaded. Verified signature and keys.
Ran apache rat to look for errant licenses.
Was able to build a new tarball from src (all unit tests pass)

St.Ack

[DISCUSS] Trafodion Incubation Proposal

[Stack]

capabilities, such as Apache Hive, Apache Drill, and Apache Phoenix. These
are more focused on reporting and analytics across data structures
supported on HDFS. In comparison to all of these technologies Trafodion
provides a very complete implementation of ANSI SQL, one of the most
sophisticated optimizers for such workloads, a completely parallel data
flow architecture that does not materialize intermediate results unless
necessary, full ACID transactional support, ANSI GRANT/REVOKE security, and
other capabilities that would take decades to build in these products. On
the other hand currently Trafodion is just focused on HBase and querying
Hive, whereas Hive and Drill provide access to other data formats in HDFS.

An Excessive Fascination with the Apache Brand

We understand the reputation and value of the Apache brand, and no doubt
believe that it will help us attract contributors and users. Our primary
goal is to follow a proven, open source development and community building
model that will make Trafodion successful and enable better collaboration
with other Apache projects in the Hadoop ecosystem. We also understand the
rules and guidelines about the use of the Apache brand and intend to follow
them.

Documentation

Documentation and technical details on Trafodion can be found at:
http://www.trafodion.org/

Initial Source

The source is available today in a public github repository:
https://github.com/trafodion/trafodion.

Source and Intellectual Property Submission Plan

The source code has already been released under the Apache License, Version
2. The manuals have been released in Adobe PDF format. As part of the
submission process, the source for the manuals will be converted from a
proprietary DocBook XML format to AsciiDoc.

External Dependencies

Two dependencies do not have Apache compatible licenses and will be
addressed as we enter incubation. One dependency is log4cpp, which is
licensed under the LGPL. A compatible alternative might be Apache incubator
project log4cxx. The other dependency is unixodbc, which is used as the
ODBC driver manager. We will look into how Apache Hive manages being able
to use this incompatible software and do similar. All other dependencies
have Apache compatible licenses, including Apache 2.0, MIT/X11, MIT, and
BSD.

Cryptography

Trafodion does not contain any cryptographic code. It does call
cryptographic libraries: OpenSSL for C++ code and Java Cryptography
Extension (JCE) for Java code.

Required Resources

Mailing Lists

priv...@trafodion.incubator.apache.org
d...@trafodion.incubator.apache.org comm...@trafodion.incubator.apache.org

Git Repository

https://git-wip-us.apache.org/repos/afs/incubator-trafodion.git

Issue Tracking

JIRA: JIRA Trafodion (Trafodion)


Initial Committers and Affiliation

Dave Birdsall, Hewlett-Packard Company, Dave.BirdsallAThpDOTcom
Matt Brown, Hewlett-Packard Company, mattbrownAThpDOTcom
Tharak Capirala, Hewlett-Packard Company, Tharak.CapiralaAThpDOTcom
Alice Chen, Hewlett-Packard Company, Alice.ChenAThpDOTcom
John DeRoo, Hewlett-Packard Company, John.DerooAThpDOTcom
Roberta Marton, Hewlett-Packard Company, Roberta.MartonAThpDOTcom
Amanda Moran, Hewlett-Packard Company, Amanda.Kay.MoranAThpDOTcom
Suresh Subbiah, Hewlett-Packard Company, Suresh.SubbiahAThpDOTcom
Sandyha Sundaresan, Hewlett-Packard Company,
Sandhya.SundaresanAThpDOTcom

Sponsors

Champion

Michael Stack, StackATapacheDOTorg

Nominated Mentors

Michael Stack, StackATapacheDOTorg
Roman Shaposhnik, rshaposhnikATpivotalDOTio

We are seeking additional mentors.

Sponsoring Entity

Apache Incubator PMC

HBaseCon2015 CfP's closes February 6th

[Stack]

If you have any hbasey topics you'd think the community would like to hear
about, send in an abstract. We'd love to from you. Register at
https://easychair.org/account/signin.cgi?key=19733317.f4v8ARL3qsrpDXfI

Thanks all,
St.Ack

Re: [VOTE] Release Apache htrace-3.1.0-incubating

[Stack]

WIth 3+1 (binding), a dodgy binding +1 vote (mine), and a non-binding +1,
the vote passes. Thank you to all who voted. Let me push out our first
release out of incubator.

Thanks,
St.Ack

On Tue, Jan 20, 2015 at 12:14 PM, Billie Rinaldi bil...@apache.org wrote:

 +1 binding

 On Sat, Jan 17, 2015 at 10:36 PM, Stack st...@duboce.net wrote:
  Apache HTrace (incubating), after ten release candidates, has voted to
  release the below referenced Apache HTrace 3.1.0-incubating release
  candidate.
 
  Dear IPMC, please vote on our first release candidate as an Apache
  Incubator project.
 
  Here is the vote thread we ran on our dev list (Six binding +1 votes and
 no
  dissent) with
  a subject: [VOTE] htrace-3.1.0, the this is it for sure!, tenth
 release
  candidate
 
  *
 

 http://mail-archives.apache.org/mod_mbox/incubator-htrace-dev/201501.mbox/%3CCADcMMgF_agDCzcwsxpdGsJOzCQ1ebA5z7hsM_-oFbneAVzh4dg%40mail.gmail.com%3E
  
 

 http://mail-archives.apache.org/mod_mbox/incubator-htrace-dev/201501.mbox/%3CCADcMMgF_agDCzcwsxpdGsJOzCQ1ebA5z7hsM_-oFbneAVzh4dg%40mail.gmail.com%3E
  *
 
  The source tarball, hashes, and signing are here:
 
http://people.apache.org/~stack/htrace-3.1.0-incubatingRC9/
 
  (Over in htrace our RC number was zero based so RC9 == tenth RC)
 
  Related maven artifacts are posted here:
 
 
 https://repository.apache.org/content/repositories/orgapachehtrace-1014
 
  The tag for the RC is here:
 
 

 https://git-wip-us.apache.org/repos/asf?p=incubator-htrace.git;a=commit;h=0cabe569bc05a58c7a319a460eed5e50e136bae7
 
  The KEYS file with the key used signing is available here:
 
  *https://dist.apache.org/repos/dist/release/incubator/htrace/KEYS
  https://dist.apache.org/repos/dist/release/incubator/htrace/KEYS*
 
 
  44 issues were closed/resolved for this release:
 
 
 

 https://issues.apache.org/jira/issues/?jql=project%20%3D%20HTRACE%20AND%20status%20%3D%20resolved%20AND%20fixVersion%20%3D%203.1.0%20ORDER%20BY%20issuetype%20DESC
 
 
  The vote will be open for 72 hours.
 
  [ ] +1 Release this package as Apache HTrace 3.1.0-incubating
  [ ] +0 no opinion
  [ ] -1 Do not release this package because ...
 
 
  Thanks,
  St.Ack
 

Re: [VOTE] Release Apache htrace-3.1.0-incubating

[Stack]

+1 (binding -- though it may not be allowed that I vote on an RC I posted).

From the htrace mailing list [1]:

+1

Verified md5 and signature.
Ran rat and all unit tests.
Was able to assemble a src tarball from downloaded tarball.

St.Ack


1. 
http://mail-archives.apache.org/mod_mbox/incubator-htrace-dev/201501.mbox/%3ccadcmmgfl6orjlvcqr2taf7hr+s44bpw9pcavslee+m2g518...@mail.gmail.com%3E




On Sat, Jan 17, 2015 at 7:36 PM, Stack st...@duboce.net wrote:

 Apache HTrace (incubating), after ten release candidates, has voted to
 release the below referenced Apache HTrace 3.1.0-incubating release
 candidate.

 Dear IPMC, please vote on our first release candidate as an Apache
 Incubator project.

 Here is the vote thread we ran on our dev list (Six binding +1 votes and
 no dissent) with
 a subject: [VOTE] htrace-3.1.0, the this is it for sure!, tenth
 release candidate

 *http://mail-archives.apache.org/mod_mbox/incubator-htrace-dev/201501.mbox/%3CCADcMMgF_agDCzcwsxpdGsJOzCQ1ebA5z7hsM_-oFbneAVzh4dg%40mail.gmail.com%3E
 http://mail-archives.apache.org/mod_mbox/incubator-htrace-dev/201501.mbox/%3CCADcMMgF_agDCzcwsxpdGsJOzCQ1ebA5z7hsM_-oFbneAVzh4dg%40mail.gmail.com%3E*

 The source tarball, hashes, and signing are here:

   http://people.apache.org/~stack/htrace-3.1.0-incubatingRC9/

 (Over in htrace our RC number was zero based so RC9 == tenth RC)

 Related maven artifacts are posted here:

https://repository.apache.org/content/repositories/orgapachehtrace-1014

 The tag for the RC is here:
 https://git-wip-us.apache.org/repos/asf?p=incubator-htrace.git;a=commit;h=0cabe569bc05a58c7a319a460eed5e50e136bae7

 The KEYS file with the key used signing is available here:

 *https://dist.apache.org/repos/dist/release/incubator/htrace/KEYS
 https://dist.apache.org/repos/dist/release/incubator/htrace/KEYS*


 44 issues were closed/resolved for this release:

 https://issues.apache.org/jira/issues/?jql=project%20%3D%20HTRACE%20AND%20status%20%3D%20resolved%20AND%20fixVersion%20%3D%203.1.0%20ORDER%20BY%20issuetype%20DESC


 The vote will be open for 72 hours.

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


 Thanks,
 St.Ack

[VOTE] Release Apache htrace-3.1.0-incubating

[Stack]

Apache HTrace (incubating), after ten release candidates, has voted to
release the below referenced Apache HTrace 3.1.0-incubating release
candidate.

Dear IPMC, please vote on our first release candidate as an Apache
Incubator project.

Here is the vote thread we ran on our dev list (Six binding +1 votes and no
dissent) with
a subject: [VOTE] htrace-3.1.0, the this is it for sure!, tenth release
candidate

*http://mail-archives.apache.org/mod_mbox/incubator-htrace-dev/201501.mbox/%3CCADcMMgF_agDCzcwsxpdGsJOzCQ1ebA5z7hsM_-oFbneAVzh4dg%40mail.gmail.com%3E
http://mail-archives.apache.org/mod_mbox/incubator-htrace-dev/201501.mbox/%3CCADcMMgF_agDCzcwsxpdGsJOzCQ1ebA5z7hsM_-oFbneAVzh4dg%40mail.gmail.com%3E*

The source tarball, hashes, and signing are here:

  http://people.apache.org/~stack/htrace-3.1.0-incubatingRC9/

(Over in htrace our RC number was zero based so RC9 == tenth RC)

Related maven artifacts are posted here:

   https://repository.apache.org/content/repositories/orgapachehtrace-1014

The tag for the RC is here:
https://git-wip-us.apache.org/repos/asf?p=incubator-htrace.git;a=commit;h=0cabe569bc05a58c7a319a460eed5e50e136bae7

The KEYS file with the key used signing is available here:

*https://dist.apache.org/repos/dist/release/incubator/htrace/KEYS
https://dist.apache.org/repos/dist/release/incubator/htrace/KEYS*


44 issues were closed/resolved for this release:

https://issues.apache.org/jira/issues/?jql=project%20%3D%20HTRACE%20AND%20status%20%3D%20resolved%20AND%20fixVersion%20%3D%203.1.0%20ORDER%20BY%20issuetype%20DESC


The vote will be open for 72 hours.

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


Thanks,
St.Ack

Re: [VOTE] Release Apache Parquet Format (incubating) 2.2.0 RC2

[Stack]

+1 (binding)

Checked signature, md5 and that files were properly licensed.  LGTM.

St.Ack

On Mon, Nov 10, 2014 at 2:35 PM, Ryan Blue b...@apache.org wrote:

 Hi everyone,

 I'd like to propose a vote to release parquet-format-2.2.0-rc2 as the
 official Parquet Format 2.2.0 release.

 This release candidate has passed a podling vote, which can be found here:

 https://mail-archives.apache.org/mod_mbox/incubator-
 parquet-dev/201411.mbox/%3C54613B48.6060602%40apache.org%3E

 The release candidate, signature, and checksums are available at:
   https://dist.apache.org/repos/dist/dev/incubator/parquet/2.2.0-rc2/

 The branch used to create the release candidate is:

 https://git-wip-us.apache.org/repos/asf?p=incubator-parquet-
 format.git;hb=release-2.2.0-rc2

 KEYS to validate the signature are available at:
   https://dist.apache.org/repos/dist/dev/incubator/parquet/KEYS

 Please download, verify, and test.

 [ ] +1: Release this tag as parquet-format-2.2.0
 [ ] +0:
 [ ] -1: This release is not ready because . . .


 == More details ==

 This will be the first release from the Parquet project. We are releasing
 parquet-format first because the other projects (parquet-mr and
 parquet-cpp) depend on it.

 This release uses the pre-Apache maven coordinate
 com.twitter:parquet-format and parquet.* package names. To make the
 transition to org.apache naming as smooth as possible for downstream
 projects, we are planning to release a com.twitter artifact immediately
 followed by an org.apache artifact. These artifacts will be identical
 except for naming changes:

 * com.twitter:parquet-format = org.apache.parquet:parquet-format
 * package parquet.* = package org.apache.parquet.*

 There are three major changes included in this release:
 * PARQUET-119: Add encoding stats to ColumnMetaData
 * PARQUET-79: Streaming thrift API
 * PARQUET-12: New logical types


 rb


 --
 Ryan Blue

 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept HTrace into the Apache Incubator

[Stack]

+1

On Wed, Nov 5, 2014 at 11:16 AM, Roman Shaposhnik r...@apache.org wrote:

 Following the discussion earlier in the thread:
http://s.apache.org/Dk7

 I would like to call a VOTE for accepting HTrace
 as a new incubator project.

 The proposal is available at:

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

 Vote is open until at least Sunday, 9th November 2014, 23:59:00 UTC

  [ X] +1 accept HTrace in the Incubator
  [ ] ±0
  [ ] -1 because...

 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] [PROPOSAL] HTrace for Apache Incubator

[Stack]

 a Scala dependency,
   at a minimum, you need an alternate means of generating traces.
   HTrace provides this facility for Java as well as bridging tools
   to feed traces to Zipkin for query and display.
  
   The projects complement each other.
  
   === A Excessive Fascination with the Apache Brand ===
   While we intend to leverage the Apache ‘branding’ when talking to other
   projects as testament of our project’s ‘neutrality’, we have no plans
   for making use of Apache brand in press releases nor posting billboards
   advertising acceptance of HTrace into Apache Incubator.
  
  
   == Documentation ==
   See [[http://htrace.org|htrace.org]] for the current state of the
 HTrace
   project and documentation.
  
   How to enable tracing in
   [[http://hbase.apache.org/book/tracing.html|HBase using HTrace]]
   Elliott Clark on
   [[
  http://files.meetup.com/1350427/HBase%20Meetup%20-%20Zipkin.pptx|tracing
   in HBase]]
  
   == Initial Source ==
   Jonathan Leavitt and Todd Lipcon built the first versions of HTrace in
  the
   summer of 2012.  Jonathan was Todd’s summer intern at Cloudera.
  
  
   == Source and Intellectual Property Submission Plan ==
   We know of no legal encumberments in the way of transfer of source to
   Apache.
  
   == External Dependencies ==
   HTrace includes third party libs. These include guava, jetty, junit,
   protobuf,
   hbase, and thrift.  All dependencies are Apache licensed or licenses
 that
   are
   palatable: e.g. junit is EPL (Eclipse Public License v1.0) and
   ProtoBufs are BSD licensed.
  
   Cryptography
   N/A
  
   == Required Resources ==
  
   === Mailing lists ===
 * priv...@htrace.incubator.apache.org (moderated subscriptions)
 * comm...@htrace.incubator.apache.org
 * d...@htrace.incubator.apache.org
 * iss...@htrace.incubator.apache.org
 * u...@htrace.incubator.apache.org
  
   === Git Repository ===
   https://git-wip-us.apache.org/repos/asf/incubator-htrace.git
  
   === Issue Tracking ===
   JIRA HTrace (HTRACE)
  
   === Other Resources ===
   Means of setting up regular builds for htrace on builds.apache.org
  
   == Initial Committers ==
 * Colin McCabe (cmcc...@apache.org)
 * Elliott Clark (ecl...@apache.org)
 * Jonathan Leavitt (jon.s.leav...@gmail.com) -- CLA being submitted
 * Masatake Iwasaki (iwasak...@gmail.com) -- CLA being submitted
 * Michael Stack (st...@apache.org)
 * Nick Dimiduk (ndimi...@apache.org)
 * Todd Lipcon (t...@apache.org)
  
  
   == Affiliations ==
 * Colin McCabe - Cloudera
 * Elliott Clark - Facebook
 * Jonathan Leavitt - Google
 * Masatake Iwasaki - NTTData
 * Michael Stack - Cloudera
 * Nick Dimiduk - Hortonworks
 * Todd Lipcon - Cloudera
  
   == Sponsors ==
  
   === Champion ===
   Roman Shaposhnik
  
   === Nominated Mentors ===
 * Michael Stack - Apache Member
 * Todd Lipcon - Apache Member
  
   We will be soliciting more mentors as part of the proposal process.
  
   === Sponsoring Entity ===
   We would like to propose Apache incubator to sponsor this project.
  
   -
   To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
   For additional commands, e-mail: general-h...@incubator.apache.org
  
  
 
 
  --
  Best regards,
 
 - Andy
 
  Problems worthy of attack prove their worth by hitting back. - Piet Hein
  (via Tom White)
 

 --
 _
 The information contained in this communication is intended solely for the
 use of the individual or entity to whom it is addressed and others
 authorized to receive it. It may contain confidential or legally privileged
 information. If you are not the intended recipient you are hereby notified
 that any disclosure, copying, distribution or taking any action in reliance
 on the contents of this information is strictly prohibited and may be
 unlawful. If you have received this communication in error, please notify
 us immediately by responding to this email and then delete it from your
 system. The firm is neither liable for the proper and complete transmission
 of the information contained in this communication nor for any delay in its
 receipt.

Re: [DISCUSS] [PROPOSAL] HTrace for Apache Incubator

[Stack]

On Mon, Nov 3, 2014 at 8:01 AM, Branko Čibej br...@apache.org wrote:

 On 03.11.2014 16:49, Stack wrote:
  On Sun, Nov 2, 2014 at 6:19 PM, Naresh Agarwal 
 naresh.agar...@inmobi.com
  wrote:
 
  Just curious if HTrace is aimed only for Hadoop infrastructure/Hadoop
 based
  applications or it can be used in any Java based systems?
 
 
  HTrace's provenance is Hadoop but the only hadoop 'taint' in HTrace is
 the
  leading 'H' in its name; it should be fit for any java distributed
 systems.
 
  Lets make this more plain in the proposal.

 Would it hurt to remove the H from the project name, then?

 (I won't propose replacing it with D, that would be really confusing.)

 -- Brane

 P.S.: Ooh ... Distributed Tracing - Distress, which happens to be
 what an admin feels when her distributed app goes wonkers ...


HTrace is 'fairly' generic and the github project is what comes up when you
search. That said, I think your suggestion pretty great, funny. Its
probably a bad name for a software project though? (Distrace?)

St.Ack

Re: [DISCUSS] [PROPOSAL] HTrace for Apache Incubator

[Stack]

On Mon, Nov 3, 2014 at 12:04 PM, Jean-Louis MONTEIRO jeano...@gmail.com
wrote:

 BTW, wondering how to get the Apache Sirona community involved or if there
 is a possible common road where the 2 projects could join.


How do you see the projects relating?  How would the recording and viewing
of traces in Sirona look?  Do you foresee a zipkin like viewer in Sirona?
Thanks,
St.Ack

Re: [DISCUSS] [PROPOSAL] HTrace for Apache Incubator

[Stack]

On Mon, Nov 3, 2014 at 2:15 PM, Romain Manni-Bucau rmannibu...@gmail.com
wrote:

 Le 3 nov. 2014 22:06, Stack st...@duboce.net a écrit :
 
  On Mon, Nov 3, 2014 at 12:04 PM, Jean-Louis MONTEIRO jeano...@gmail.com
 
  wrote:
 
   BTW, wondering how to get the Apache Sirona community involved or if
 there
   is a possible common road where the 2 projects could join.
  
  
  How do you see the projects relating?  How would the recording and
 viewing
  of traces in Sirona look?  Do you foresee a zipkin like viewer in Sirona?

 We just started but we have agents to get data on nodes then we push in a
 store (cassandra mainly today). Gui is not yet complete for tracing part.


Ok. When comes time, would be great hooking up Apache Sirona as a Trace
Sink (HTrace has a few Sink implemenations as is: zipkin, files, hbase).
Thanks,
St.Ack

Re: [VOTE] Accept Ignite into the Apache Incubator

[Stack]

+1 from me (mentor, binding).
St.Ack

On Sat, Sep 27, 2014 at 5:58 PM, Konstantin Boudnik c...@apache.org wrote:

 I would like to call a vote for accepting Apache Ignite for Apache
 Incubator.
 The full proposal is available below. We ask the IPMC to sponsor it, with
 cos
 as Champion, and stack, rvs, cos, hsaputra and brane volunteering to be
 Mentors.

 Please cast your vote:

 [ ] +1, bring Iginite into Incubator
 [ ] +0, I don't care either way,
 [ ] -1, do not bring Iginite into Incubator, because...

 This vote will be open for 72 hours and only votes from the Incubator
 PMC are binding.

 http://wiki.apache.org/incubator/IgniteProposal

 Proposal text from the wiki:
 ## page was renamed from SilkProposal
 = Ignite Apache Incubator Proposal =
 == Abstract ==
 Apache Ignite will be a unified In-Memory Data Fabric providing
 high-performance, distributed in-memory data management software layer
 between
 various data sources and user applications.

 == Proposal ==
 Apache Ignite is written mostly in Java and Scala with small amount of C++
 code
 and will initially combine the following technologies under one unified
 umbrella:

  * In-Memory Data Grid
  * In-Memory Compute Grid
  * In-Memory Streaming Processing

 This unified in-memory fabric will provide high-performance, distributed
 in-memory software layer that sits in between various data sources and user
 applica tions. Data sources can include SQL RDBMS, NoSQL, or HDFS.
 Applications
 APIs will be available for Java (and Java-based scripting languages),
 Scala,
 C++ and .NET (C#).

 GridGain Systems, Inc. submits this proposal to donate its Apache
 2.0-licensed
 open source project generally known as “GridGain In-Memory Computing
 Platform”,
 its source code, documentation, and websites to the Apache Software
 Foundation
 (“ASF”) with the goal of extending the vibrant open source community around
 this technology ultimately governed by “Apache Way”. Proposed Naming

 We have been advised by the ASF mentors that the name “Ignite” may not be
 ideal
 because the name may be too generic and may not pass ASF legal check. Here
 are
 the alternatives that we have come up with and any of those will be
 acceptable
 for the project pending the ASF legal green light:

  * Apache Silk (preferable name)
  * Apache Sylk
  * Apache Memstor
  * Apache Ignite

 == Background  Rationale ==
 In-Memory Data Fabric is a natural and evolutionary consolidation of
 various
 “in-memory technologies” from the last decade. From simple local caching
 (JSR-107), to distributed caching, to data grids and databases, to
 streaming
 and plug-n-play acceleration - the in-memory space has grown quite
 dramatically.

 With rapid advances in NVRAM and significant price reduction of traditional
 DRAM on one hand, and growing sophistication and demand for faster data
 processing on another - many users of these silo-ed technologies and
 products
 started to look for a “strategic approach” to in-memory - an in-memory data
 fabric - that would provide suitable APIs for different types of payloads:
 from
 data caching, to data grids, to in-memory SQL data stores, to HPC, to
 streaming
 processing.

 With expensive and proprietary in-memory computing products from companies
 like
 Oracle, SAP, Microsoft, and IBM -  the developers worldwide need an
 unhindered
 access to advanced open source in-memory software technology, the
 technology
 they can trust to develop with and deploy for critical applications.
 Current
 Status

 Apache Ignite will be based on the technology that is currently developed
 by
 GridGain Systems and available under Apache 2.0 license
 (http://www.gridgain.org). The software has been in development since
 2007 and
 in production since 2009. It is currently used by over 500 production
 deployments with over 1,000,000 downloads to date, and with over 20,000,000
 GridGain nodes started in the last 5 years.

 == Comparative analysis to relevant projects ==
 === Ignite vs. Spark ===
 Apache Spark is a data-analytic and ML centric system that ingest data from
 HDFS or another distributed file system and performs in-memory processing
 of
 this data. Ignite is an In-Memory Data Fabric that is data source agnostic
 and
 provides both Hadoop-like computation engine (MapReduce) as well as many
 other
 computing paradigms like MPP, MPI, Streaming processing. Ignite also
 includes
 first-class level support for cluster management and operations,
 cluster-aware
 messaging and zero-deployment technologies. Ignite also provides support
 for
 full ACID transactions spanning memory and optional data sources.

 Ignite is a broader in-memory system that is less focused on Hadoop. Apache
 Spark is more inclined towards analytics and ML, and focused on MR-specific
 payloads.

 === Ignite vs. Storm, Samza ===
 Apache Storm is streaming processing framework. Apache Samza is a
 distributed
 stream processing engine. Ignite is a multi-purpose In-Memory Data Fabric
 that
 also includes

Re: [VOTE] Graduation of Apache Phoenix from the Incubator

[Stack]

+1


On Wed, Apr 30, 2014 at 10:44 PM, James Taylor jamestay...@apache.orgwrote:

 Hi everyone,

 The Apache Phoenix podling has has discussed and voted to graduate from the
 incubator with 22 +1 votes, 5 of which were IPMC vote [1]. We've made three
 releases, increased our contributor and committer list [2], and have an
 active, thriving community.

 Please VOTE below on the graduation of Apache Phoenix from the
 Incubator. The graduation resolution is pasted below.

 The VOTE will be open for at least 72 hours:

 [ ] +1 Graduate Apache Phoenix from the Incubator.
 [ ] +0 Don't care.
 [ ] -1 Don't graduate Apache Phoenix from the Incubator because

 [1]

 http://mail-archives.apache.org/mod_mbox/incubator-phoenix-dev/201405.mbox/%3CCAAF1JdgX_0nc7hgSrx9v1wJGKG0C3LBjO2ceZpGYsW1Z%3DsSaYw%40mail.gmail.com%3E
 [2] https://incubator.apache.org/projects/phoenix.html


 X. Establish the Apache Phoenix Project

WHEREAS, the Board of Directors deems it to be in the best
interests of the Foundation and consistent with the
Foundation's purpose to establish a Project Management
Committee charged with the creation and maintenance of
open-source software, for distribution at no charge to
the public, related to a SQL database for NoSQL data stores
such as Apache HBase.

NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the Apache Phoenix Project,
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further

RESOLVED, that the Apache Phoenix Project be and hereby is
responsible for the creation and maintenance of software
related to a SQL database for NoSQL data stores such as Apache
HBase; and be it further

RESOLVED, that the office of Vice President, Apache Phoenix be
and hereby is created, the person holding such office to
serve at the direction of the Board of Directors as the chair
of the Apache Phoenix Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache Phoenix Project; and be it further

RESOLVED, that the persons listed immediately below be and
hereby are appointed to serve as the initial members of the
Apache Phoenix Project:

  * Andrew Purtellapurt...@apache.org
  * Anoop Sam Johnanoopsamj...@apache.org
  * Devaraj Das   d...@apache.org
  * Eli Levineelilev...@apache.org
  * Enis Soztutar e...@apache.org
  * Gabriel Reid  gr...@apache.org
  * James R. Taylor   jamestay...@apache.org
  * Jeffrey Zhong jeffr...@apache.org
  * Jesse Yates   jya...@apache.org
  * Lars Hofhansl la...@apache.org
  * Maryann Xue   maryann...@apache.org
  * Michael Stack st...@apache.org
  * Mujtaba Chohanmujt...@apache.org
  * Nick Dimiduk  ndimi...@apache.org
  * Ramkrishna Vasudevan  ramkris...@apache.org
  * Simon Toens   sto...@apache.org
  * Steven Noels  stev...@apache.org

NOW, THEREFORE, BE IT FURTHER RESOLVED, that James R. Taylor
be appointed to the office of Vice President, Apache Phoenix, to
serve in accordance with and subject to the direction of the
Board of Directors and the Bylaws of the Foundation until
death, resignation, retirement, removal or disqualification,
or until a successor is appointed; and be it further

RESOLVED, that the initial Apache Phoenix PMC be and hereby is
tasked with the creation of a set of bylaws intended to
encourage open development and increased participation in the
Apache Phoenix Project; and be it further

RESOLVED, that the Apache Phoenix Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator Phoenix podling; and be it further

RESOLVED, that all responsibilities pertaining to the Apache
Incubator Phoenix podling encumbered upon the Apache Incubator
Project are hereafter discharged.

Re: [VOTE] Release of Apache Phoenix 4.0.0 incubating RC3

[Stack]

+1

(Promoting my phoenix dev list +1 here)

St.Ack


On Mon, Mar 31, 2014 at 10:47 PM, James Taylor jamestay...@apache.orgwrote:

 Hi everyone,
 This is a call for a vote on Apache Phoenix 4.0.0 incubating RC3. Phoenix
 is a SQL query engine for Apache HBase, a NoSQL data store. It is accessed
 as a JDBC driver and enables querying and managing HBase tables using SQL.
 This
 is the next major release of Phoenix compatible with the 0.98 branch of
 Apache HBase (0.98.1+) and will be our third release in the incubator. The
 release includes both a source-only release and a convenience binary
 release.

 The 4.0.0 release has feature parity with our pending 3.0.0 release. New
 features include:
 - Equi-joins through broadcast hash join
 - Shared tables over same physical HBase table
 - Read-only and updatable views
 - Multi-tenancy
 - JDBC ARRAY type
 - Sequence creation and usage

 The dev list thread for the passing vote (7 +1s with 2 IPMC votes) can be
 found at:

 http://mail-archives.apache.org/mod_mbox/incubator-phoenix-dev/201404.mbox/%3CCAAF1JdjJ_3%2B%2B2y3TYFNUDJSt9UVJngQjqg5dU6qnTUW%2BamhBag%40mail.gmail.com%3E

 The source tarball, including signatures, digests, etc can be found at:

 https://dist.apache.org/repos/dist/dev/incubator/phoenix/phoenix-4.0.0-incubating-rc3/src/

 The binary artifacts can be found at:

 https://dist.apache.org/repos/dist/dev/incubator/phoenix/phoenix-4.0.0-incubating-rc3/bin/

 Release artifacts are signed with the following key:
 https://people.apache.org/keys/committer/mujtaba.asc

 KEYS file available here:
 https://dist.apache.org/repos/dist/release/incubator/phoenix/KEYS

 The hash and tag to be voted on:

 https://git-wip-us.apache.org/repos/asf?p=incubator-phoenix.git;a=commit;h=4d90a49dd375da984a9db195d517ef26166745f0

 https://git-wip-us.apache.org/repos/asf?p=incubator-phoenix.git;a=tag;h=refs/tags/v4.0.0-incubating-rc3

 For information about the contents of this release see:

 https://git-wip-us.apache.org/repos/asf?p=incubator-phoenix.git;a=log;h=refs/tags/v4.0.0-incubating-rc3

 Vote will be open for at least 72 hours. Please vote:

 [ ] +1 approve
 [ ] +0 no opinion
 [ ] -1 disapprove (and reason why)

 Thanks,
 The Apache Phoenix Team

Re: [VOTE] Release of Apache Phoenix 2.2.3 incubating RC4

[Stack]

+1

Ran unit tests, checked hash, and checked for license compliance.

This is a repeat of my vote from over on the phoenix list.

St.Ack


On Fri, Mar 7, 2014 at 10:43 AM, James Taylor jamestay...@apache.orgwrote:

 Hello Everyone,
 This is a call for a vote on Apache Phoenix 2.2.3 incubating RC4. Phoenix
 is a SQL query engine for Apache HBase, a NoSQL data store. It is accessed
 as a JDBC driver and enables querying and managing HBase tables using SQL.
 This
 will be our first release in the incubator. The release includes both a
 source-only release and a convenience binary release. The last RC was sunk
 because of errors in the LICENSE and NOTICE files.

 The source tarball, including signatures, digests, etc can be found at:

 https://dist.apache.org/repos/dist/dev/incubator/phoenix/phoenix-2.2.3-incubating-rc4/src/

 The binary artifacts can be found at:

 https://dist.apache.org/repos/dist/dev/incubator/phoenix/phoenix-2.2.3-incubating-rc4/bin/

 The dev list thread for the passing vote (3 +1s with 1 IPMC vote) can be
 found at:

 http://mail-archives.apache.org/mod_mbox/incubator-phoenix-dev/201403.mbox/%3CCAAF1JdiOuwWisUGRFDMChB_bpiALz1HVrJDEtk9-pAdwDVLchA%40mail.gmail.com%3E

 Release artifacts are signed with the following key:
 https://people.apache.org/keys/committer/mujtaba.asc

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

 The tag to be voted upon is v2.2.3:

 https://git-wip-us.apache.org/repos/asf?p=incubator-phoenix.git;a=tag;h=refs/tags/v2.2.3

 For information about the contents of this release see:

 https://git-wip-us.apache.org/repos/asf?p=incubator-phoenix.git;a=log;h=refs/tags/v2.2.3

 Vote will be open for at least 72 hours. Please vote:

 [ ] +1 approve
 [ ] +0 no opinion
 [ ] -1 disapprove (and reason why)

 Thanks,
 James

[RESULT] [IP CLEARANCE] Apache Phoenix, a SQL query engine for Apache HBase

[Stack]

Just to wrap it up, the 72 hour window has more than passed, so I'm calling
this IP clearance complete.

Thanks,
St.Ack


On Thu, Feb 6, 2014 at 11:31 AM, Craig L Russell
craig.russ...@oracle.comwrote:

 lgtm.

 Craig

 On Feb 6, 2014, at 11:21 AM, Stack wrote:

  Please check this IP-Clearance form
 
  http://incubator.staging.apache.org/ip-clearance/phoenix.html
 
  It is for a software grant for Apache Phoenix from Salesforce.
 
  Salesforce were the original sponsors of the Phoenix project and
  have donated the code to ASF.
 
  Thanks,
  St.Ack

 Craig L Russell
 Architect, Oracle
 http://db.apache.org/jdo
 408 276-5638 mailto:craig.russ...@oracle.com
 P.S. A good JDO? O, Gasp!


 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org

[IP CLEARANCE] Apache Phoenix, a SQL query engine for Apache HBase

[Stack]

Please check this IP-Clearance form

http://incubator.staging.apache.org/ip-clearance/phoenix.html

It is for a software grant for Apache Phoenix from Salesforce.

Salesforce were the original sponsors of the Phoenix project and
have donated the code to ASF.

Thanks,
St.Ack

Re: Admin permissions for phoenix (incubating) up JIRA

[Stack]

Thanks Jake.  That works.
St.Ack


On Mon, Jan 20, 2014 at 11:58 AM, Jake Farrell jfarr...@apache.org wrote:

 Stack
 You are set and the project lead for Phoenix and can edit these settings
 and add people/permissions as necessary. If you need help with this please
 submit a ticket in the infra project and i'd be happy to help you with this

 Thanks
 -Jake



 On Mon, Jan 20, 2014 at 2:42 PM, Stack st...@duboce.net wrote:

  We'd like to assign issues but are missing perms.  May I (stack) and
 James
  Taylor (jamestaylor) be added as administrators?
 
  Or is this an INFRA request?
 
  Thanks,
  St.Ack
 

Admin permissions for phoenix (incubating) up JIRA

[Stack]

We'd like to assign issues but are missing perms.  May I (stack) and James
Taylor (jamestaylor) be added as administrators?

Or is this an INFRA request?

Thanks,
St.Ack

Re: January 2014 Incubator report timeline

[Stack]

Pardon the dumb question but how do I get the phoenix podling's first
report to show on this page: http://wiki.apache.org/incubator/January2014 ?

Thanks,
St.Ack


On Wed, Dec 25, 2013 at 5:22 PM, Roman Shaposhnik r...@apache.org wrote:

 January 2014 Incubator report timeline:

 http://wiki.apache.org/incubator/January2014

 Wed January 01 -- Podling reports due by end of day
 Sun January 05 -- Shepherd reviews due by end of day
 Sun January 05 -- Summary due by end of day
 Tue January 07 -- Mentor signoff due by end of day
 Wed January 08 -- Report submitted to Board
 Wed January 15 -- Board meeting

 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org

Re: January 2014 Incubator report timeline

[Stack]

On Tue, Jan 7, 2014 at 1:42 PM, Marvin Humphrey mar...@rectangular.comwrote:

 On Tue, Jan 7, 2014 at 11:38 AM, Stack st...@duboce.net wrote:
  Pardon the dumb question but how do I get the phoenix podling's first
  report to show on this page:
 http://wiki.apache.org/incubator/January2014 ?

 Glad to see Phoenix's first report!


Wait till you read it first! (smile).



 As an anti-spam measure, ASF wikis must whitelist contributors. See
 the top of http://wiki.apache.org/incubator/.

 Please let us know your wiki username (not Apache ID) and we will add
 you to the ContributorsGroup whitelist.



MichaelStack



 For future reference, please note that podling reports are due two
 weeks before the Board meeting and a week before the Incubator VP
 files the report.  If a podling report shows up one day before we
 file, there's not enough time to go through shepherding, etc.

 So far, we've just been accepting late reports and asking nicely for
 future punctuality, but at some point we may start rejecting them like
 the Board does.  Ostensibly the Board expects the IPMC to review all
 podling reports before we file the aggregate report; if we ever
 institute such a process, we'll almost certainly start rejecting late
 reports then.



Understood.  All my fault: i.e. the mentor. Thanks for taking our report
though late.

I'll add it soon my credentials are blessed.

Thanks Marvin,
St.Ack

Re: January 2014 Incubator report timeline

[Stack]

On Tue, Jan 7, 2014 at 2:14 PM, David Crossley cross...@apache.org wrote:

 Stack wrote:
  Marvin Humphrey wrote:
  
   As an anti-spam measure, ASF wikis must whitelist contributors. See
   the top of http://wiki.apache.org/incubator/.
  
   Please let us know your wiki username (not Apache ID) and we will add
   you to the ContributorsGroup whitelist.
 
  MichaelStack

 Done.


Thanks David.

I went ahead and added up the Phoenix report (I removed us from the
non-reporters list -- smile).  I did not know what to fill in for the
'signed-off by' list so left it blank.  Let me go ping our Shepherd for
this period; hopefully he is just as forgiving of our late submission.

Thanks for the help,
St.Ack

Re: January 2014 Incubator report timeline

[Stack]

On Tue, Jan 7, 2014 at 5:24 PM, Marvin Humphrey mar...@rectangular.comwrote:

 On Tue, Jan 7, 2014 at 3:49 PM, Stack st...@duboce.net wrote:

  I went ahead and added up the Phoenix report (I removed us from the
  non-reporters list -- smile).

 Great, thanks!

  I did not know what to fill in for the 'signed-off by' list so left it
  blank.

 It's a list of Mentors who have seen the report and approved it.  I took
 the
 liberty of filling in the checkboxes for Enis Sözutar and Devaraj Das
 because
 they both sent +1 emails to dev@phoenix.incubator.

  Let me go ping our Shepherd for this period; hopefully he is just as
  forgiving of our late submission.

 The main thing we need shepherds for is to signal the IPMC when all Mentors
 have gone missing and a podling is adrift.  The secondary function of
 providing outsider feedback can be helpful, but it's best not to add
 commentary late in the process because we want to give the podling the
 chance
 to respond if necessary.


Thank you for the explanations.
St.Ack

Re: [VOTE] Phoenix for incubator project

[Stack]

Pardon me Craig.  I messed up the closing of the vote.  I resent the vote
tally later w/ appropriate title:
http://mail-archives.apache.org/mod_mbox/incubator-general/201312.mbox/%3CCADcMMgHzeJJ7Vi-bSWGqb16j44cSEz9Svov%3D5L4LKctzBQ3_xw%40mail.gmail.com%3E

St.Ack


On Thu, Dec 12, 2013 at 11:09 AM, Craig L Russell
craig.russ...@oracle.comwrote:

 Hi St.Ack,

 I haven't seen that this vote has closed.

 Craig

 On Dec 5, 2013, at 1:43 PM, Stack wrote:

  Discussion of the Phoenix proposal has settled since its original
  posting on November 7th.  Feedback has been incorporated.
 
  Let us now move to a vote.
 
  Should Phoenix become an Apache incubator project?
 
  [] +1 Accept Phoenix into the Incubator
  [] +0 Don't care whether or which
  [] -1 Do not accept Phoenix into the Incubator because...
 
  The latest version of the proposal can be found here [1].  It is
  also posted below for your convenience.
 
  Let the vote run 72 hours.
 
  Thank you,
  St.Ack
 
  1. https://wiki.apache.org/incubator/PhoenixProposal
 
 
 
 
  Abstract
 
  Phoenix is an open source SQL query engine for Apache HBase, a NoSQL data
  store. It is accessed as a JDBC driver and enables querying and managing
  HBase tables using SQL.
 
  Proposal
 
  Phoenix is an open source SQL skin over HBase delivered as a
  client-embedded JDBC driver targeting low latency queries over HBase
 data.
  Phoenix takes your SQL query, compiles it into a series of HBase scans,
 and
  orchestrates the running of those scans to produce regular JDBC result
  sets. The table metadata is stored in an HBase table and versioned, such
  that snapshot queries over prior versions will automatically use the
  correct schema. Direct use of the HBase API, along with coprocessors and
  custom filters, results in performance on the order of milliseconds for
  small queries, or seconds for tens of millions of rows. Phoenix
 interfaces
  with both Pig and Map-reduce for the input and output of data.
 
  Background
 
  Phoenix initially started as an internal project at Salesforce.com to
  efficiently analyze big data stored in HBase. It was open sourced on
 Github
  about a year ago in Jan 2013. Over time Phoenix, together with HBase as
 the
  storage tier, has begun to evolve into a general SQL database with
 support
  for metadata management, secondary indexes, joins, query optimization,
 and
  multi-tenancy. This is expected to continue as Phoenix implements a
  cost-based query optimizer and potentially transaction support, and
  surfaces new HBase security features such as encryption and cell-level
  security. Phoenix's developer community has also grown to include
  additional companies such as Intel, who have contributed join support to
  Phoenix, as well as Hortonworks, who are in the process of porting
 Phoenix
  to the 0.96 release of HBase.
 
  Rationale
 
  As usage and the number of contributors to Phoenix has grown, we have
  sought for a long-term home for the project, and we believe the Apache
  foundation would be a great fit. Joining Apache would ensure that tried
 and
  true processes and procedures are in place for the growing number of
  organizations interested in contributing to Phoenix. Phoenix is also a
 good
  fit for the Apache foundation: Phoenix already interoperates with several
  existing Apache projects (HBase, Hadoop, Pig, BigTop). The Phoenix team
 is
  familiar with the Apache process and and believes in the Apache mission -
  the team already includes multiple Apache committers.
 
  Initial Goals
 
  The initial goals will be to move the existing codebase to Apache and
  integrate with the Apache development process. Once this is accomplished,
  we plan for incremental development and releases that follow the Apache
  guidelines.
 
  Current Status
 
  Phoenix has undergone two major and three minor releases (1.0, 1.1, 1.2,
  2.0, and 2.1) as well as many patch releases. Phoenix is being used in
  production by Salesforce.com as well as at other organizations. The
 Phoenix
  codebase is currently hosted at github.com, which will form the basis of
  the Apache git repository.
 
  Meritocracy
 
  The Phoenix project already operates on meritocratic principles. Phoenix
  has several developers from various organizations outside of
 Salesforce.com
  who have contributed major new features. While this process has remained
  mostly informal, as we do not have an official committer list, an
 implicit
  organization exists in which individuals who contribute major components
  act as maintainers for those modules. If accepted, the Phoenix project
  would include several of these participants as initial committers. We
 will
  work to identify all committers and PPMC members for the project and to
  operate under the ASF meritocratic principles.
 
  Community
 
  Acceptance into the Apache foundation would bolster the already strong
 user
  and developer community around Phoenix. That community includes many
  contributors from various

Re: [VOTE] Phoenix for incubator project

[Stack]

Let me vote +1 (binding) and now close the VOTE.

Here are the results (* means IPMC):

+1s:
Roman Shaposhnik(*)
James Taylor
Lars Hofhansl(*)
Henry Saputra(*)
Leif Hedstrom(*)
Anil Gupta
Ted Dunning(*)
Patrick Reilly
Andrew Purtell(*)
Ashish
Anoop John
Bruno Mahé
Ramkrishna S. Vasudevan
Jonathan Hsieh
Devaraj Das(*)
Sergio Fernández(*)
Alan D. Cabrera(*)
Misha Nasledov
Joris V.R.
Mujtaba Chohan
Johann Schleier-Smith
Nick Dimiduk
Eli Levine
Steven Noels(*)
Doug Meil
Enis Söztutar(*)
Olivier Lamy(*)
Supun Kamburugamuva
Imesh Gunaratne
Michael Stack(*)

+0s:
None

-1s:
None

With 30 +1s (13 binding) and no 0s or -1s, the vote passes.

Thanks all who voted.
St.Ack


On Thu, Dec 5, 2013 at 1:43 PM, Stack st...@duboce.net wrote:

 Discussion of the Phoenix proposal has settled since its original
 posting on November 7th.  Feedback has been incorporated.

 Let us now move to a vote.

 Should Phoenix become an Apache incubator project?

 [] +1 Accept Phoenix into the Incubator
 [] +0 Don't care whether or which
 [] -1 Do not accept Phoenix into the Incubator because...

 The latest version of the proposal can be found here [1].  It is
 also posted below for your convenience.

 Let the vote run 72 hours.

 Thank you,
 St.Ack

 1. https://wiki.apache.org/incubator/PhoenixProposal




 Abstract

 Phoenix is an open source SQL query engine for Apache HBase, a NoSQL data
 store. It is accessed as a JDBC driver and enables querying and managing
 HBase tables using SQL.

 Proposal

 Phoenix is an open source SQL skin over HBase delivered as a
 client-embedded JDBC driver targeting low latency queries over HBase data.
 Phoenix takes your SQL query, compiles it into a series of HBase scans, and
 orchestrates the running of those scans to produce regular JDBC result
 sets. The table metadata is stored in an HBase table and versioned, such
 that snapshot queries over prior versions will automatically use the
 correct schema. Direct use of the HBase API, along with coprocessors and
 custom filters, results in performance on the order of milliseconds for
 small queries, or seconds for tens of millions of rows. Phoenix interfaces
 with both Pig and Map-reduce for the input and output of data.

 Background

 Phoenix initially started as an internal project at Salesforce.com to
 efficiently analyze big data stored in HBase. It was open sourced on Github
 about a year ago in Jan 2013. Over time Phoenix, together with HBase as the
 storage tier, has begun to evolve into a general SQL database with support
 for metadata management, secondary indexes, joins, query optimization, and
 multi-tenancy. This is expected to continue as Phoenix implements a
 cost-based query optimizer and potentially transaction support, and
 surfaces new HBase security features such as encryption and cell-level
 security. Phoenix's developer community has also grown to include
 additional companies such as Intel, who have contributed join support to
 Phoenix, as well as Hortonworks, who are in the process of porting Phoenix
 to the 0.96 release of HBase.

 Rationale

 As usage and the number of contributors to Phoenix has grown, we have
 sought for a long-term home for the project, and we believe the Apache
 foundation would be a great fit. Joining Apache would ensure that tried and
 true processes and procedures are in place for the growing number of
 organizations interested in contributing to Phoenix. Phoenix is also a good
 fit for the Apache foundation: Phoenix already interoperates with several
 existing Apache projects (HBase, Hadoop, Pig, BigTop). The Phoenix team is
 familiar with the Apache process and and believes in the Apache mission -
 the team already includes multiple Apache committers.

 Initial Goals

 The initial goals will be to move the existing codebase to Apache and
 integrate with the Apache development process. Once this is accomplished,
 we plan for incremental development and releases that follow the Apache
 guidelines.

 Current Status

 Phoenix has undergone two major and three minor releases (1.0, 1.1, 1.2,
 2.0, and 2.1) as well as many patch releases. Phoenix is being used in
 production by Salesforce.com as well as at other organizations. The Phoenix
 codebase is currently hosted at github.com, which will form the basis of
 the Apache git repository.

 Meritocracy

 The Phoenix project already operates on meritocratic principles. Phoenix
 has several developers from various organizations outside of Salesforce.com
 who have contributed major new features. While this process has remained
 mostly informal, as we do not have an official committer list, an implicit
 organization exists in which individuals who contribute major components
 act as maintainers for those modules. If accepted, the Phoenix project
 would include several of these participants as initial committers. We will
 work to identify all committers and PPMC members for the project and to
 operate under the ASF meritocratic principles.

 Community

 Acceptance

[RESULT][VOTE] Phoenix for incubator project

[Stack]

(Resend with fixed subject)

On Wed, Dec 11, 2013 at 9:00 AM, Stack st...@duboce.net wrote:

 Let me vote +1 (binding) and now close the VOTE.

 Here are the results (* means IPMC):

 +1s:
 Roman Shaposhnik(*)
 James Taylor
 Lars Hofhansl(*)
 Henry Saputra(*)
 Leif Hedstrom(*)
 Anil Gupta
 Ted Dunning(*)
 Patrick Reilly
 Andrew Purtell(*)
 Ashish
 Anoop John
 Bruno Mahé
 Ramkrishna S. Vasudevan
 Jonathan Hsieh
 Devaraj Das(*)
 Sergio Fernández(*)
 Alan D. Cabrera(*)
 Misha Nasledov
 Joris V.R.
 Mujtaba Chohan
 Johann Schleier-Smith
 Nick Dimiduk
 Eli Levine
 Steven Noels(*)
 Doug Meil
 Enis Söztutar(*)
 Olivier Lamy(*)
 Supun Kamburugamuva
 Imesh Gunaratne
 Michael Stack(*)

 +0s:
 None

 -1s:
 None

 With 30 +1s (13 binding) and no 0s or -1s, the vote passes.

 Thanks all who voted.
 St.Ack


 On Thu, Dec 5, 2013 at 1:43 PM, Stack st...@duboce.net wrote:

 Discussion of the Phoenix proposal has settled since its original
 posting on November 7th.  Feedback has been incorporated.

 Let us now move to a vote.

 Should Phoenix become an Apache incubator project?

 [] +1 Accept Phoenix into the Incubator
 [] +0 Don't care whether or which
 [] -1 Do not accept Phoenix into the Incubator because...

 The latest version of the proposal can be found here [1].  It is
 also posted below for your convenience.

 Let the vote run 72 hours.

 Thank you,
 St.Ack

 1. https://wiki.apache.org/incubator/PhoenixProposal




 Abstract

 Phoenix is an open source SQL query engine for Apache HBase, a NoSQL data
 store. It is accessed as a JDBC driver and enables querying and managing
 HBase tables using SQL.

 Proposal

 Phoenix is an open source SQL skin over HBase delivered as a
 client-embedded JDBC driver targeting low latency queries over HBase data.
 Phoenix takes your SQL query, compiles it into a series of HBase scans, and
 orchestrates the running of those scans to produce regular JDBC result
 sets. The table metadata is stored in an HBase table and versioned, such
 that snapshot queries over prior versions will automatically use the
 correct schema. Direct use of the HBase API, along with coprocessors and
 custom filters, results in performance on the order of milliseconds for
 small queries, or seconds for tens of millions of rows. Phoenix interfaces
 with both Pig and Map-reduce for the input and output of data.

 Background

 Phoenix initially started as an internal project at Salesforce.com to
 efficiently analyze big data stored in HBase. It was open sourced on Github
 about a year ago in Jan 2013. Over time Phoenix, together with HBase as the
 storage tier, has begun to evolve into a general SQL database with support
 for metadata management, secondary indexes, joins, query optimization, and
 multi-tenancy. This is expected to continue as Phoenix implements a
 cost-based query optimizer and potentially transaction support, and
 surfaces new HBase security features such as encryption and cell-level
 security. Phoenix's developer community has also grown to include
 additional companies such as Intel, who have contributed join support to
 Phoenix, as well as Hortonworks, who are in the process of porting Phoenix
 to the 0.96 release of HBase.

 Rationale

 As usage and the number of contributors to Phoenix has grown, we have
 sought for a long-term home for the project, and we believe the Apache
 foundation would be a great fit. Joining Apache would ensure that tried and
 true processes and procedures are in place for the growing number of
 organizations interested in contributing to Phoenix. Phoenix is also a good
 fit for the Apache foundation: Phoenix already interoperates with several
 existing Apache projects (HBase, Hadoop, Pig, BigTop). The Phoenix team is
 familiar with the Apache process and and believes in the Apache mission -
 the team already includes multiple Apache committers.

 Initial Goals

 The initial goals will be to move the existing codebase to Apache and
 integrate with the Apache development process. Once this is accomplished,
 we plan for incremental development and releases that follow the Apache
 guidelines.

 Current Status

 Phoenix has undergone two major and three minor releases (1.0, 1.1, 1.2,
 2.0, and 2.1) as well as many patch releases. Phoenix is being used in
 production by Salesforce.com as well as at other organizations. The Phoenix
 codebase is currently hosted at github.com, which will form the basis of
 the Apache git repository.

 Meritocracy

 The Phoenix project already operates on meritocratic principles. Phoenix
 has several developers from various organizations outside of Salesforce.com
 who have contributed major new features. While this process has remained
 mostly informal, as we do not have an official committer list, an implicit
 organization exists in which individuals who contribute major components
 act as maintainers for those modules. If accepted, the Phoenix project
 would include several of these participants as initial committers. We will
 work

[VOTE] Phoenix for incubator project

[Stack]

 HBase data so that
they get the performance benefits of using Phoenix.

A Excessive Fascination with the Apache Brand

Phoenix is already a healthy and relatively well known open source project.
This proposal is not for the purpose of generating publicity. Rather, the
primary benefits to joining Apache are those outlined in the Rationale
section.

Documentation

Additional documentation on Phoenix may be found on its github website:

Phoenix overview:
https://github.com/forcedotcom/phoenix/blob/master/README.md

Phoenix wiki: https://github.com/forcedotcom/phoenix/wiki

Phoenix road map: https://github.com/forcedotcom/phoenix/wiki#roadmap

Phoenix issue tracking:
https://github.com/forcedotcom/phoenix/issues?direction=descsort=updatedstate=open

Phoenix codebase: https://github.com/forcedotcom/phoenix

Phoenix SQL language reference: http://forcedotcom.github.io/phoenix/

Phoenix performance:
https://github.com/forcedotcom/phoenix/wiki/Performance#phoenix-vs-related-products

User group: https://groups.google.com/group/phoenix-hbase-user

Initial Source

The Phoenix codebase is currently hosted on Github:
https://github.com/forcedotcom/phoenix.

Source and Intellectual Property Submission Plan

Currently, the Phoenix codebase is distributed under a BSD license. Upon
entering Apache, the Phoenix license will be migrated to the Apache 2.0
License.

External Dependencies

Beyond relying on Apache HBase, Phoenix has the following external
dependencies:

ANTLR 3.5 (BSD license: http://www.antlr3.org/license.html)

Sqlline 1.1.2 (BSD license:
https://github.com/julianhyde/sqlline/blob/master/LICENSE)

Open CSV 2.3 (Apache 2.0 license)

Upon acceptance to the incubator, we would begin a thorough analysis of all
transitive dependencies to verify this information and introduce license
checking into the build and release process by integrating with Apache Rat.

Required Resources

Mailing list

We will migrate the existing Phoenix mailing lists as follows:

phoenix-hbase-u...@googlegroups.com -- us...@phoenix.incubator.apache.org

phoenix-hbase-...@googlegroups.com -- d...@phoenix.incubator.apache.org

priv...@phoenix.incubator.apache.org for IPMC members

comm...@phoenix.incubator.apache.org

The latter is to be consistent with the new PIAO naming scheme for podlings.

Source control

The Phoenix team would like to use Git for source control, due to our
current use of Git. We request a writeable Git repo for Phoenix, and
mirroring to be set up to Github through INFRA.

Issue Tracking

Phoenix currently uses the github issue tracking system associated with its
github repo:
https://github.com/forcedotcom/phoenix/issues?direction=descsort=updatedstate=open.
We will migrate to the Apache JIRA:
http://issues.apache.org/jira/browse/PHOENIX

Other Resources

Jenkins/Hudson for builds and test running.
Wiki for documentation purposes
Blog to improve project dissemination

Initial Committers

James Taylor jtaylor at salesforce dot com

Mujtaba Chohan mchohan at salesforce dot com

Jesse Yates jyates at apache dot org

Eli Levine elevine at salesforce dot com

Simon Toens stoens at salesforce dot com

Maryann Xue wei.xue at intel dot com

Anoop Sam John anoopsamjohn at apache dot org

Ramkrishna S Vasudevan ramkrishna at apache dot org

Jeffrey Zhong jeffreyz at apache dot org

Nick Dimiduk ndimiduk at apache dot org

Affiliations

The initial committers are from three organizations: Salesforce.com, Intel,
and Hortonworks.

James Taylor (Salesforce.com)
Mujtaba Chohan (Salesforce.com)
Jesse Yates (Salesforce.com)
Eli Levine (Salesforce.com)
Simon Toens (Salesforce.com)
Maryann Xue (Intel)
Anoop Sam John (Intel)
Ramkrishna S Vasudevan (Intel)
Jeffrey Zhong (Hortonworks)
Nick Dimiduk (Hortonworks)

Sponsors

Champion

Michael Stack

Nominated Mentors

Michael Stack
Lars Hofhansl
Andrew Purtell
Devaraj Das
Enis Soztutar
Steven Noels

Sponsoring Entity

The Apache Incubator

Re: [VOTE] Accept Twill for Incubation

[Stack]

+1


St.Ack


On Thu, Nov 7, 2013 at 1:04 PM, Andreas Neumann a...@apache.org wrote:

 The discussion about the Weave proposal has calmed. As the outcome of the
 discussion, we have chosen a new name for the project, Twill. I would like
 to call a vote for Twill to become an incubated project.

 The proposal is pasted below, and also available at:
 https://wiki.apache.org/incubator/TwillProposal

 Let's keep this vote open for three business days, closing the voting on
 Tuesday 11/12.

 [ ] +1 Accept Twill into the Incubator
 [ ] +0 Don't care.
 [ ] -1 Don't accept Twill because...

 -Andreas.

 = Abstract =

 Twill is an abstraction over Apache Hadoop® YARN that reduces the
 complexity of developing distributed applications, allowing developers to
 focus more on their business logic.

 = Proposal =

 Twill is a set of libraries that reduces the complexity of developing
 distributed applications. It exposes the distributed capabilities of Apache
 Hadoop® YARN via a simple and intuitive programming model similar to Java
 threads. Twill also has built-in capabilities required by many distributed
 applications, such as real-time application logs and metrics collection,
 application lifecycle management, and network service discovery.

 = Background =

 Hadoop YARN is a generic cluster resource manager that supports any type of
 distributed application. However, YARN’s interfaces are too low level for
 rapid application development. It requires a great deal of boilerplate code
 even for a simple application, creating a high ramp up cost that can turn
 developers away.

 Twill is designed to improve this situation with a programming model that
 makes running distributed applications as easy as running Java threads.
 With the abstraction provided by Twill, applications can be executed in
 process threads during development and unit testing and then be deployed to
 a YARN cluster without any modifications.

 Twill also has built-in support for real-time application logs and metrics
 collection, delegation token renewal, application lifecycle management, and
 network service discovery. This greatly reduces the pain that developers
 face when developing, debugging, deploying and monitoring distributed
 applications.

 Twill is not a replacement for YARN, it’s a framework that operates on top
 of YARN.

 = Rationale =

 Developers who write YARN applications typically find themselves
 implementing the same (or similar) boilerplate code over and over again
 for every application. It makes sense to distill this common code into a
 reusable set of libraries that is perpetually maintained and improved by a
 diverse community of developers.

 Twill’s simple thread-like programming model will enable many Java
 programmers to develop distributed applications. We believe that this
 simplicity will attract developers who would otherwise be discouraged by
 complexity, and many new use cases will emerge for the usage of YARN.

 Incubating Twill as an Apache project makes sense because Twill is a
 framework built on top of YARN, and Twill uses Apache Zookeeper, HDFS,
 Kafka, and other Apache software (see the External Dependencies section).

 = Current Status =

 Twill was initially developed at Continuuity under the name of Weave. The
 Weave codebase is currently hosted in a public repository at github.com,
 which will seed the Apache git repository after renaming to Twill.

 == Meritocracy ==

 Our intent with this incubator proposal is to start building a diverse
 developer community around Twill following the Apache meritocracy model.
 Since Twill was initially developed in early 2013, we have had fast
 adoption and contributions within Continuuity. 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 ==

 Twill is currently being used internally at Continuuity and is at the core
 of our products. We hope to extend our contributor base significantly and
 we will invite all who are interested in simplifying the development of
 distributed applications to participate.

 == Core Developers ==

 Twill is currently being developed by five engineers at Continuuity:
 Terence Yim, Andreas Neumann, Gary Helmling, Poorna Chandra and Albert
 Shau.
 Terence Yim is an Apache committer for Helix, Andreas is an Apache
 committer and PMC member for Oozie, and Gary Helmling is an Apache
 committer and PMC member for HBase. Poorna Chandra and Albert Shau have
 made many contributions to Twill.

 == Alignment ==

 The ASF is the natural choice to host the Twill project as its goal of
 encouraging community-driven open source projects fits with our vision for
 Twill.

 Additionally, many other projects with which we are familiar and expect
 Twill to integrate with, such as ZooKeeper, YARN, HDFS, log4j, and others
 

Re: [VOTE] Accumulo to join the Incubator

[Stack]

+1 (non-binding)
St.Ack

On Fri, Sep 9, 2011 at 9:22 AM, Doug Cutting cutt...@apache.org wrote:
 It's been a week since the Accumulo proposal was submitted for
 discussion.  A few questions were asked, and the proposal was clarified
 in response.  Sufficient mentors have volunteered.  I thus feel we are
 now ready for a vote.

 The latest proposal can be found at the end of this email and at:

  http://wiki.apache.org/incubator/AccumuloProposal

 The discussion regarding the proposal can be found at:

  http://s.apache.org/oi

 Please cast your votes:

 [  ] +1 Accept Accumulo for incubation
 [  ] +0 Indifferent to Accumulo incubation
 [  ] -1 Reject Accumulo for incubation

 This vote will close 72 hours from now.

 Thanks,

 Doug

 ---

 = Accumulo Proposal =

 == Abstract ==
 Accumulo is a distributed key/value store that provides expressive,
 cell-level access labels.

 == Proposal ==
 Accumulo is a sorted, distributed key/value store based on Google's
 BigTable design.  It is built on top of Apache Hadoop, Zookeeper, and
 Thrift.  It features a few novel improvements on the BigTable design in
 the form of cell-level access labels and a server-side programming
 mechanism that can modify key/value pairs at various points in the data
 management process.

 == Background ==
 Google published the design of BigTable in 2006.  Several other open
 source projects have implemented aspects of this design including HBase,
 CloudStore, and Cassandra.  Accumulo began its development in 2008.

 == Rationale ==
 There is a need for a flexible, high performance distributed key/value
 store that provides expressive, fine-grained access labels.  The
 communities we expect to be most interested in such a project are
 government, health care, and other industries where privacy is a
 concern.  We have made much progress in developing this project over the
 past 3 years and believe both the project and the interested communities
 would benefit from this work being openly available and having open
 development.

 == Current Status ==

 === Meritocracy ===
 We intend to strongly encourage the community to help with and
 contribute to the code.  We will actively seek potential committers and
 help them become familiar with the codebase.

 === Community ===
 A strong government community has developed around Accumulo and training
 classes have been ongoing for about a year.  Hundreds of developers use
 Accumulo.

 === Core Developers ===
 The developers are mainly employed by the National Security Agency, but
 we anticipate interest developing among other companies.

 === Alignment ===
 Accumulo is built on top of Hadoop, Zookeeper, and Thrift.  It builds
 with Maven.  Due to the strong relationship with these Apache projects,
 the incubator is a good match for Accumulo.

 == Known Risks ==
 === Orphaned Products ===
 There is only a small risk of being orphaned.  The community is
 committed to improving the codebase of the project due to its fulfilling
 needs not addressed by any other software.

 === Inexperience with Open Source ===
 The codebase has been treated internally as an open source project since
 its beginning, and the initial Apache committers have been involved with
 the code for multiple years.  While our experience with public open
 source is limited, we do not anticipate difficulty in operating under
 Apache's development process.

 === Homogeneous Developers ===
 The committers have multiple employers and it is expected that
 committers from different companies will be recruited.

 === Reliance on Salaried Developers ===
 The initial committers are all paid by their employers to work on
 Accumulo and we expect such employment to continue.  Some of the initial
 committers would continue as volunteers even if no longer employed to do so.

 === Relationships with Other Apache Products ===
 Accumulo uses Hadoop, Zookeeper, Thrift, Maven, log4j, commons-lang,
 -net, -io, -jci, -collections, -configuration, -logging, and -codec.

 === Relationship to HBase ===
 Accumulo and HBase are both based on the design of Google's BigTable, so
 there is a danger that potential users will have difficulty
 distinguishing the two.  Some of the key areas in which Accumulo differs
 from HBase are discussed below.  It may be possible to incorporate the
 desired features of Accumulo into HBase.  However, the amount of work
 required would slow development of HBase and Accumulo considerably.  We
 believe this warrants a podling for Accumulo at the current time.  We
 expect active cross-pollination will occur between HBase and podling
 Accumulo and it is possible that the codebases and projects will
 ultimately converge.

  Access Labels 
 Accumulo has an additional portion of its key that sorts after the
 column qualifier and before the timestamp.  It is called column
 visibility and enables expressive cell-level access control.
 Authorizations are passed with each query to control what data is
 returned 

Re: Accumulo incubator proposal: Statement of Concern

[Stack]

On Tue, Sep 6, 2011 at 7:41 PM, Adam P Fuchs adam.p.fu...@ugov.gov wrote:
 ...Furthermore, I believe that having both projects be part of ASF gives us 
 more of an opportunity to collaborate going forwards. Whether we find that 
 there are enough competing ideas to support two top level projects, or 
 whether we end up collapsing Accumulo and HBase into one project, I think 
 that the competition and collaboration we will see in the short term will be 
 healthy for both projects.


IMO, the HBase project would be more into collaborating than it would
be up for competing.

The differences listed in the proposal are minor IMO.  If you'd come
to the hbase project, even now, today, and said add a label to the
KeyValue and you'll get a set of smart developers on board and a bunch
of new users, it would be done.  I agree w/ Doug that 'unlikely to' is
not a correct characterization.  Similar for Accumulo Iterators (hbase
TRUNK coprocessors seem to be a more generic Iterator facility).

But rumor has it though that the differences while small looking when
described in a short incubator proposal, in implementation, the code
is very different making an integration project, unfortunately, a
piece of work.

I'd be up for exploring how we can come together.  I've not seen the
code so excuse me my idealism.

The discussion here has been enlightening.  The circumstances that
brought about this proposal are explained and why you could not ask
the hbase project do something like add a label to KeyValue.  I'm
gung-ho on gov going more foss.  If you lads are helping along that
effort, more power to you.

I'm looking forward to the code drop.  That you didn't use more hbase
code must mean that you came up with something better.  We want to rob
what you've come up with.

St.Ack
HBase Chief Janitor

P.S. I was surprised not to see Julian Assange alongside Doug as a
sponsor for this proposal

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Accumulo incubator proposal: Statement of Concern

[Stack]

On Wed, Sep 7, 2011 at 12:47 PM, Billie J Rinaldi
billie.j.rina...@ugov.gov wrote:
 On Wednesday, September 7, 2011 1:34:20 PM, Stack st...@duboce.net wrote:

 I agree w/ Doug that 'unlikely to' is not a correct characterization.

 Would the following alteration be more accurate?
 It may be possible to incorporate the desired features of Accumulo into 
 HBase.  However, the amount of work required at the current time would slow 
 development of HBase and Accumulo considerably.


From my perspective, that is more the case though your second sentence
above comes across as a setup for our not integrating.


 But rumor has it though that the differences while small looking when
 described in a short incubator proposal, in implementation, the code
 is very different making an integration project, unfortunately, a
 piece of work.

 Yes, the implementation is very different, and we had difficulty capturing 
 that in the proposal.


Understood.


 hbase TRUNK coprocessors seem to be a more generic Iterator facility

 Some types of functions (e.g. query-time aggregation) can be implemented in 
 both coprocessors and iterators, but coprocessors will not easily support the 
 entirety of iterator functionality.  Nor is the reverse true.  The two models 
 present different programming mechanisms for server-side processing.  It 
 would be useful to have both in the same project.


I'll take your word for it not having seen the code.

St.Ack

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Accumulo incubator proposal: Statement of Concern

[Stack]

On Wed, Sep 7, 2011 at 2:21 PM, Billie J Rinaldi
billie.j.rina...@ugov.gov wrote:
 How about this?
 It may be possible to incorporate the desired features of Accumulo into 
 HBase.  However, the amount of work required would slow development of HBase 
 and Accumulo considerably.  We believe this warrants a podling for Accumulo 
 at the current time.  We expect active cross-pollination will occur between 
 HBase and podling Accumulo and it is possible that the codebases and projects 
 will ultimately converge.


This is better than the former.
Good luck,
St.Ack

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org