[ANNOUNCE] Apache Tez 0.4.0-incubating released
The Apache Tez team is proud to announce the latest release of Apache Tez - version 0.4.0-incubating. Apache Tez is an application framework which allows for a complex directed-acyclic-graph of tasks for processing data and is built atop Apache Hadoop YARN. More details on Apache Tez can be found at http://tez.incubator.apache.org/ The release bits are available at: http://www.apache.org/dyn/closer.cgi/incubator/tez/tez-0.4.0-incubating/ The released maven artifacts have also been made available on repository.apache.org. We would like to thank all the contributors that made this release possible. Thanks Siddharth Seth on behalf of The Apache Tez Team
Re: Fw: [VOTE] Release Apache BatchEE 0.1-incubating
+1 (binding) Regards JB On 04/01/2014 10:03 PM, Mark Struberg wrote: FYI: BatchEE is voting on our first release. LieGrue, strub On Tuesday, 1 April 2014, 19:04, Romain Manni-Bucau wrote: +1 thanks Mark! Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-04-01 14:38 GMT+02:00 Mark Struberg : Hi! I'd like to call a VOTE on releasing Apache BatchEE 0.1-incubating. BatchEE is a JBatch implementation (based on the RI code) plus many useful extensions and additional SPI implementations. The following bugs and enhancements got implemented: Bug [BATCHEE-1] - move from javax.* dependencies to org.apache.geronimo.specs.* [BATCHEE-2] - make the thread creation an SPI [BATCHEE-3] - Job/StepContext getExecutionId()/getInstanceId() return wrong value on partition threads [BATCHEE-4] - Spec change on skip/retry exception matching coming in 1.1 [BATCHEE-5] - Metrics weren't fully implemented in RI for partition steps [BATCHEE-6] - JAX-RS requires an Application impl [BATCHEE-9] - Once a batch action (JobOperator) is invoked it should use a single ServicesManager and not a contextual one [BATCHEE-17] - Class 'IOs' is redundant in many modules [BATCHEE-19] - add TransactionManager support for IBM WebSphere [BATCHEE-24] - create the DB create table scripts for a few standard databases [BATCHEE-25] - entity StepExecutionEntity use reserved names as attributes New Feature [BATCHEE-7] - ModelMapper ItemProcessor [BATCHEE-8] - basic test module [BATCHEE-10] - helper to execute step directly in batchee-test [BATCHEE-11] - basic cli [BATCHEE-12] - bar goal for mvn plugin and support for cli [BATCHEE-13] - suuport more than string injecton types [BATCHEE-14] - add JobExecutionCallbackService [BATCHEE-15] - try to generate a diagram (png?) from a batch file through a mvn plugin [BATCHEE-16] - create a war with batchee-servlet [BATCHEE-18] - AsynchronousProcessor The release notes are available online: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12326689 Maven staging repo: https://repository.apache.org/content/repositories/orgapachebatchee-1000/ Source Release: http://repository.apache.org/content/repositories/orgapachebatchee-1000/org/apache/batchee/batchee/0.1-incubating/batchee-0.1-incubating-source-release.zip sha1: 2e5ffb5cf0c3b3bc762fbeed29bcc36b6d4abe75 My PGP release key 2FDB81B1 http://svn.apache.org/repos/asf/openwebbeans/trunk/KEYS I've staged the release commits in my private repo for a review https://github.com/struberg/incubator-batchee/tree/0.1-incubating-vote1 This gets merged to trunk once the VOTE succeeds. The VOTE will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 veto (and reason why) txs and LieGrue, strub -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] [RESULT] Release Apache BatchEE 0.1-incubating
The VOTE has passed with the following +1 Olivier Lamy (IPMC), Romain Manni-Bucau (PMC), Jean-Louis Montiero (PMC), Jean-Baptise Onofre (IPMC) Mark Struberg (IPMC) No +0 nor -1. LieGrue, strub On Wednesday, 2 April 2014, 12:18, Jean-Louis MONTEIRO wrote: +1 > >First release amazing work > > > >2014-04-02 4:53 GMT+02:00 Olivier Lamy : > >> +1 >> >> >> On 1 April 2014 23:38, Mark Struberg wrote: >> > Hi! >> > >> > I'd like to call a VOTE on releasing Apache BatchEE 0.1-incubating. >> > >> > >> > BatchEE is a JBatch implementation (based on the RI code) plus many >> useful extensions and additional SPI implementations. >> > >> > The following bugs and enhancements got implemented: >> > >> > >> > Bug >> > >> > [BATCHEE-1] - move from javax.* dependencies to >> org.apache.geronimo.specs.* >> > [BATCHEE-2] - make the thread creation an SPI >> > [BATCHEE-3] - Job/StepContext getExecutionId()/getInstanceId() >> return wrong value on partition threads >> > [BATCHEE-4] - Spec change on skip/retry exception matching coming in >> 1.1 >> > [BATCHEE-5] - Metrics weren't fully implemented in RI for partition >> steps >> > [BATCHEE-6] - JAX-RS requires an Application impl >> > [BATCHEE-9] - Once a batch action (JobOperator) is invoked it should >> use a single ServicesManager and not a contextual one >> > [BATCHEE-17] - Class 'IOs' is redundant in many modules >> > [BATCHEE-19] - add TransactionManager support for IBM WebSphere >> > [BATCHEE-24] - create the DB create table scripts for a few standard >> databases >> > [BATCHEE-25] - entity StepExecutionEntity use reserved names as >> attributes >> > >> > New Feature >> > >> > [BATCHEE-7] - ModelMapper ItemProcessor >> > [BATCHEE-8] - basic test module >> > [BATCHEE-10] - helper to execute step directly in batchee-test >> > [BATCHEE-11] - basic cli >> > [BATCHEE-12] - bar goal for mvn plugin and support for cli >> > [BATCHEE-13] - suuport more than string injecton types >> > [BATCHEE-14] - add JobExecutionCallbackService >> > [BATCHEE-15] - try to generate a diagram (png?) from a batch file >> through a mvn plugin >> > [BATCHEE-16] - create a war with batchee-servlet >> > [BATCHEE-18] - AsynchronousProcessor >> > >> > >> > >> > The release notes are available online: >> > >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12326689 >> > >> > Maven staging repo: >> > >> https://repository.apache.org/content/repositories/orgapachebatchee-1000/ >> > >> > Source Release: >> > >> http://repository.apache.org/content/repositories/orgapachebatchee-1000/org/apache/batchee/batchee/0.1-incubating/batchee-0.1-incubating-source-release.zip >> > sha1: 2e5ffb5cf0c3b3bc762fbeed29bcc36b6d4abe75 >> > >> > >> > My PGP release key 2FDB81B1 >> http://svn.apache.org/repos/asf/openwebbeans/trunk/KEYS >> > >> > >> > I've staged the release commits in my private repo for a review >> > >> > https://github.com/struberg/incubator-batchee/tree/0.1-incubating-vote1 >> > This gets merged to trunk once the VOTE succeeds. >> > >> > >> > >> > The VOTE will be open for 72 hours. >> > >> > [ ] +1 approve >> > >> > [ ] +0 no opinion >> > >> > [ ] -1 veto (and reason why) >> > >> > >> > >> > txs and LieGrue, >> > >> > strub >> >> >> >> -- >> Olivier Lamy >> Ecetera: http://ecetera.com.au >> http://twitter.com/olamy | http://linkedin.com/in/olamy >> > > > >-- >Jean-Louis > > > > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Stratosphere
Hi Guys, The proposal looks great and I would love to help to sign up as a Mentor if you guys still have space for one. - Henry On Sun, Mar 30, 2014 at 12:14 AM, Alan Gates wrote: > I would like to propose Stratosphere as an Apache Incubator project. I have > posted the proposal to https://wiki.apache.org/incubator/StratosphereProposal > and posted the text of the proposal below. > > Alan. > > = Stratosphere = > > == Abstract == > Stratosphere is an open source system for parallel data analysis. > Stratosphere deeply integrates MapReduce and database technologies to provide > expressive and optimizable programming interfaces and at the same time > efficient and scalable execution. > > == Proposal == > Stratosphere is an open source system for expressive, declarative, fast, and > efficient data analysis. Stratosphere combines the scalability and > programming flexibility of distributed MapReduce-like platforms with the > efficiency, out-of-core execution, and query optimization capabilities found > in parallel databases. > > == Background == > There is currently a need for general-purpose cluster computing platforms > that are compatible with the Hadoop ecosystem, are more efficient, easier to > use, and can support more applications than Hadoop MapReduce, but are not > restricted to a specific data model and language (such as the relational > model and a variant of SQL). Stratosphere fulfils these needs. > > Stratosphere exposes expressive APIs in Java and Scala (conceptually similar > to Spark, Cascading, Scalding) that allow arbitrary user-defined functions in > the same language and data model that the program is written in. Stratosphere > programs pass through a cost-based optimizer that finds the best execution > path for these programs depending on the data and cluster characteristics. > The design and implementation of Stratosphere is based on research that > generalizes query optimizers in relational databases. Stratosphere has a > distributed runtime that is architected upon the principles of parallel > databases, providing true pipelining (a basis for stream processing) and > efficient out-of-core algorithms for grouping, sorting, joining, and > aggregating data. Stratosphere provides first-class support for iterative > algorithms via a built-in iterate operator, covering Machine Learning and > graph analysis use cases. It achieves performance similar to Apache Giraph > without being a specialized graph processing system. > > Stratosphere has undergone three major releases (v0.1, v0.2, v0.4) and some > minor ones. > > == Rationale == > Stratosphere started out in 2008 as a research project by the Technical > University of Berlin, the Humboldt University of Berlin, and the Hasso > Plattner Institute, and has received subsequent funding from the German > Research Council, the European Institute of Innovation and Technology, the > European Commision, and industry. > > The traction of Stratosphere has by far exceeded our initial expectations, > and we are therefore seeking an organizational long-term home for > Stratosphere beyond the University walls that will house and further > encourage contributors from companies and other organizations that are > interested in Stratosphere. We believe that the Apache Software Foundation is > the ideal home for Stratosphere. Stratosphere integrates with several > existing Apache projects, such as HDFS, YARN, HBase, and Avro. The team is > familiar with the Apache processes and fully subscribes to the Apache > mission. One of the proposing members is a long-time Apache contributor and > PMC member. > > == Initial Goals == > * Move the existing codebase to Apache > * Integrate with the Apache development process > * Ensure all dependencies are compliant with Apache License version 2.0 > * Incremental development and releases per Apache guidelines > > > == Current Status == > === Meritocracy === > Stratosphere operated on meritocratic principles from the get go. The initial > project proposal submitted to the German Research Council > in 2008 stated that all code developed in the project will be released as > open source under the Apache 2 license. Currently, all the > discussions pertaining to Stratosphere development are public on > [[https://github.com/stratosphere/stratosphere|GitHub]] and our > [[https://groups.google.com/forum/#!forum/stratosphere-dev|mailing list]]. > The current incubation proposal includes the major code contributors to > Stratosphere. Several additional people have worked on the Stratosphere > codebase for research prototypes and 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 === > Currently, the core of Stratosphere is developed at TU Berlin, mainly by the > committers list
