Re: [VOTE] Release Apache Atlas version 0.7-incubating RC2

[Arun C Murthy]

+1 (binding)

Arun

On Fri, Jul 8, 2016 at 2:00 PM, Alan Gates  wrote:

> +1.
>
> I checked the LICENSE, DISCLAIMER, and NOTICE files.  Checked that there
> were no binary files in the distribution (there are images, but that seems
> ok).  Checked the signatures.  Did a build with a fresh local maven repo
> with -DskipTests set.
>
> When I built with tests it failed with:
> Running org.apache.atlas.TestUtils
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.171 sec
> - in org.apache.atlas.TestUtils
>
> Results :
>
> Failed tests:
>   StoreBackedTypeCacheTest.testGetTraitType:146 expected: but
> was:
>   StoreBackedTypeCacheTest.testHasTraitType:164 expected: but
> was:
>
> Tests run: 452, Failures: 2, Errors: 0, Skipped: 0
>
> This isn’t enough to scuttle the release, though it’s nice when tests
> pass.  I’m building on a Mac with JDK 1.8.
>
> Alan.
>
> > On Jul 6, 2016, at 00:09, Hemanth Yamijala  wrote:
> >
> > Hi all,
> >
> > This is a call for a vote on the Apache Atlas 0.7-incubating release
> > (release candidate RC2).
> >
> > A vote was held on developer mailing list and it passed with 7 +1s.
> >
> > Vote thread: https://s.apache.org/Czm4
> > Results thread: https://s.apache.org/PAeO
> >
> > The source tarball (*.tar.gz), signature (*.asc), checksum (*.md5,
> *.sha512):
> >
> https://dist.apache.org/repos/dist/dev/incubator/atlas/0.7.0-incubating-rc2/
> >
> > The SHA512 checksum of the archive is
> > 8B923CEA 2CDD32C8 7CE9A066 38002BFA 14F666DC C56F95AF 2805D5C1 08B58F9E
> 436E3E3C
> > 61B40908 474C67E7 782E720E 1BFA3678 B8099EBC 282F64C2 C16A48C4
> >
> > The commit id (15748e7bc5ed019a63326f201258e3a55d512d96) to be voted
> upon:
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-atlas.git;a=commit;h=15748e7bc5ed019a63326f201258e3a55d512d96
> >
> > The tag to be voted upon:
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-atlas.git;a=log;h=refs/tags/release-0.7-rc2
> >
> > The list of fixed issues:
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-atlas.git;a=blob;f=release-log.txt;hb=refs/heads/0.7-incubating
> >
> > Keys to verify the signature of the release artifact are available at:
> > http://www.apache.org/dist/incubator/atlas/KEYS
> > PGP release keys:
> > http://pgp.mit.edu/pks/lookup?op=vindex=0xA0E6F9F5D96BF0FD
> >
> > Note that this is a source only release and we are voting on the
> > source release-0.7-incubating-rc2.
> >
> > Please download, test, and try it out.
> >
> > Vote will be open for at least 72 hours till 9th July, 2016 1 AM Pacific
> time.
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove (and reason why)
> >
> > Thank you!
> >
> > Regards,
> > Hemanth
> >
> > -
> > 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 Atlas version 0.6-incubating

[Arun C Murthy]

+1 (binding)

Arun

On Thursday, December 24, 2015, Suma Shivaprasad  wrote:

> Hello folks,
>
> This is a call for a vote on the Apache Atlas 0.6 incubating release.
>
> A vote was held on developer mailing list and it passed with five +1's.
>
> Vote thread: http://s.apache.org/nxl
> Results thread: http://s.apache.org/HyG
>
> The source tarball (*.tar.gz), signature (*.asc), checksum (*.md5, *.sha):
>
> > *
> https://dist.apache.org/repos/dist/dev/incubator/atlas/0.6.0-incubating-rc2/
> <
> https://dist.apache.org/repos/dist/dev/incubator/atlas/0.6.0-incubating-rc2/
> >*
>
> The SHA512 checksum of the archive is
>
> CD7441A1 1790B2DA 52DA09D6 1ED4CF10 2B202D56 109DE7AE D86D1026 8EDE3A11
> CF9AD7BF 9FAEDF55 E5175EB2 137A01B6 A311ECA1 EEA6EBFE 3D6CFA7F 23BE6CC8
> The commit id (c8109a0177058d4a788d476a74d425a7593e7a9b) to be voted upon:
>
> >
>
> *
> https://git-wip-us.apache.org/repos/asf?p=incubator-atlas.git;a=commit;h=c8109a0177058d4a788d476a74d425a7593e7a9b
> <
> https://git-wip-us.apache.org/repos/asf?p=incubator-atlas.git;a=commit;h=c8109a0177058d4a788d476a74d425a7593e7a9b
> >*
> The tag to be voted upon:
>
> > *
> https://git-wip-us.apache.org/repos/asf?p=incubator-atlas.git;a=tag;h=refs/tags/release-0.6-rc2
> <
> https://git-wip-us.apache.org/repos/asf?p=incubator-atlas.git;a=tag;h=refs/tags/release-0.6-rc2
> >*
>
> The list of fixed issues:
>
> > *
> https://git-wip-us.apache.org/repos/asf?p=incubator-atlas.git;a=blob;f=release-log.txt;h=c778ff0014b355b88ede8296a6c849a19f8202d3;hb=refs/heads/branch-0.6-incubating
> <
> https://git-wip-us.apache.org/repos/asf?p=incubator-atlas.git;a=blob;f=release-log.txt;h=c778ff0014b355b88ede8296a6c849a19f8202d3;hb=refs/heads/branch-0.6-incubating
> >*
>
> Keys to verify the signature of the release artifact are available at:
> http://www.apache.org/dist/incubator/atlas/KEYS
> PGP release keys:
> http://pgp.mit.edu/pks/lookup?op=vindex=0x2DBD4D9B
>
> Note that this is a source only release and we are voting on the source
> (release-0.6-incubating-rc2 /
>
> Commit:
> c8109a0177058d4a788d476a74d425a7593e7a9b /
>
> Checksums:
> SHA512:
> CD7441A1 1790B2DA 52DA09D6 1ED4CF10 2B202D56 109DE7AE D86D1026 8EDE3A11
> CF9AD7BF 9FAEDF55 E5175EB2 137A01B6 A311ECA1 EEA6EBFE 3D6CFA7F 23BE6CC8
> MD5 : 32 A1 13 D6 E8 7A 8E C9  34 1C D3 45 E8 4D 90 E1).
>
> Vote will be open for atleast 72 hours ( atleast till 30th Dec 7:30 PM PST/
> 10:30 PM EST /31st Dec 9 AM IST).
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> Thanks!
>
> Regards,
> Suma
>

Re: [VOTE] Release Apache Atlas version 0.5-incubating

[Arun C Murthy]

+1 (binding)

Arun

 On Jun 24, 2015, at 6:46 PM, Venkatesh Seetharam venkat...@apache.org wrote:
 
 Hello folks,
 
 This is a call for a vote on the Apache Atlas 0.5 incubating release.
 
 A vote was held on developer mailing list and it passed with 9 +1's.
 
 Vote thread: http://s.apache.org/RyM
 Results thread: http://s.apache.org/f8S
 
 The source tarball (*.tar.gz), signature (*.asc), checksum (*.md5, *.sha):
 https://dist.apache.org/repos/dist/dev/incubator/atlas/0.5.0-incubating-rc0
 
 The commit id (318abdacd4c4d17a3d613c1cda04a58194042715) to ve voted upon:
 https://git-wip-us.apache.org/repos/asf?p=incubator-atlas.git;a=commit;h=318abdacd4c4d17a3d613c1cda04a58194042715
 
 The tag to be voted upon:
 https://git-wip-us.apache.org/repos/asf?p=incubator-atlas.git;a=tag;h=refs/tags/release-0.5-rc0
 
 The list of fixed issues:
 https://git-wip-us.apache.org/repos/asf?p=incubator-atlas.git;a=blob;f=release-log.txt;h=df92e95d408469b2bea5b988fb9be3de802b9f2b;hb=318abdacd4c4d17a3d613c1cda04a58194042715
 
 Keys to verify the signature of the release artifact are available at:
 http://www.apache.org/dist/incubator/atlas/KEYS
 PGP release keys:
 http://pgp.mit.edu/pks/lookup?op=vindexsearch=0x1B16738C42C7A5EA
 
 Note that this is a source only release and we are voting on the source.
 
 Checksums:
 SHA1 (apache-atlas-0.5-incubating-sources.tar.gz =
 ab21ce037e488a8e5b8986353adb853dc515abd4)
 MD5 (apache-atlas-0.5-incubating-sources.tar.gz) =
 e358ed601233f7d00ba9eb1c64095f55
 
 Vote will be open for 72 hours.
 
 [ ] +1 approve
 [ ] +0 no opinion
 [ ] -1 disapprove (and reason why)
 
 Thanks!
 
 Regards,
 Venkatesh


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

Re: [VOTE] Accept Apache Atlas into Apache Incubator

[Arun C Murthy]

+1 (binding)

thanks,
Arun

On May 1, 2015, at 12:26 AM, Seetharam Venkatesh venkat...@innerzeal.com 
wrote:

 Hello folks,
 
 Following the discussion earlier in the thread: http://s.apache.org/r2
 
 I would like to call a VOTE for accepting Apache Atlas as a new incubator
 project.
 
 The proposal is available at:
 https://wiki.apache.org/incubator/AtlasProposal
 Also, the text of the latest wiki proposal is included at the bottom of
 this email.
 
 The VOTE is open for at least the next 72 hours:
 
 [ ] +1 accept Apache Atlas into the Apache Incubator
 [ ] ±0 Abstain
 [ ] -1 because...
 
 Of course I am +1! (non-binding)
 
 Thanks!
 
 
 = Apache Atlas Proposal =
 
 == Abstract ==
 
 Apache Atlas is a scalable and extensible set of core foundational
 governance services that enables enterprises to effectively and efficiently
 meet their compliance requirements within Hadoop and allows integration
 with the complete enterprise data ecosystem.
 
 == Proposal ==
 
 Apache Atlas allows agnostic governance visibility into Hadoop, these
 abilities are enabled through a set of core foundational services powered
 by a flexible metadata repository.
 
 These services include:
 
 * Search and Lineage for datasets
 * Metadata driven data access control
 * Indexed and Searchable Centralized Auditing operational Events
 * Data lifecycle management – ingestion to disposition
 * Metadata interchange with other metadata tools
 
 == Background ==
 
 Hadoop is one of many platforms in the modern enterprise data ecosystem and
 requires governance controls commensurate with this reality.
 
 Currently, there is no easy or complete way to provide comprehensive
 visibility and control into Hadoop audit, lineage, and security for
 workflows that require Hadoop and non-Hadoop processing.
 
 Many solutions are usually point based, and require a monolithic
 application workflow.  Multi-tenancy and concurrency are problematic as
 these offerings are not aware of activity outside of their narrow focus.
 
 As Hadoop gains greater popularity, governance concerns will become
 increasingly vital to increasing maturity and furthering adoption. It is a
 particular barrier to expanding enterprise data under management.
 
 == Rationale ==
 
 Atlas will address issues previously discussed by providing governance
 capabilities in Hadoop -- using both a prescriptive and forensic model
 enriched by business taxonomical metadata.Atlas, at its core, is
 designed to exchange metadata with other tools and processes within and
 outside of the Hadoop stack -- enable governance controls that are truly
 platform agnostic and effectively (and defensibly) address compliance
 concerns.
 
 Initially working with a group of leading partners in several industries,
 Atlas is built to solve specific real world governance problems that
 accelerate product maturity and time to value.
 
 Atlas aims to grow a community to help build a widely adopted pattern for
 governance, metadata modeling and exchange in Hadoop – which will advance
 the interests for the whole community.
 
 == Current Status ==
 
 An initial version with a valuable set of features is developed by the list
 of initial committers and is hosted on github.
 
 === Meritocracy ===
 
 Our intent with this proposal is to start building a diverse  developer
 community around Atlas following the Apache meritocracy model. We have
 wanted to make the project open source and encourage contributors from
 multiple organizations from the start.
 
 We plan to provide plenty of support to new developers and to quickly
 recruit those who make solid contributions to committer status.
 
 === Community ===
 
 We are happy to report that the initial team already represents multiple
 organizations. We hope to extend the user and developer base further in the
 future and build a solid open source community around Atlas.
 
 === Core Developers ===
 
 Atlas development is currently being led by engineers from Hortonworks –
 Harish Butani, Venkatesh Seetharam, Shwetha G S, and Jon Maron. All the
 engineers have deep expertise in Hadoop and are quite familiar with the
 Hadoop Ecosystem.
 
 === Alignment ===
 
 The ASF is a natural host for Atlas given that it is already the home of
 Hadoop, Falcon, Hive,  Pig, Oozie, Knox, Ranger, and other emerging “big
 data” software projects.
 
 Atlas has been designed to solve the data governance challenges and
 opportunities of the Hadoop ecosystem family of products as well as
 integration to the tradition Enterprise Data ecosystem.
 
 Atlas fills the gap that the Hadoop Ecosystem has been lacking in the areas
 of data governance and compliance management.
 
 == Known Risks ==
 
 === Orphaned products  Reliance on Salaried Developers ===
 The core developers plan to work full time on the project. There is very
 little risk of Atlas getting orphaned.  A prototype of Atlas is in use and
 being actively developed by several companies and have vested interest in
 its continued 

Re: [VOTE] Release Apache Ranger 0.4.0 (incubating) - (formally known as Apache Argus)

[Arun C Murthy]

+1 (binding)

Checked license  signatures.

Arun

On Nov 13, 2014, at 12:33 AM, Selvamohan Neethiraj sneet...@apache.org wrote:

 The Apache Ranger community has voted on and approved a proposal to release 
 Apache Ranger 0.4.0 (incubating).
 
 This will be our first release since the project entered incubation in July 
 2014 as Apache Argus and then, got it renamed as Apache Ranger.
 
 The ranger-0.4.0-rc3 release candidate is now available with the following 
 artifacts up for a project vote :
 
 Git tag for the release:
   
 https://git-wip-us.apache.org/repos/asf?p=incubator-argus.git;a=shortlog;h=refs/tags/ranger-0.4.0-rc3
 
 Source release:
   
 http://people.apache.org/~sneethir/ranger/ranger-0.4.0-rc3/ranger-0.4.0-rc3.tar.gz
 
 Source release verification:
   PGP Signature:  
 http://people.apache.org/~sneethir/ranger/ranger-0.4.0-rc3/ranger-0.4.0-rc3.tar.gz.asc
   MD5/SHA  Hash:  
 http://people.apache.org/~sneethir/ranger/ranger-0.4.0-rc3/ranger-0.4.0-rc3.tar.gz.mds
   Keys to verify the signature of the release artifact are available at:  
 https://people.apache.org/keys/group/argus.asc
 
 Build verification steps can be found at:  
 http://argus.incubator.apache.org/quick_start_guide.html
 
 The vote will be open for at least 72 hours or until necessary number of 
 votes are reached.
 [ ] +1  approve
 [ ] +0  no opinion
 [ ] -1  disapprove (and reason why)
 
 Here is my +1 (non binding)
 
 Thanks
 Selva-


-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Re: [VOTE] Release Apache Tez-0.4.1-incubating RC0

[Arun C Murthy]

+1 (binding)

Arun

On Jul 7, 2014, at 1:20 PM, Siddharth Seth ss...@apache.org wrote:

 The Apache Tez Incubating PPMC has voted to release Apache
 Tez-0.4.1-incubating (RC0).
 
 Result Mail:
 http://mail-archives.apache.org/mod_mbox/incubator-tez-dev/201407.mbox/%3CCAOapipsBOizkB5yOmCxT1UP9%2BCL%2BHjtxcy39mzFNFkZXeocaxA%40mail.gmail.com%3E
 Initial Vote Thread:
 http://mail-archives.apache.org/mod_mbox/incubator-tez-dev/201406.mbox/%3CCAOapipsP5KfMD2_imfubp%2BUKc9qPA5b4EVAmRPqbv-utt%3DSNkQ%40mail.gmail.com%3E
 
 This thread is for the IPMC to vote on this release.
 
 GIT source tag:
 https://git-wip-us.apache.org/repos/asf/incubator-tez/repo?p=incubator-tez.git;a=log;h=refs/tags/release-0.4.1-incubating-rc0
 
 Staging site:
 https://dist.apache.org/repos/dist/dev/incubator/tez/tez-0.4.1-incubating-src-rc0/
 
 Nexus Staging URL:
 https://repository.apache.org/content/repositories/orgapachetez-1006/
 
 PGP release keys:
 http://pgp.mit.edu/pks/lookup?op=getsearch=0x477E02D33DD51430
 KEYS file available at
 https://dist.apache.org/repos/dist/release/incubator/tez/KEYS
 
 List of issues fixed in the release:
 *https://issues.apache.org/jira/browse/TEZ/fixforversion/12327143/
 https://issues.apache.org/jira/browse/TEZ/fixforversion/12327143/*
 Also available in CHANGES.txt within the release tarball.
 
 Vote will be open for at least 72 hours ( until the required number of IPMC
 votes are obtained).
 
 [ ] +1 approve
 [ ] +0 no opinion
 [ ] -1 disapprove (and reason why)
 
 
 Thanks
 
 - Sid



-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Re: [VOTE] Graduate Apache Tez from Apache Incubator to TLP

[Arun C Murthy]

+1 (binding)

Arun

On Jun 30, 2014, at 9:16 PM, Hitesh Shah hit...@apache.org wrote:

 Hello folks
 
 Tez entered incubation in February, 2013. Since then, we have made progress 
 towards graduation[1]. The Tez community recently voted positively towards 
 graduation[2] with 27 +1s.
 Of the 27, there were 5 IPMC votes from our mentors:
   - Alan Gates
- Arun C. Murthy
- Chris Mattman
- Chris Douglas
- Jakob Homan
 
 Now, I would like to ask the IPMC to vote for the graduation of Apache Tez.
 
 Please VOTE to indicate if Apache Tez is ready to graduate as a Top Level 
 Project. The board resolution is included below. 
 
 [ ] +1 Graduate Apache Tez as a TLP
 [ ] +0 Don't care.
 [ ] -1 Don't graduate Apache Tez as a TLP because…
 
 The vote will remain open for 72 hours. 
 
 thanks
 — Hitesh Shah ( on behalf of Tez PPMC )
 
 [1] 
 http://mail-archives.apache.org/mod_mbox/incubator-tez-dev/201406.mbox/%3ccfc4fef8.16337a%25chris.a.mattm...@jpl.nasa.gov%3E
 [2] 
 http://mail-archives.apache.org/mod_mbox/incubator-tez-dev/201406.mbox/%3ccaoapips7pjs_6hinkwk0uv0hnnrydqcg639dpf9vojeuto9...@mail.gmail.com%3E
 
 Board Resolution:
 --
 X. Establish the Apache Tez 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 fast and flexible large-scale data analysis
 on clusters.
 
 NOW, THEREFORE, BE IT RESOLVED, that a Project Management
 Committee (PMC), to be known as the Apache Tez Project, be
 and hereby is established pursuant to Bylaws of the Foundation;
 and be it further
 
 RESOLVED, that the Apache Tez Project be and hereby is
 responsible for the creation and maintenance of software
 related to efficient cluster management, resource isolation
 and sharing across distributed applications; and be it further
 RESOLVED, that the office of Vice President, Apache Tez 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 Tez Project, and to have primary responsibility for
 management of the projects within the scope of responsibility
 of the Apache Tez 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 Tez Project:
 
 * Alan Gates ga...@apache.org
 * Arun C. Murthy acmur...@apache.org
 * Ashutosh Chauhan hashut...@apache.org
 * Bill Graham billgra...@apache.org
 * Bikas Saha bi...@apache.org
 * Chris Douglas cdoug...@apache.org
 * Chris Mattmann mattm...@apache.org
 * Daryn Sharp da...@apache.org
 * Devaraj Das d...@apache.org
 * Gopal Vijayaraghavan gop...@apache.org
 * Gunther Hagleitner gunt...@apache.org
 * Hitesh Shah hit...@apache.org
 * Jitendra Pandey jiten...@apache.org
 * Jason Lowe jl...@apache.org
 * Jakob Homan jgho...@apache.org
 * Julien Le Dem jul...@apache.org
 * Kevin Wilfong kevinwilf...@apache.org
 * Mike Liddell mlidd...@apache.org
 * Mohammad Kamrul Islam kam...@apache.org
 * Namit Jain na...@apache.org
 * Nathan Roberts nrobe...@apache.org
 * Owen O’Malley omal...@apache.org
 * Rajesh Balamohan rbalamo...@apache.org
 * Robert Evans bo...@apache.org
 * Rohini Palaniswamy roh...@apache.org
 * Siddharth Seth ss...@apache.org
 * Tassapol Athiapinya tassap...@apache.org
 * Thomas Graves tgra...@apache.org
 * Tom White tomwh...@apache.org
 * Vikram Dixit vik...@apache.org
 * Vinod Kumar Vavilapalli vino...@apache.org
 
 NOW, THEREFORE, BE IT FURTHER RESOLVED, that Hitesh Shah be
 appointed to the office of Vice President, Apache Tez, 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 Tez Project be and hereby is
 tasked with the migration and rationalization of the Apache
 Incubator Tez podling; and be it further
 
 RESOLVED, that all responsibilities pertaining to the Apache
 Incubator Tez podling encumbered upon the Apache Incubator
 Project are hereafter discharged.
 --
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 




-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message

Re: [VOTE] Accept Slider into the incubator

[Arun C Murthy]

+1 (binding)

thanks,
Arun

On Apr 17, 2014, at 6:01 AM, Steve Loughran ste...@hortonworks.com wrote:

 I'd like to call a vote on accepting Slider into the incubator
 
 
 https://wiki.apache.org/incubator/SliderProposal
 
 [ ] +1 Accept Slider into the Incubator
 [ ] +0 Indifferent to the acceptance of Slider
 [ ] -1 Do not accept Slider because …
 
 
 The vote will be open until Thursday April 24 13:00 UTC
 
 -Steve
 


-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

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

Re: Slider Proposal

[Arun C. Murthy]

Looks great, thanks for the update Steve.

Arun


 On Mar 31, 2014, at 8:49 PM, Steve Loughran ste...@hortonworks.com wrote:
 
 Hi
 
 
 For people wondering what's been happening with that Hoya proposal, I've
 got a successor proposal up for discussion.
 
 
 https://wiki.apache.org/incubator/SliderProposal
 
 This proposal -as well as having a different name- is a superset of the
 original draft. It emphasises that making the tool usable by other
 applications via a client API is a key need -it's how some people have been
 using Hoya- and that packaging and service registration and discovery are
 key areas for improvement.
 
 
 The code is up on github at https://github.com/hortonworks/slider for
 people to download and play with
 
 If you look closely you'll see that the packaging is still .hoya, as are a
 lot of the classnames. That's something we'll fix during incubation, along
 with some of the code packaging.
 
 
 Comments?
 
 -Stevve
 
 -- 
 CONFIDENTIALITY NOTICE
 NOTICE: This message is intended for the use of the individual or entity to 
 which it is addressed and may contain information that is confidential, 
 privileged and exempt from disclosure under applicable law. If the reader 
 of this message is not the intended recipient, you are hereby notified that 
 any printing, copying, dissemination, distribution, disclosure or 
 forwarding of this communication is strictly prohibited. If you have 
 received this communication in error, please contact the sender immediately 
 and delete it from your system. Thank You.

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

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

Re: [VOTE] Release Apache Tez-0.4.0-incubating RC1

[Arun C. Murthy]

+1 (binding)

Arun

 On Apr 1, 2014, at 11:42 PM, Siddharth Seth ss...@apache.org wrote:
 
 I have created a tez-0.4.0-incubating release candidate (rc1).
 
 This includes license and notice files missing from rc0 release artifacts
 (the javadoc artifact has these files under resources/META-INF instead of
 directly under META-INF)
 
 GIT source tag:
 https://git-wip-us.apache.org/repos/asf/incubator-tez/repo?p=incubator-tez.git;a=log;h=refs/tags/release-0.4.0-incubating-rc1
 (git commit 145c730c8d1cea863185b2a3354b19f2ab21addd)
 
 Staging site:
 https://dist.apache.org/repos/dist/dev/incubator/tez/0.4.0-incubating-rc1
 (svn revision 4929)
 
 Nexus Staging URL:
 *https://repository.apache.org/content/repositories/orgapachetez-1005/
 https://repository.apache.org/content/repositories/orgapachetez-1005/*
 
 PGP release keys:
 http://pgp.mit.edu/pks/lookup?op=getsearch=0x477E02D33DD51430
 KEYS file available at
 https://dist.apache.org/repos/dist/release/incubator/tez/KEYS
 
 List of issues fixed in the release:
 https://issues.apache.org/jira/browse/TEZ/fixforversion/12326283/
 Also available in CHANGES.txt within the release tarball.
 
 Vote will be open for at least 72 hours ( until the required number of IPMC
 votes are obtained
 ).
 
 [ ] +1 approve
 [ ] +0 no opinion
 [ ] -1 disapprove (and reason why)
 
 For folks not familiar with vetting a release, please refer to
 http://incubator.apache.org/guides/releasemanagement.html#check-list
 
 Thanks
 - Sid

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

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

Re: [VOTE] Release Apache Tez-0.3.0-incubating RC0

[Arun C Murthy]

+1 (binding)

Arun

On Feb 23, 2014, at 11:31 AM, Hitesh Shah hit...@apache.org wrote:

 Hello folks,
 
 I have created a tez-0.3.0-incubating release candidate (rc0). This is the 
 second release for Tez. 
 
 GIT source tag: 
 https://git-wip-us.apache.org/repos/asf/incubator-tez/repo?p=incubator-tez.git;a=log;h=refs/tags/release-0.3.0-incubating-rc0
 Staging site: 
 https://dist.apache.org/repos/dist/dev/incubator/tez/0.3.0-incubating-rc0/
 Nexus Staging URL: 
 https://repository.apache.org/content/repositories/orgapachetez-1002
 
 PGP release keys: 
 http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xA9510905F0B000F0
 KEYS file also available at 
 https://dist.apache.org/repos/dist/release/incubator/tez/KEYS
 
 One can look into the issues fixed in this release at: 
 https://issues.apache.org/jira/browse/TEZ/fixforversion/12325655 or look at 
 the CHANGES.txt in the release tarball.
 
 Vote will be open for at least 72 hours ( until the required number of IPMC 
 votes are obtained ).
 
 [ ] +1 approve
 [ ] +0 no opinion
 [ ] -1 disapprove (and reason why)
 
 For folks not familiar with vetting a release, please refer to 
 http://incubator.apache.org/guides/releasemanagement.html#check-list
 
 thanks
 -- Hitesh
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 



-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Re: [VOTE] Release Apache Tez-0.2.0-incubating RC0

[Arun C Murthy]

+1 (binding)

Arun

On Nov 25, 2013, at 4:33 PM, Hitesh Shah hit...@apache.org wrote:

 Hello folks,
 
 I have created a tez-0.2.0-incubating release candidate (rc0). This is the 
 first release for Tez. Therefore, please do not be gentle. 
 
 GIT source tag: 
 https://git-wip-us.apache.org/repos/asf/incubator-tez/repo?p=incubator-tez.git;a=log;h=refs/tags/release-0.2.0-rc0
 Staging site: 
 http://people.apache.org/~hitesh/tez-release-rc/tez-0.2.0-incubating-rc0/
 Nexus Staging URL: 
 https://repository.apache.org/content/repositories/orgapachetez-002/
 
 PGP release keys: 
 http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0xA9510905F0B000F0
 KEYS file also available at 
 https://dist.apache.org/repos/dist/release/incubator/tez/KEYS
 
 One can look into the issues fixed in this release at: 
 https://issues.apache.org/jira/browse/TEZ/fixforversion/12324349
 
 Vote will be open for 72 hours.
 
 [ ] +1 approve
 [ ] +0 no opinion
 [ ] -1 disapprove (and reason why)
 
 thanks
 -- Hitesh
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 

--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/



-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Re: [VOTE] Graduate Ambari from Apache Incubator

[Arun C. Murthy]

 
 [  ] +1 Graduate Ambari from Incubator

+1 for graduation (binding)

thanks,
Arun


 On Nov 15, 2013, at 9:12 AM, Yusaku Sako yus...@hortonworks.com wrote:
 
 This is a call for vote to graduate Ambari from Apache Incubator.
 
 The Apache Ambari project has been incubating since August 2011.
 We have made significant progress with the project during the two years
 of Incubation, adding 27 committers for a total of 36 committers [1], and
 producing 8 releases following ASF policies and guidelines.
 The Apache Ambari community has voted to graduate Ambari as a TLP [2].
 The community vote results can be found at [3].
 The discussion thread for the board resolution can be found at [4].
 
 Please cast your votes:
 
 [  ] +1 Graduate Ambari from Incubator
 [  ] +0 Indifferent to graduation status of Ambari
 [  ] -1 Reject graduation of Ambari from Incubator
 
 This vote will remain open for at least 72 hours from now.
 Please find the proposed board resolution below.
 
 [1] http://people.apache.org/committers-by-project.html#ambari
 [2] http://markmail.org/thread/cp5ajf2uvfl3oj66
 [3] http://markmail.org/message/l6zss4rgfcs3gvpm
 [4] http://markmail.org/thread/36dplr3pwzmazwmg
 
 Regards,
 Yusaku Sako
 
 ###
 
 X. Establish the Apache Ambari 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 Hadoop cluster management.
 
  NOW, THEREFORE, BE IT RESOLVED, that a Project Management
  Committee (PMC), to be known as the Apache Ambari Project,
  be and hereby is established pursuant to Bylaws of the
  Foundation; and be it further
 
  RESOLVED, that the Apache Ambari Project be and hereby is
  responsible for the creation and maintenance of software
  related to Hadoop cluster management;
  and be it further
 
  RESOLVED, that the office of Vice President, Apache Ambari 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 Ambari Project, and to have primary responsibility
  for management of the projects within the scope of
  responsibility of the Apache Ambari 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 Ambari Project:
 
* Babiichuk Andriy (ababiichuk)
* Arun Murthy (acmurthy)
* Aleksandr Kovalenko (akovalenko)
* Antonenko Aleksandr Igorevich (alexantonenko)
* Andrii Tkach (atkach)
* Bernd Fondermann (berndf)
* Billie Rinaldi (billie)
* Christopher Douglas (cdouglas)
* Chad Roberts (croberts)
* Devaraj Das (ddas)
* Dmitry Lysnichenko (dmitriusan)
* Dmytro Sen (dsen)
* Eric Yang (eyang)
* Hitesh Shah (hitesh)
* Jagane Sundar (jagane)
* Jaimin Jetly (jaimin)
* Jitendra Pandey (jitendra)
* John Speidel (jspeidel)
* Kan Zhang (kzhang)
* Mahadev Konar (mahadev)
* Papirkovskyy Myroslav (mpapirkovskyy)
* Nate Cole (ncole)
* Oleksandr Diachenko (odiachenko)
* Owen O’Malley (omalley)
* Oleg Nechiporenko (onechiporenko)
* Ramya Sunil (ramya)
* Varun Kapoor (reznor)
* Sumit Mohanty (smohanty)
* Srimanth Gunturi (srimanth)
* Siddharth Wagle (swagle)
* Thomas Beerbower (tbeerbower)
* Suhas (vgogate)
* Vikram Dixit K (vikram)
* Vinod Kumar Vavilapalli (vinodkv)
* Xi Wang (xiwang)
* Yusaku Sako (yusaku)
 
 
  NOW, THEREFORE, BE IT FURTHER RESOLVED, that Yusaku Sako
  be appointed to the office of Vice President, Apache Ambari, 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 Ambari 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 Ambari Project; and be it further
 
  RESOLVED, that the Apache Ambari Project be and hereby
  is tasked with the migration and rationalization of the Apache
  Incubator Ambari podling; and be it further
 
  RESOLVED, that all responsibilities pertaining to the Apache
  Incubator Ambari podling encumbered upon the Apache Incubator
  Project are hereafter discharged.
 
 -- 
 CONFIDENTIALITY NOTICE
 NOTICE: This message is intended for the use of the individual or entity 

Re: [VOTE] Accept Twill for Incubation

[Arun C Murthy]

, HDFS, log4j, and others
 mentioned in the External Dependencies section are Apache projects, and
 Twill will benefit by close proximity to them.
 
 = Known Risks =
 
 == Orphaned Products ==
 
 There is very little risk of Twill being orphaned, as it is a key part of
 Continuuity’s products. The core Twill developers plan to continue to work
 on Twill, and Continuuity has funding in place to support their efforts
 going forward.
 Many other Big Data companies can benefit from Twill, and we have already
 received interest from various entities that would like to use and
 contribute to Twill.
 
 == Inexperience with Open Source ==
 
 Several of the core developers have experience with open source
 development. Terence Yim, Andreas Neumann and Gary Helmling are currently
 Apache committers for Helix, Oozie and HBase respectively
 Homogeneous Developers
 
 The current core developers are all Continuuity employees. However, we
 intend to establish a developer community that includes independent and
 corporate contributors. We are encouraging new contributors via our mailing
 lists, public presentations, and personal contacts, and we will continue to
 do so. Various entities have already expressed interest in becoming
 involved with Twill.
 
 == Reliance on Salaried Developers ==
 
 Currently, these developers are paid to work on Twill. Once the project has
 built a community, we expect to attract committers, developers and
 community
 other than the current core developers. However, because Continuuity
 products use Twill internally, the reliance on salaried developers is
 unlikely to change, at least in the near term.
 
 == Relationships with Other Apache Products ==
 
 Twill is deeply integrated with Apache projects. Twill uses Apache YARN as
 its underlying resource management and task scheduling system and Apache
 Zookeeper for coordination. In addition, Twill uses Apache HDFS and Apache
 Kafka. A number of other Apache projects are Twill dependencies and are
 listed in the External Dependencies section.
 
 == An Excessive Fascination with the Apache Brand ==
 
 While we respect the reputation of the Apache brand and have no doubt that
 it will attract contributors and users, our interest is primarily to give
 Twill a solid home as an open source project following an established
 development model. We have also given additional reasons in the Rationale
 and Alignment sections.
 
 = Documentation =
 
 The current documentation for Weave is at
 https://github.com/continuuity/weave.
 This will be adapted to the new name Twill.
 
 = Initial Source =
 
 The Weave codebase is currently hosted at
 https://github.com/continuuity/weave. Weave will be renamed to Twill to
 seed the Apache git repository.
 
 = External Dependencies =
 
 The dependencies all have Apache-compatible licenses:
 * avro (Apache 2.0)
 * hadoop (Apache 2.0)
 * gson (Apache 2.0)
 * guava-libraries (Apache 2.0)
 * hbase (Apache 2.0)
 * hdfs (Apache 2.0)
 * kafka (Apache 2.0)
 * netty (Apache 2.0)
 * snappy-java (Apache 2.0)
 * yarn (Apache 2.0)
 * zookeeper (Apache 2.0)
 * asm (BSD)
 * junit (EPL v1.0)
 * logback (EPL v1.0 )
 * slf4j (MIT)
 
 = Cryptography =
 
 Twill will depend on secure Hadoop, which can optionally use Kerberos.
 
 = Required Resources =
 
 == Mailing Lists ==
 
 * twill-private for private PMC discussions (with moderated subscriptions)
 * twill-dev for technical discussions among contributors
 * twill-commits for notification about commits
 
 == Subversion Directory ==
 
 Git is the preferred source control system: git://git.apache.org/twill
 
 == Issue Tracking ==
 
 JIRA Twill (TWILL)
 
 == Other Resources ==
 
 The existing code already has unit tests, so we would like a Hudson
 instance to run them whenever a new patch is submitted. This can be added
 after project creation.
 
 = Initial Committers =
 
 * Terence Yim
 * Andreas Neumann
 * Gary Helmling
 * Poorna Chandra
 * Albert Shau
 
 = Affiliations =
 
 * Terence Yim (Continuuity)
 * Andreas Neumann (Continuuity)
 * Gary Helmling (Continuuity)
 * Poorna Chandra (Continuuity)
 * Albert Shau (Continuuity)
 
 = Sponsors =
 
 == Champion ==
 
 Vinod K vinodkv at apache dot org (Apache Member)
 
 == Nominated Mentors ==
 
 * Arun C Murthy acmurthy at apache dot org
 * Tom White tomwhite at apache dot org
 * Patrick Hunt phunt at apache dot org
 * Andrei Savu asavu at apache dot org
 
 == Sponsoring Entity ==
 
 We are requesting that the Incubator sponsor this project.

--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/



-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly

Re: [VOTE] Apache Ambari 1.2.5-incubating RC1

[Arun C Murthy]

+1 (binding)

Missed ambari-dev@ in prev. response.

Arun

On Sep 4, 2013, at 10:39 AM, Sumit Mohanty smoha...@hortonworks.com wrote:

 Hi all,
 
 ambari-1.2.5-incubating-rc0 release candidate is now available.
 
 Here's a summary of what's new in Ambari 1.2.5:
 * Added support to setup Ganglia and Nagios HTTPS
 * Added support to run Ambari Server as non-root account.
 * Added ability to manage Kerberos Secure Cluster.
 * Added support to setup Ambari Server HTTPS.
 * Enabled Ambari Server configuration property encryption.
 * Added support to configure Ambari Server-Agent Two-Way SSL Communication.
 * Added ability to customize Dashboard Widgets.
 * Improved Host Checks during Install Wizard
 
 I have successfully deployed a 3-node cluster on RHEL 6.3 using the
 instructions available at:
 http://incubator.apache.org/ambari/1.2.5/installing-hadoop-using-ambari/cont
 ent/index.html
 
 Git source tag:
 https://git-wip-us.apache.org/repos/asf/incubator-ambari/repo?p=incubator-am
 bari.git;a=log;h=refs/tags/release-1.2.5-rc0
 
 Staging site:
 http://people.apache.org/~smohanty/ambari-release-1.2.5-rc0/
 
 PGP release keys (signed using 791FDAB0)
 http://pgp.mit.edu:11371/pks/lookup?op=vindexsearch=0xECFC8276791FDAB0
 
 One can look into the issues fixed in this release at:
 https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMBARI%20AND%20fi
 xVersion%20%3D%20%221.2.5%22%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20
 priority%20DESC
 
 Vote will be open for 72 hours.
 
 [ ] +1 approve
 [ ] +0 no opinion
 [ ] -1 disapprove (and reason why)
 
 Here's my vote to start: +1 (binding)
 
 Sumit
 
 
 
 -- 
 CONFIDENTIALITY NOTICE
 NOTICE: This message is intended for the use of the individual or entity to 
 which it is addressed and may contain information that is confidential, 
 privileged and exempt from disclosure under applicable law. If the reader 
 of this message is not the intended recipient, you are hereby notified that 
 any printing, copying, dissemination, distribution, disclosure or 
 forwarding of this communication is strictly prohibited. If you have 
 received this communication in error, please contact the sender immediately 
 and delete it from your system. Thank You.

--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/



-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Re: [VOTE] Apache Ambari 1.2.5-incubating RC1

[Arun C Murthy]

+1 (binding)

Arun

On Sep 4, 2013, at 10:39 AM, Sumit Mohanty smoha...@hortonworks.com wrote:

 Hi all,
 
 ambari-1.2.5-incubating-rc0 release candidate is now available.
 
 Here's a summary of what's new in Ambari 1.2.5:
 * Added support to setup Ganglia and Nagios HTTPS
 * Added support to run Ambari Server as non-root account.
 * Added ability to manage Kerberos Secure Cluster.
 * Added support to setup Ambari Server HTTPS.
 * Enabled Ambari Server configuration property encryption.
 * Added support to configure Ambari Server-Agent Two-Way SSL Communication.
 * Added ability to customize Dashboard Widgets.
 * Improved Host Checks during Install Wizard
 
 I have successfully deployed a 3-node cluster on RHEL 6.3 using the
 instructions available at:
 http://incubator.apache.org/ambari/1.2.5/installing-hadoop-using-ambari/cont
 ent/index.html
 
 Git source tag:
 https://git-wip-us.apache.org/repos/asf/incubator-ambari/repo?p=incubator-am
 bari.git;a=log;h=refs/tags/release-1.2.5-rc0
 
 Staging site:
 http://people.apache.org/~smohanty/ambari-release-1.2.5-rc0/
 
 PGP release keys (signed using 791FDAB0)
 http://pgp.mit.edu:11371/pks/lookup?op=vindexsearch=0xECFC8276791FDAB0
 
 One can look into the issues fixed in this release at:
 https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMBARI%20AND%20fi
 xVersion%20%3D%20%221.2.5%22%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20
 priority%20DESC
 
 Vote will be open for 72 hours.
 
 [ ] +1 approve
 [ ] +0 no opinion
 [ ] -1 disapprove (and reason why)
 
 Here's my vote to start: +1 (binding)
 
 Sumit
 
 
 
 -- 
 CONFIDENTIALITY NOTICE
 NOTICE: This message is intended for the use of the individual or entity to 
 which it is addressed and may contain information that is confidential, 
 privileged and exempt from disclosure under applicable law. If the reader 
 of this message is not the intended recipient, you are hereby notified that 
 any printing, copying, dissemination, distribution, disclosure or 
 forwarding of this communication is strictly prohibited. If you have 
 received this communication in error, please contact the sender immediately 
 and delete it from your system. Thank You.

--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/



-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Re: [VOTE] Release of Apache Falcon (incubating) v0.3

[Arun C Murthy]

+1 (binding)

Arun

On Aug 11, 2013, at 11:39 PM, Srikanth Sundarrajan srik...@hotmail.com wrote:

 Hello,
 This is a call for a vote on Apache Falcon 0.3 incubating. This is our first 
 release.
 
 A vote was held on developer mailing list and it
 passed with 7 +1's.
 
 VOTE: 
 http://mail-archives.apache.org/mod_mbox/falcon-dev/201308.mbox/%3CBLU167-W17AB8E710B264BF39C06C0A45E0%40phx.gbl%3E
 RESULT: 
 http://mail-archives.apache.org/mod_mbox/incubator-falcon-dev/201308.mbox/BLU167-W2D47F8F380BB099FC409FA45B0%40phx.gbl
  
 
 Source tar ball is available at
 http://people.apache.org/~sriksun/falcon-release/0.3-rc4
 
 The release has been signed through key(D2498DC9):
 http://pgp.mit.edu:11371/pks/lookup?op=vindexsearch=0x90814E84D2498DC9
 
 Source corresponding to this release can be found at
 https://git-wip-us.apache.org/repos/asf?p=incubator-falcon.git;a=tag;h=refs/tags/v0.3-rc4
 
 Checksums:
 MD5(falcon-0.3-incubating-sources.tar.gz)= 92bedce87ce2f3959156f9c050638ada
 SHA1(falcon-0.3-incubating-sources.tar.gz)= 
 0acfb200c2bfa60142a163a43f5deeab23ee149c
 
 List of issues closed in this release is available at 
 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314429version=12324423
 
 Vote will be open for 72 hours and close at 15/Aug/2013 12PM IST.
 
 [ ] +1 approve
 [ ] +0 no opinion
 [ ] -1 disapprove (and reason why)
 
 Thanks  Regards
 Srikanth Sundarrajan
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 

--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/



-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Re: [VOTE] Apache Ambari 1.2.3-incubating RC1

[Arun C Murthy]

+1 (binding)

Verified bits and check license etc.

Arun

On May 29, 2013, at 7:09 PM, Yusaku Sako wrote:

 Hi all,
 
 ambari-1.2.3-incubating-rc1 release candidate is now available.
 
 Here's a summary of Ambari 1.2.3 features:
 * Improved stability
 * Ability to update core-site.xml properties post-install
 * Ability to add and remove custom configuration properties
 * New Heatmaps (Host  CPU WIO %, HBase  RegionServer
 Reads/Writes/Regions/QueueSize/MemstoreSize)
 * Ability to add host components on existing hosts
 * Filter hosts by host health status
 * Mixed OS support
 * init.d scripts
 * Support for Oracle Enterprise Linux 5 and 6
 
 I have successfully deployed a 5-node cluster on RHEL 6.3 using the
 instructions available at:
 http://incubator.apache.org/ambari/1.2.3/installing-hadoop-using-ambari/content/index.html
 
 SVN source tag:
 https://svn.apache.org/repos/asf/incubator/ambari/tags/release-1.2.3-rc1
 
 Staging site:
 http://people.apache.org/~yusaku/ambari-1.2.3-incubating-rc1
 
 PGP release keys (signed using 3ABE18B3)
 http://pgp.mit.edu:11371/pks/lookup?op=vindexsearch=0x4C3AA2723ABE18B3
 
 One can look into the issues fixed in this release at:
 https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMBARI%20AND%20fixVersion%20%3D%20%221.2.3%22%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20priority%20DESC
 
 Vote will be open for 72 hours.
 
 [ ] +1 approve
 [ ] +0 no opinion
 [ ] -1 disapprove (and reason why)
 
 
 Here's my vote to start: +1 (binding)
 
 Yusaku

--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/

Re: [VOTE] Apache Ambari 1.2.2-incubating RC1

[Arun C Murthy]

+1 (binding)

Arun

On Apr 9, 2013, at 12:28 AM, Yusaku Sako wrote:

 Hi all,
 
 I have created the ambari-1.2.2-incubating-rc1 release candidate.
 
 I have run the rat tool and successfully deployed a 5-node cluster on RHEL
 6.3 using the instructions available at:
 http://incubator.apache.org/ambari/1.2.2/installing-hadoop-using-ambari/content/index.html
 
 Critical fixes made since ambari-1.2.2-rc0 are:
 https://issues.apache.org/jira/browse/AMBARI-1748: JDK option on the UI
 when used is not passed onto the global parameters
 https://issues.apache.org/jira/browse/AMBARI-1794: Add Host install retry
 shuts down all services in the cluster
 https://issues.apache.org/jira/browse/AMBARI-1795: Add Hosts - retrying
 install shows all progress bars in red and causes the wizard to get stuck
 on the progress page
 https://issues.apache.org/jira/browse/AMBARI-1815; After modifying custom
 configs, properties are shown as blank, leading to corrupt core-site.xml
 upon save
 
 SVN source tag:
 https://svn.apache.org/repos/asf/incubator/ambari/tags/release-1.2.2-rc1
 
 Staging site:
 http://people.apache.org/~yusaku/ambari-1.2.2-incubating-rc1
 
 PGP release keys (signed using 3ABE18B3)
 http://pgp.mit.edu:11371/pks/lookup?op=vindexsearch=0x4C3AA2723ABE18B3
 
 One can look into the issues fixed in this release at:
 https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMBARI%20AND%20fixVersion%20%3D%20%221.2.2%22%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20priority%20DESC
 
 Vote will be open for 72 hours.
 
 [ ] +1 approve
 [ ] +0 no opinion
 [ ] -1 disapprove (and reason why)
 
 
 Here's my vote to start: +1 (binding)
 
 Yusaku

--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/

Re: [VOTE] Apache Ambari (incubating) 1.2.1 Release Candidate RC1.

[Arun C Murthy]

+1 (binding)

Arun

On Mar 13, 2013, at 11:37 PM, Mahadev Konar wrote:

 Thanks to feedback from general@incubator we have updated the release
 artifacts with the following fixes:
 
  1. Fixed NOTICE.txt
  2. Fixed KEYS file.
  3. Removed pyc files in my svn tree (unfortunately ran mvn test
 before building last time).
  4. mvn apache-rat:check passes. The exclude files are files that
 cannot have Apache Headers since it breaks the run time.
  5. Website has been updated (http://incubator.apache.org/ambari/ to
 fix all the issues mentioned earlier - thanks to Yusaku).
  6. Release artifacts now use md5 and sha1.
 
 The staging Staging site is:
 http://people.apache.org/~mahadev/ambari-1.2.1-incubating-rc1/
 
 with user docs at:
 http://incubator.apache.org/ambari/1.2.1/installing-hadoop-using-ambari/content/index.html
 and dev docs at:
 https://cwiki.apache.org/confluence/display/AMBARI/Ambari+Development
 
 SVN source tag:
 https://svn.apache.org/repos/asf/incubator/ambari/tags/release-1.2.1-rc1
 
 PGP release keys (signed using 8EE2F25C)
 http://pgp.mit.edu:11371/pks/lookup?op=vindexsearch=0x0DFF492D8EE2F25C
 
 One can look into the issues fixed in this release at
 
 https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMBARI%20AND%20fixVersion%20%3D%20%221.2.1%22%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20priority%20DESC
 
 Vote will be open for 72 hours.
 [ ] +1 approve
 [ ] +0 no opinion
 [ ] -1 disapprove (and reason why)
 
 thanks
 mahadev
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 

--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/

Re: [PROPOSAL] Ivory - Hadoop data management and processing platform

[Arun C Murthy]

 developers. All the engineers have built
 two generations of Data Management on Hadoop, having deep expertise in
 Hadoop
 and are quite familiar with the Hadoop Ecosystem.
 
 === Alignment ===
 The ASF is a natural host for Ivory given that it is already the home of
 Hadoop,
 Pig, Knox, HCatalog, and other emerging “big data” software projects. Ivory
 has
 been designed to solve the data management challenges and opportunities of
 the
 Hadoop ecosystem family of products. Ivory fills the gap that Hadoop
 ecosystem
 has been lacking in the areas of data processing and data lifecycle
 management.
 
 == Known Risks ==
 
 === Orphaned products  Reliance on Salaried Developers ===
 The core developers plan to work full time on the project. There is very
 little
 risk of Ivory getting orphaned. Ivory is in use by companies we work for so
 the
 companies have an interest in its continued vitality.
 
 === Inexperience with Open Source ===
 All of the core developers are active users and followers of open source.
 Srikanth Sundarrajan has been contributing patches to Apache Hadoop and
 Apache
 Oozie, Shwetha GS has been contributing patches to Apache Oozie.
 Seetharam Venkatesh is a committer on Apache Knox. Rohini Palaniswamy is a
 committer on Apache PIG. Sharad Agarwal, Amareshwari SR (also a Apache Hive
 PMC member) and Sanjay Radia are PMC members on Apache Hadoop.
 
 === Homogeneous Developers ===
 The current core developers are from diverse set of organizations such as
 InMobi, Hortonworks, and, Yahoo!. We expect to quickly establish a
 developer
 community that includes contributors from several corporations post
 incubation.
 
 === Reliance on Salaried Developers ===
 Currently, most developers are paid to do work on Ivory but few are
 contributing
 in their spare time. However, once the project has a community built around
 it
 post incubation, we expect to get committers and developers from outside
 the
 current core developers.
 
 === Relationships with Other Apache Products ===
 Ivory is going to be used by the users of Hadoop and the Hadoop ecosystem
 in
 general.
 
 === A Excessive Fascination with the Apache Brand ===
 While we respect the reputation of the Apache brand and have no doubts that
 it
 will attract contributors and users, our interest is primarily to give
 Ivory a
 solid home as an open source project following an established development
 model.
 We have also given reasons in the Rationale and Alignment sections.
 
 == Documentation ==
 There is documentation in github repository at:
 https://github.com/sriksun/Ivory
 
 == Initial Source ==
 The source is currently in github repository at:
 https://github.com/sriksun/Ivory
 
 == Source and Intellectual Property Submission Plan ==
 The complete Ivory code is under Apache Software License 2.
 
 == External Dependencies ==
 The dependencies all have Apache compatible licenses. These include BSD,
 MIT licensed dependencies.
 
 == Cryptography ==
 None
 
 == Required Resources ==
 
 === Mailing lists ===
 
 * ivory-dev AT incubator DOT apache DOT org
 * ivory-commits AT incubator DOT apache DOT org
 * ivory-user AT incubator apache DOT org
 * ivory-private AT incubator DOT apache DOT org
 
 === Subversion Directory ===
 https://svn.apache.org/repos/asf/incubator/ivory
 
 === Issue Tracking ===
 JIRA IVORY
 
 == Initial Committers ==
 * Srikanth Sundarrajan (Srikanth.Sundarrajan AT inmobi DOT com)
 * Shwetha GS (shwetha.gs AT inmobi DOT com)
 * Shaik Idris (shaik.idris AT inmobi DOT com)
 * Venkatesh Seetharam (Venkatesh AT apache DOT com)
 * Rohini Palaniswamy (rohinip AT yahoo-inc DOT com)
 * Thiruvel Thirumoolan (thiruvel AT yahoo-inc DOT com)
 * Sanjay Radia (sanjay AT apache DOT org)
 * Sharad Agarwal (sharad AT apache DOT org)
 * Amareshwari SR (amareshwari AT apache DOT org)
 
 == Affiliations ==
 * Srikanth Sundarrajan (InMobi)
 * Shwetha GS (InMobi)
 * Shaik Idris (InMobi)
 * Venkatesh Seetharam (Hortonworks Inc)
 * Rohini Palaniswamy (Yahoo! Inc)
 * Thiruvel Thirumoolan (Yahoo! Inc)
 * Sanjay Radia (Hortonworks Inc)
 * Sharad Agarwal (InMobi)
 * Amareshwari SR (InMobi)
 
 == Sponsors ==
 
 === Champion ===
 * Arun C Murthy (acmurthy at apache dot org)
 
 === Nominated Mentors ===
 * Alan Gates (gates AT apache DOT org)
 * Chris Douglas (cdouglas AT apache DOT org)
 * Devaraj  Das (ddas AT apache DOT org)
 * Owen O’Malley (omalley AT apache DOT org)
 
 === Sponsoring Entity ===
 Incubator PMC
 
 -- 
 _
 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

Re: [VOTE] Accept Tez into Incubator

[Arun C Murthy]

Thanks to all who voted. Obviously, I'm +1 (binding) on the proposal.

With 14 +1s (10 binding) the vote passes.

I'll start the work to get the podling started.

thanks,
Arun

On Feb 19, 2013, at 8:26 PM, Arun C Murthy wrote:

 Hi Folks,
 
 Thanks for participating in the discussion. I'd like to call a VOTE for 
 acceptance of Apache Tez into the Incubator. I'll let the vote run till into 
 this weekend (Sun 2/24 6pm PST).
 
 [ ]  +1 Accept Apache Tez into the Incubator
 [ ]  +0 Don't care.
 [ ]  -1 Don't accept Apache Tez into the Incubator because...
 
 Full proposal is pasted at the bottom of this email, and the corresponding 
 wiki is http://wiki.apache.org/incubator/TezProposal. 
 
 Only VOTEs from Incubator PMC members are binding, but all are welcome to 
 express their thoughts.
 
 Here's my +1 (binding).
 
 thanks,
 Arun
 
 PS: From the initial discussion, the only changes are that I've added one new 
 mentor and 2 new committers. All the new additions come from the non-major 
 employer while we continue to strive to further diversify during the 
 incubation. Thanks.
 
 
 
 = Tez =
 
 == Abstract ==
 Tez is an effort to develop a generic application framework which can be used
 to process arbitrarily complex data-processing tasks and also a re-usable set
 of data-processing primitives which can be used by other projects.
 
 == Proposal ==
 Tez is a proposal to develop a generic application which can be used to
 process complex data-processing task DAGs and runs natively on Apache Hadoop 
 YARN. YARN is a generic resource-management system on which currently 
 applications like MapReduce already exist. MapReduce is a specific, and
 constrained, DAG - which is not optimal for several frameworks like Apache 
 Hive
 and Apache Pig. Furthermore, we propose to develop a re-usable set of
 libraries of data-processing primitives such as sorting, merging,
 data-shuffling, intermediate data management etc. which are necessary for Tez 
 which we envision can be used directly by other projects. 
 
 == Background ==
 Apache Hadoop MapReduce has emerged as the assembly-language on which other
 frameworks like Apache Pig and Apache Hive have been built. However, it has
 been well accepted that MapReduce produces very constrained task DAGs for each
 job which results in Apache Pig and Apache Hive requiring multiple MapReduce
 jobs for several queries. By providing a more expressive DAG of tasks for a
 job, Tez attempts to provide significantly enhanced data-processing
 capabilities for projects like Apache Pig, Apache Hive, Cascading etc.
 
 == Rationale ==
 There is an important gap that Tez fulfills in the Apache Hadoop ecosystem of
 allowing for more expressive task DAGs for data-processing applications such
 as Apache Pig, Apache Hive, Cascading etc.
 
 With emergence of Apache Hadoop YARN, there is a strong need for a
 common DAG application which can then be shared by Apache Pig, Apache Hive,
 Cascading etc.
 
 == Initial Goals ==
 The initial goals for this project are to specify the detailed requirements
 and architecture, and then develop the initial implementation including the
 DAG ApplicationMaster to run natively inside Apache Hadoop YARN. 
 
 == Current Status ==
 Significant work has been completed to identify the initial requirements and
 define the overall system architecture. There is a patch available in the
 internal Hortonworks git repository which can act as the initial seed. 
 
 === Meritocracy ===
 We plan to invest in supporting a meritocracy. We will discuss the 
 requirements 
 in an open forum. Several companies have already expressed interest in this 
 project, and we intend to invite additional developers to participate. 
 We will encourage and monitor community participation so that privileges can 
 be 
 extended to those that contribute. 
 
 === Community ===
 The need for a generic DAG application for data processing in the open source 
 is 
 tremendous, so there is a potential for a very large community. We believe
 that Tez's extensible architecture will further encourage community 
 participation. 
 Also, related Apache projects (eg, Pig, Hive) have very large and active 
 communities, and we expect that over time Tez will also attract a large 
 community.
 
 === Core Developers ===
 The developers on the initial committers list include people very experienced
 in the Apache Hadoop ecosystem:
 
  * Alan Gates gates at apache dot org
  * Arun C Murthy acmurthy at apache dot org
  * Ashutosh Chauhan hashutosh at apache dot org
  * Bikas Saha bikas at apache dot org
  * Chris Douglas cdouglas at apache dot org
  * Daryn Sharp daryn at apache dot org
  * Devaraj Das ddas at apache dot org
  * Gopal Vijayaraghavan gopal at hortonworks dot com
  * Gunther Hagleitner ghagleitner at hortonworks dot com
  * Hitesh Shah hitesh at apache dot org
  * Jason Lowe jlowe at apache dot org
  * Jean Xu jeanxu at facebook dot com
  * Jitendra Pandey jitendra at apache dot org
  * Julien Le

Re: [VOTE] Accept Tez into Incubator

[Arun C Murthy]

On Feb 20, 2013, at 1:38 PM, Andrew Purtell wrote:

 Arun, would you please clarify how Tez is (conceptually) different from
 the Workflow AM proposed in MAPREDUCE-4495/OOZIE-1178?
 
 I would also like to understand this as well. They seem largely identical,
 but the Tez proposal has a set of initial committers disjunctive from those
 who performed the work on MAPREDUCE-4495/OOZIE-1178 and volunteered for the
 so-called YAPP proposal.
 

Sorry, I thought I answered this when I talked about scope of Tez being similar 
to Hyracks or Stratosphere when I responded to Sebastian 
(http://s.apache.org/x4u).

IAC, Tez is an attempt to build a _single job_ which can run a DAG of tasks 
(ala Hyracks/Stratosphere) where-as yapp was about having an application to 
manage a DAG of independent jobs to construct a more complex workflow for 
Oozie. Each is significantly different to the other in scope and goals.

Hope that helps.

thanks,
Arun

PS: I'm happy to help bring yapp in as another podling, but I haven't heard 
back from Alejandro and other original authors of what we talked about as yapp. 
If you could comment on the jira, I'll take it fwd - I'm still interested in 
working on yapp independent of Tez - this is one of the strengths of YARN. Tx!

 
 On Wed, Feb 20, 2013 at 8:26 AM, Alejandro Abdelnur t...@cloudera.comwrote:
 
 +1 (non-binding), glad to see that finally the idea of having a DAG AM is
 getting traction.
 
 Arun, would you please clarify how Tez is (conceptually) different from the
 Workflow AM proposed in MAPREDUCE-4495/OOZIE-1178?
 
 
 
 On Wed, Feb 20, 2013 at 6:50 AM, Hitesh Shah hit...@hortonworks.com
 wrote:
 
 +1 ( non-binding )
 
 -- Hitesh
 
 On Feb 19, 2013, at 8:26 PM, Arun C Murthy wrote:
 
 Hi Folks,
 
 Thanks for participating in the discussion. I'd like to call a VOTE for
 acceptance of Apache Tez into the Incubator. I'll let the vote run till
 into this weekend (Sun 2/24 6pm PST).
 
 [ ]  +1 Accept Apache Tez into the Incubator
 [ ]  +0 Don't care.
 [ ]  -1 Don't accept Apache Tez into the Incubator because...
 
 Full proposal is pasted at the bottom of this email, and the
 corresponding wiki is http://wiki.apache.org/incubator/TezProposal.
 
 Only VOTEs from Incubator PMC members are binding, but all are welcome
 to express their thoughts.
 
 Here's my +1 (binding).
 
 thanks,
 Arun
 
 PS: From the initial discussion, the only changes are that I've added
 one new mentor and 2 new committers. All the new additions come from the
 non-major employer while we continue to strive to further diversify
 during
 the incubation. Thanks.
 
 
 
 = Tez =
 
 == Abstract ==
 Tez is an effort to develop a generic application framework which can
 be
 used
 to process arbitrarily complex data-processing tasks and also a
 re-usable set
 of data-processing primitives which can be used by other projects.
 
 == Proposal ==
 Tez is a proposal to develop a generic application which can be used to
 process complex data-processing task DAGs and runs natively on Apache
 Hadoop
 YARN. YARN is a generic resource-management system on which currently
 applications like MapReduce already exist. MapReduce is a specific, and
 constrained, DAG - which is not optimal for several frameworks like
 Apache Hive
 and Apache Pig. Furthermore, we propose to develop a re-usable set of
 libraries of data-processing primitives such as sorting, merging,
 data-shuffling, intermediate data management etc. which are necessary
 for Tez
 which we envision can be used directly by other projects.
 
 == Background ==
 Apache Hadoop MapReduce has emerged as the assembly-language on which
 other
 frameworks like Apache Pig and Apache Hive have been built. However, it
 has
 been well accepted that MapReduce produces very constrained task DAGs
 for each
 job which results in Apache Pig and Apache Hive requiring multiple
 MapReduce
 jobs for several queries. By providing a more expressive DAG of tasks
 for a
 job, Tez attempts to provide significantly enhanced data-processing
 capabilities for projects like Apache Pig, Apache Hive, Cascading etc.
 
 == Rationale ==
 There is an important gap that Tez fulfills in the Apache Hadoop
 ecosystem of
 allowing for more expressive task DAGs for data-processing applications
 such
 as Apache Pig, Apache Hive, Cascading etc.
 
 With emergence of Apache Hadoop YARN, there is a strong need for a
 common DAG application which can then be shared by Apache Pig, Apache
 Hive,
 Cascading etc.
 
 == Initial Goals ==
 The initial goals for this project are to specify the detailed
 requirements
 and architecture, and then develop the initial implementation including
 the
 DAG ApplicationMaster to run natively inside Apache Hadoop YARN.
 
 == Current Status ==
 Significant work has been completed to identify the initial
 requirements
 and
 define the overall system architecture. There is a patch available in
 the
 internal Hortonworks git repository which can act as the initial seed.
 
 === Meritocracy

Re: [PROPOSAL] Tez to join Apache Incubator

[Arun C Murthy]

Thanks Sebastian.

The scope includes allowing for a complex DAG within the same 'job' and, as 
such, it generalizes MapReduce to look more like Stratosphere/Hyracks. The goal 
is to help better Hive/Pig/Cascading/Crunch etc.

Hope that helps.

thanks,
Arun

On Feb 19, 2013, at 1:23 AM, Sebastian Schelter wrote:

 Hi,
 
 This proposal looks very interesting to me. What exactly is the scope of
 Tez? Does it aim to be a general data flow system such as
 Stratosphere[1] or Hyracks[2]? Or will it still be executing Map and
 Reduce tasks, that are composable in a more flexible manner?
 
 Best,
 Sebastian
 
 [1] http://dl.acm.org/citation.cfm?id=1807148
 https://www.stratosphere.eu/sites/default/files/papers/NephelePACTs_10.pdf
 
 [2]
 http://dl.acm.org/citation.cfm?id=2005632
 http://asterix.ics.uci.edu/pub/Hyracks.pdf
 
 On 19.02.2013 09:53, Avik Dey wrote:
 The Tez incubator proposal seems to have a lot in common with the work on
 https://issues.apache.org/jira/browse/OOZIE-1178
 
 It is useful to have a workflow application master, which will be capable
 of running a DAG of jobs. The workflow client submits a DAG request to the
 AM and then the AM will manage the life cycle of this application in terms
 of requesting the needed resources from the RM, and starting, monitoring
 and retrying the application's individual tasks.
 
 Compared to running Oozie with the current MapReduce Application Master,
 these are some of the advantages:
 
   - Less number of consumed resources, since only one application master
   will be spawned for the whole workflow.
   - Reuse of resources, since the same resources can be used by multiple
   consecutive jobs in the workflow (no need to request/wait for resources 
 for
   every individual job from the central RM).
   - More optimization opportunities in terms of collective resource
   requests.
   - Optimization opportunities in terms of rewriting and composing jobs
   in the workflow (e.g. pushing down Mappers).
   - This Application Master can be reused/extended by higher systems
   like Pig and hive to provide an optimized way of running their workflows.
 
 So, is this the 'yapp' proposal that was discussed on that thread?
 
 ~avik
 
 
 On Mon, Feb 18, 2013 at 9:40 PM, Ted Dunning ted.dunn...@gmail.com wrote:
 
 This seems like a reasonable project (basically it is the long fabled
 map-reduce-reduce or MCR* in google terminology).
 
 But it is *very* heavy with Hortonworks developers.  By my count, the
 proportion is over half from HW with only token representation from other
 companies:
 
  13 Hortonworks
   4 Yahoo
   3 Facebook
   2 Microsoft
   1 Cloudera
 
 Shouldn't this be a bit broader to start with?  Or is that an incubation
 task?
 
 On Mon, Feb 18, 2013 at 9:29 PM, Arun C Murthy a...@hortonworks.com
 wrote:
 
 Folks,
 
 I'd like to propose adding Tez to the Apache Incubator:
 http://wiki.apache.org/incubator/TezProposal
 
 Essentially, it's the next step to improve projects in the Apache Hadoop
 ecosystem such as Apache Hive, Apache Pig, Cascading (ASL2, but not ASF
 project) by providing a more complex DAG of 'tasks' in a single
 application
 to process data, there-by providing significant advantages for them.
 
 During the time I've spent working on MapReduce, I've forever heard
 complaints from Pig/Hive folks about the fact that MapReduce provides a
 very constrained task graph which results in excessive number of
 MapReduce
 jobs... *smile*. It's very exciting to take this next step, and I would
 be
 thrilled to have it happen in the ASF - as you can see in the proposal
 this
 effort has broad support from members of MapReduce, Hive  Pig
 communities,
 many of whom are eager to participate and have already contributed their
 efforts during the initial prototype.
 
 I welcome your feedback/discussion and look forward to it!
 
 thanks,
 Arun
 (proposed Champion)
 
 
 
 = Tez =
 
 == Abstract ==
 Tez is an effort to develop a generic application framework which can be
 used
 to process arbitrarily complex data-processing tasks and also a re-usable
 set
 of data-processing primitives which can be used by other projects.
 
 == Proposal ==
 Tez is a proposal to develop a generic application which can be used to
 process complex data-processing task DAGs and runs natively on Apache
 Hadoop
 YARN. YARN is a generic resource-management system on which currently
 applications like MapReduce already exist. MapReduce is a specific, and
 constrained, DAG - which is not optimal for several frameworks like
 Apache
 Hive
 and Apache Pig. Furthermore, we propose to develop a re-usable set of
 libraries of data-processing primitives such as sorting, merging,
 data-shuffling, intermediate data management etc. which are necessary for
 Tez
 which we envision can be used directly by other projects.
 
 == Background ==
 Apache Hadoop MapReduce has emerged as the assembly-language on which
 other
 frameworks like Apache Pig and Apache Hive have been built. However, it
 has

Re: Wiki privs

[Arun C Murthy]

Help, please?

I got one of my other mentors to put up the wiki, but would be nice to get 
write access as well.

thanks!
Arun

On Feb 18, 2013, at 3:05 PM, Arun C Murthy wrote:

 Hi Folks,
 
 Can someone pls grant me privs so that I can put up a new Incubator proposal 
 on the wiki (http://wiki.apache.org/incubator/TezProposal) ? My wiki username 
 is 'Arun C Murthy'.
 
 thanks,
 Arun
 

Re: [VOTE] Accept Apache Knox Hadoop Gateway Project into the Incubator

[Arun C Murthy]

 knox-user AT hms incubator apache DOT org knox-private
 AT incubator DOT apache DOT org
 
 Subversion Directory
 
 https://svn.apache.org/repos/asf/incubator/knox
 
 Issue Tracking
 
 JIRA Knox (KNOX)
 
 Initial Committers
 
 Kevin Minder (kevin DOT minder AT hortonworks DOT com)
 
 Larry McCay (lmccay AT hortonworks DOT com)
 
 John Speidel (jspeidel AT hortonworks DOT com)
 Tom Beerbower (tbeerbower AT hortonworks DOT com)
 Sumit Mohanty (smohanty AT hortonworks DOT com)
 Venkatesh Seetharam (venkatesh AT hortonworks DOT com)
 
 Affiliations
 
 Kevin Minder (Hortonworks)
 
 Larry McCay (Hortonworks)
 
 John Speidel (Hortonworks)
 Tom Beerbower (Hortonworks)
 Sumit Mohanty (Hortonworks)
 Venkatesh Seetharm (Hortonworks)
 Owen O'Malley (Hortonworks)
 Mahadev Konar (Hortonworks)
 Alan Gates (Hortonworks)
 Devaraj Das (Hortwonrks)
 Chris Douglas (Microsoft)
 Chris Mattmann (NASA)
 Tom White (Cloudera)
 
 Sponsors
 
 Champion
 
 Devaraj Das (ddas AT apache DOT org)
 
 Nominated Mentors
 
 Owen O’Malley (omalley AT apache DOT org)
 Mahadev Konar (mahadev AT apache DOT org)
 Alan Gates (gates AT apache DOT org)
 Devaraj Das (ddas AT apache DOT org)
 Chris Douglas (cdouglas AT apache DOT org)
 Chris Mattmann (chris DOT a DOT mattmann AT jpl DOT nasa DOT gov)
 Tom White (tom DOT e DOT white AT gmail DOT com)
 
 Sponsoring Entity
 
 Incubator PMC
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 

--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/

[VOTE] Accept Tez into Incubator

[Arun C Murthy]

Hi Folks,

Thanks for participating in the discussion. I'd like to call a VOTE for 
acceptance of Apache Tez into the Incubator. I'll let the vote run till into 
this weekend (Sun 2/24 6pm PST).

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

Full proposal is pasted at the bottom of this email, and the corresponding wiki 
is http://wiki.apache.org/incubator/TezProposal. 

Only VOTEs from Incubator PMC members are binding, but all are welcome to 
express their thoughts.

Here's my +1 (binding).

thanks,
Arun

PS: From the initial discussion, the only changes are that I've added one new 
mentor and 2 new committers. All the new additions come from the non-major 
employer while we continue to strive to further diversify during the 
incubation. Thanks.



= Tez =

== Abstract ==
Tez is an effort to develop a generic application framework which can be used
to process arbitrarily complex data-processing tasks and also a re-usable set
of data-processing primitives which can be used by other projects.

== Proposal ==
Tez is a proposal to develop a generic application which can be used to
process complex data-processing task DAGs and runs natively on Apache Hadoop 
YARN. YARN is a generic resource-management system on which currently 
applications like MapReduce already exist. MapReduce is a specific, and
constrained, DAG - which is not optimal for several frameworks like Apache Hive
and Apache Pig. Furthermore, we propose to develop a re-usable set of
libraries of data-processing primitives such as sorting, merging,
data-shuffling, intermediate data management etc. which are necessary for Tez 
which we envision can be used directly by other projects. 

== Background ==
Apache Hadoop MapReduce has emerged as the assembly-language on which other
frameworks like Apache Pig and Apache Hive have been built. However, it has
been well accepted that MapReduce produces very constrained task DAGs for each
job which results in Apache Pig and Apache Hive requiring multiple MapReduce
jobs for several queries. By providing a more expressive DAG of tasks for a
job, Tez attempts to provide significantly enhanced data-processing
capabilities for projects like Apache Pig, Apache Hive, Cascading etc.

== Rationale ==
There is an important gap that Tez fulfills in the Apache Hadoop ecosystem of
allowing for more expressive task DAGs for data-processing applications such
as Apache Pig, Apache Hive, Cascading etc.

With emergence of Apache Hadoop YARN, there is a strong need for a
common DAG application which can then be shared by Apache Pig, Apache Hive,
Cascading etc.

== Initial Goals ==
The initial goals for this project are to specify the detailed requirements
and architecture, and then develop the initial implementation including the
DAG ApplicationMaster to run natively inside Apache Hadoop YARN. 

== Current Status ==
Significant work has been completed to identify the initial requirements and
define the overall system architecture. There is a patch available in the
internal Hortonworks git repository which can act as the initial seed. 

=== Meritocracy ===
We plan to invest in supporting a meritocracy. We will discuss the requirements 
in an open forum. Several companies have already expressed interest in this 
project, and we intend to invite additional developers to participate. 
We will encourage and monitor community participation so that privileges can be 
extended to those that contribute. 

=== Community ===
The need for a generic DAG application for data processing in the open source 
is 
tremendous, so there is a potential for a very large community. We believe
that Tez's extensible architecture will further encourage community 
participation. 
Also, related Apache projects (eg, Pig, Hive) have very large and active 
communities, and we expect that over time Tez will also attract a large 
community.

=== Core Developers ===
The developers on the initial committers list include people very experienced
in the Apache Hadoop ecosystem:

 * Alan Gates gates at apache dot org
 * Arun C Murthy acmurthy at apache dot org
 * Ashutosh Chauhan hashutosh at apache dot org
 * Bikas Saha bikas at apache dot org
 * Chris Douglas cdouglas at apache dot org
 * Daryn Sharp daryn at apache dot org
 * Devaraj Das ddas at apache dot org
 * Gopal Vijayaraghavan gopal at hortonworks dot com
 * Gunther Hagleitner ghagleitner at hortonworks dot com
 * Hitesh Shah hitesh at apache dot org
 * Jason Lowe jlowe at apache dot org
 * Jean Xu jeanxu at facebook dot com
 * Jitendra Pandey jitendra at apache dot org
 * Julien Le Dem julien at apache dot org
 * Kevin Wilfong kevinwilfong at apache dot org
 * Mike Liddell mike dot lidell at microsoft dot com
 * Namit Jain namit at apache dot org
 * Nathan Roberts nroberts at yahoo dash inc dot com
 * Owen O'Malley omalley at apache dot org
 * Robert Evans bobby at apache dot org
 * Siddharth Seth sseth at apache dot

Wiki privs

[Arun C Murthy]

Hi Folks,

Can someone pls grant me privs so that I can put up a new Incubator proposal on 
the wiki (http://wiki.apache.org/incubator/TezProposal) ? My wiki username is 
'Arun C Murthy'.

thanks,
Arun

[PROPOSAL] Tez to join Apache Incubator

[Arun C Murthy]

Folks,

 I'd like to propose adding Tez to the Apache Incubator: 
http://wiki.apache.org/incubator/TezProposal
 
 Essentially, it's the next step to improve projects in the Apache Hadoop 
ecosystem such as Apache Hive, Apache Pig, Cascading (ASL2, but not ASF 
project) by providing a more complex DAG of 'tasks' in a single application to 
process data, there-by providing significant advantages for them. 

 During the time I've spent working on MapReduce, I've forever heard complaints 
from Pig/Hive folks about the fact that MapReduce provides a very constrained 
task graph which results in excessive number of MapReduce jobs... *smile*. It's 
very exciting to take this next step, and I would be thrilled to have it happen 
in the ASF - as you can see in the proposal this effort has broad support from 
members of MapReduce, Hive  Pig communities, many of whom are eager to 
participate and have already contributed their efforts during the initial 
prototype.

 I welcome your feedback/discussion and look forward to it!

thanks,
Arun 
(proposed Champion)



= Tez =

== Abstract ==
Tez is an effort to develop a generic application framework which can be used
to process arbitrarily complex data-processing tasks and also a re-usable set
of data-processing primitives which can be used by other projects.

== Proposal ==
Tez is a proposal to develop a generic application which can be used to
process complex data-processing task DAGs and runs natively on Apache Hadoop 
YARN. YARN is a generic resource-management system on which currently 
applications like MapReduce already exist. MapReduce is a specific, and
constrained, DAG - which is not optimal for several frameworks like Apache Hive
and Apache Pig. Furthermore, we propose to develop a re-usable set of
libraries of data-processing primitives such as sorting, merging,
data-shuffling, intermediate data management etc. which are necessary for Tez 
which we envision can be used directly by other projects. 

== Background ==
Apache Hadoop MapReduce has emerged as the assembly-language on which other
frameworks like Apache Pig and Apache Hive have been built. However, it has
been well accepted that MapReduce produces very constrained task DAGs for each
job which results in Apache Pig and Apache Hive requiring multiple MapReduce
jobs for several queries. By providing a more expressive DAG of tasks for a
job, Tez attempts to provide significantly enhanced data-processing
capabilities for projects like Apache Pig, Apache Hive, Cascading etc.

== Rationale ==
There is an important gap that Tez fulfills in the Apache Hadoop ecosystem of
allowing for more expressive task DAGs for data-processing applications such
as Apache Pig, Apache Hive, Cascading etc.

With emergence of Apache Hadoop YARN, there is a strong need for a
common DAG application which can then be shared by Apache Pig, Apache Hive,
Cascading etc.

== Initial Goals ==
The initial goals for this project are to specify the detailed requirements
and architecture, and then develop the initial implementation including the
DAG ApplicationMaster to run natively inside Apache Hadoop YARN. 

== Current Status ==
Significant work has been completed to identify the initial requirements and
define the overall system architecture. There is a patch available in the
internal Hortonworks git repository which can act as the initial seed. 

=== Meritocracy ===
We plan to invest in supporting a meritocracy. We will discuss the requirements 
in an open forum. Several companies have already expressed interest in this 
project, and we intend to invite additional developers to participate. 
We will encourage and monitor community participation so that privileges can be 
extended to those that contribute. 

=== Community ===
The need for a generic DAG application for data processing in the open source 
is 
tremendous, so there is a potential for a very large community. We believe
that Tez's extensible architecture will further encourage community 
participation. 
Also, related Apache projects (eg, Pig, Hive) have very large and active 
communities, and we expect that over time Tez will also attract a large 
community.

=== Core Developers ===
The developers on the initial committers list include people very experienced
in the Apache Hadoop ecosystem:

 * Alan Gates gates at apache dot org
 * Arun C Murthy acmurthy at apache dot org
 * Ashutosh Chauhan hashutosh at apache dot org
 * Bikas Saha bikas at apache dot org
 * Chris Douglas cdouglas at apache dot org
 * Daryn Sharp daryn at apache dot org
 * Devaraj Das ddas at apache dot org
 * Gopal Vijayaraghavan gopal at hortonworks dot com
 * Gunther Hagleitner ghagleitner at hortonworks dot com
 * Hitesh Shah hitesh at apache dot org
 * Jason Lowe jlowe at apache dot org
 * Jean Xu jeanxu at facebook dot com
 * Jitendra Pandey jitendra at apache dot org
 * Kevin Wilfong kevinwilfong at apache dot org
 * Mike Liddell mike dot lidell at microsoft dot com
 * Namit Jain namit at apache

Re: [VOTE] Accept Apache Knox Hadoop Gateway Project into the Incubator

[Arun C Murthy]

 
 Required Resources
 
 Mailing lists
 
 knox-dev AT incubator DOT apache DOT org knox-commits AT incubator DOT
 apache DOT org knox-user AT hms incubator apache DOT org knox-private
 AT incubator DOT apache DOT org
 
 Subversion Directory
 
 https://svn.apache.org/repos/asf/incubator/knox
 
 Issue Tracking
 
 JIRA Knox (KNOX)
 
 Initial Committers
 
 Kevin Minder (kevin DOT minder AT hortonworks DOT com)
 
 Larry McCay (lmccay AT hortonworks DOT com)
 
 John Speidel (jspeidel AT hortonworks DOT com)
 Tom Beerbower (tbeerbower AT hortonworks DOT com)
 Sumit Mohanty (smohanty AT hortonworks DOT com)
 Venkatesh Seetharam (venkatesh AT hortonworks DOT com)
 
 Affiliations
 
 Kevin Minder (Hortonworks)
 
 Larry McCay (Hortonworks)
 
 John Speidel (Hortonworks)
 Tom Beerbower (Hortonworks)
 Sumit Mohanty (Hortonworks)
 Venkatesh Seetharm (Hortonworks)
 Owen O'Malley (Hortonworks)
 Mahadev Konar (Hortonworks)
 Alan Gates (Hortonworks)
 Devaraj Das (Hortwonrks)
 Chris Douglas (Microsoft)
 Chris Mattmann (NASA)
 Tom White (Cloudera)
 
 Sponsors
 
 Champion
 
 Devaraj Das (ddas AT apache DOT org)
 
 Nominated Mentors
 
 Owen O’Malley (omalley AT apache DOT org)
 Mahadev Konar (mahadev AT apache DOT org)
 Alan Gates (gates AT apache DOT org)
 Devaraj Das (ddas AT apache DOT org)
 Chris Douglas (cdouglas AT apache DOT org)
 Chris Mattmann (chris DOT a DOT mattmann AT jpl DOT nasa DOT gov)
 Tom White (tom DOT e DOT white AT gmail DOT com)
 
 Sponsoring Entity
 
 Incubator PMC
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 

--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/

Re: [VOTE] Graduate HCatalog from the incubator and become part of Hive

[Arun C Murthy]

+1 (binding).

Congratulations! And good luck!

Arun

On Feb 6, 2013, at 8:08 PM, Vinod Kumar Vavilapalli wrote:

 +1 non-binding.
 
 Thanks,
 +Vinod
 
 
 On Wed, Feb 6, 2013 at 8:06 PM, Namit Jain nj...@fb.com wrote:
 
 +1
 
 
 On 2/5/13 2:54 PM, Alexander Alten-Lorenz wget.n...@gmail.com wrote:
 
 +1, non-binding
 
 - Alex
 
 On Feb 5, 2013, at 10:06 AM, Sushanth Sowmyan khorg...@gmail.com wrote:
 
 And my axe! Erm... I mean, my +1.
 
 
 On Mon, Feb 4, 2013 at 10:18 PM, Alan Gates ga...@hortonworks.com
 wrote:
 FYI.
 
 Alan.
 
 Begin forwarded message:
 
 From: Alan Gates ga...@hortonworks.com
 Date: February 4, 2013 10:18:09 PM PST
 To: hcatalog-...@incubator.apache.org
 Subject: [VOTE] Graduate HCatalog from the incubator and become part
 of Hive
 
 The Hive PMC has voted to accept HCatalog as a submodule of Hive.
 You can see the vote thread at
 
 http://mail-archives.apache.org/mod_mbox/hive-dev/201301.mbox/%3cCACf6R
 rzktBYD0suZxn3Pfv8XkR=vgwszrzyb_2qvesuj2vh...@mail.gmail.com%3e .  We
 now need to vote to graduate from the incubator and become a submodule
 of Hive.  This entails the following:
 
 1) the establishment of an HCatalog submodule in the Apache Hive
 Project;
 2) the adoption of the Apache HCatalog codebase into the Hive
 HCatalog submodule; and
 3) adding all currently active HCatalog committers as submodule
 committers on the Hive HCatalog submodule.
 
 Definitions for all these can be found in the (now adopted) Hive
 bylaws at
 
 https://cwiki.apache.org/confluence/display/Hive/Proposed+Changes+to+Hi
 ve+Bylaws+for+Submodule+Committer.
 
 This vote will stay open for at least 72 hours (thus 23:00 PST on
 2/7/13).  PPMC members votes are binding in this vote, though input
 from all is welcome.
 
 If this vote passes the next step will be to submit the graduation
 motion to the Incubator PMC.
 
 Here's my +1.
 
 Alan.
 
 
 --
 Alexander Alten-Lorenz
 http://mapredit.blogspot.com
 German Hadoop LinkedIn Group: http://goo.gl/N8pCF
 
 
 
 
 
 -- 
 +Vinod
 Hortonworks Inc.
 http://hortonworks.com/

--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/

Re: Sub-projects - when are they acceptable? (was Re: [VOTE] Graduate Nuvem as a sub-project under Apache Tuscany)

[Arun C Murthy]

Could agree more with Chris and Ross.

I've seen, first hand, at Hadoop the behaviour of significant portions of the 
PMC not being present in one of the 3 sub-projects we have (HDFS, YARN, 
MapReduce) and has led to significant issues in the community and in the PMC.

Along with folks like Chris I've been very vocal about pushing the Hadoop 
project to break up, unfortunately there seem to be little progress to break 
them up. 

So, overall, please be very careful about sub-projects.

Arun

PS: Yes, as the Chair, I've flagged this to the Board.

On Nov 20, 2012, at 6:47 AM, Mattmann, Chris A (388J) wrote:

 Fromt he peanut gallery of someone who has participated in a number of 
 sub-projects
 over the years (Nutch, Tika, Solr, Hadoop, etc.): I don't think they have a 
 big place at the
 ASF. The word project implies community. Sub communities == umbrella 
 projects == 
 pain, and suffering.
 
 OTOH, sub-products, or the ability for a PMC to release multiple 
 products, like e.g., 
 like Lucene does now (Lucene-Java is a product; Solr is a product; PyLucene 
 is a product),
 that works b/c the sets of individuals that make up those interested in the 
 sub products are 
 not separate communities, they just release different portions of the 
 software that they scratch 
 their itch on.
 
 My 2c.
 
 Cheers,
 Chris
 
 On Nov 20, 2012, at 3:28 AM, Ross Gardler wrote:
 
 On 20 November 2012 11:18, Benson Margulies bimargul...@gmail.com wrote:
 On Tue, Nov 20, 2012 at 3:01 AM, Bertrand Delacretaz
 bdelacre...@apache.org wrote:
 On Tue, Nov 20, 2012 at 6:41 AM, Luciano Resende luckbr1...@gmail.com 
 wrote:
 ...Nuvem has a great synergy with Apache Tuscany, and after
 discussion between the two projects, we are seeking IPMC approval to allow
 graduation of Apache Nuvem as a sub-project under Apache Tuscany
 
 Can you clarify what this means? Do all members of the Nuvem PPMC
 become Tuscany PMC members?
 
 Bertrand, this is a great opportunity to clarify the board's attitude
 toward 'subprojects'. Ever since the campaign to dismantle umbrellas,
 I've been confused about what structures the board would find
 reasonable.
 
 I don't speak for the board, but my opinion is that if a sub-project
 is OK as long as it is actively managed by the same PMC as the parent
 project.
 
 Where I start to get worried is when a sub-project takes on a life of
 its own and significant portions of the parent PMC are not interested
 in the sub-project and thus fail to provide appropriate oversight. The
 more sub-projects there are in a project the more likely this is to
 happen.
 
 I'm interested to hear if this is also the opinion of others and thus
 I've changed the subject. In terms of Nuvem I'm interested in the
 answer to Bertrands question.
 
 Ross
 
 -
 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
 

--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/

Re: [VOTE] Apache Crunch (incubating) 0.3.0 Release Candidate 1

[Arun C Murthy]

+1 (binding)

On Sep 11, 2012, at 5:58 AM, Josh Wills wrote:

 Hello everyone,
 
 This is a call for a vote on releasing the following candidate as Apache
 Crunch 0.3.0 (incubating). This will be our first release. A vote was held
 on the developer mailing list and passed with 4 +1s:
 
 http://markmail.org/thread/yvtvog5lrj3a7gep
 
 +1s:
 phunt (IPMC)
 jwills (binding)
 greid (binding)
 mafr (binding)
 
 We need two additional IPMC votes.
 
 The release fixes the issues listed here:
 
 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313526version=12322446
 
 Please download, test, and vote by September 14th at 6AM Pacific Time.
 
 Source files:
 http://people.apache.org/~jwills/crunch-0.3.0-incubating-RC1/
 
 Maven staging repo:
 https://repository.apache.org/content/repositories/orgapachecrunch-040/
 
 The tag to be voted upon:
 https://git-wip-us.apache.org/repos/asf?p=incubator-crunch.git;a=tag;h=4666bd889f9b641d7c0157bc4401a1b985fedc89
 
 Crunch's KEYS file:
 http://www.apache.org/dist/incubator/crunch/KEYS
 
 The vote will be open for 72 hours.
 
 [ ] +1  approve
 [ ] +0  no opinion
 [ ] -1  disapprove (and reason why)
 
 Thank you,
 Josh

--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/

Re: [VOTE] Graduate Oozie podling from Apache Incubator

[Arun C Murthy]

Very cool, good luck!

+1 (binding)

Arun

On Aug 10, 2012, at 4:12 PM, Alejandro Abdelnur wrote:

 This is a call for vote to graduate Oozie podling from Apache Incubator.
 
 Oozie entered the Incubator in July of 2011. Since then it has added
 two new committers and made two significant releases following the ASF
 policies and guidelines. The community of Oozie is active, healthy and
 growing and has demonstrated the ability to self-govern using accepted
 Apache practices. Oozie community has voted to proceed with graduation
 [1] and the result can be found at [2].
 
 Please cast your votes:
 
 [  ] +1 Graduate Oozie podling from Apache Incubator
 [  ] +0 Indifferent to the graduation status of Oozie podling
 [  ] -1 Reject graduation of Oozie podling from Apache Incubator
 
 This vote will be open for at least 72 hours. Please find the proposed
 board resolution below.
 
 [1] http://s.apache.org/WDb
 [2] http://s.apache.org/AB2
 
 Regards,
 Alejandro Abdelnur
 
 
X. Establish the Apache Oozie 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 related to a system for managing
   and scheduling workflows that run Apache Hadoop Map Reduce
   jobs, Apache Pig jobs, Apache Hive jobs and Apache Sqoop jobs
   for distribution at no charge to the public.
 
   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
   Committee (PMC), to be known as the Apache Oozie Project,
   be and hereby is established pursuant to Bylaws of the
   Foundation; and be it further
 
   RESOLVED, that the Apache Oozie Project be and hereby is
   responsible for the creation and maintenance of software
   related to a system for managing
   and scheduling workflows that run Apache Hadoop Map Reduce
   jobs, Apache Pig jobs, Apache Hive jobs and Apache Sqoop jobs;
   and be it further
 
   RESOLVED, that the office of Vice President, Apache Oozie 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 Oozie Project, and to have primary responsibility
   for management of the projects within the scope of
   responsibility of the Apache Oozie 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 Oozie Project:
 
* Alejandro Abdelnurt...@apache.org
* Andreas Neumann   a...@apache.org
* Angelo Huang  ange...@apache.org
* Chao Wang broo...@apache.org
* Harsh Chouraria   qwertyman...@apache.org
* Mayank Bansal may...@apache.org
* Mohammad Islamkam...@apache.org
* Virag Kothari vi...@apache.org
 
   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Alejandro Abdelnur
   be appointed to the office of Vice President, Apache Oozie,
   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 Oozie 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 Oozie Project; and be it further
 
   RESOLVED, that the Apache Oozie Project be and hereby
   is tasked with the migration and rationalization of the Apache
   Incubator Oozie podling; and be it further
 
   RESOLVED, that all responsibilities pertaining to the Apache
   Incubator Oozie podling encumbered upon the Apache Incubator
   Project are hereafter discharged.
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 

--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/

Re: [PROPOSAL] Drill for the Apache Incubator

[Arun C Murthy]

On Aug 8, 2012, at 2:13 PM, Ted Dunning wrote:
 
  It is clear that there are gobs of people with the
 credentials and track record to be potential contributors, but it is
 also clear that many of these people have huge demands on their time.
 That leaves doubt about how much contribution they can or should be
 making to a new project.

Wow! It's your project, and you can choose how to run this. However, when I do 
contribute I hope my contributions aren't discouraged because I should not be 
contributing to a new project because of the demands on my time after I 
volunteered to. 

I don't wish to belabor this or stand in your way, good luck. Hopefully, the 
project will be encouraging to new contributors.

Arun

Re: [PROPOSAL] Drill for the Apache Incubator

[Arun C Murthy]

Ted,

Wasn't clear, can I add myself now?

thanks,
Arun

On Aug 6, 2012, at 9:08 AM, Ted Dunning wrote:

 Sounds like some good pull.  I will call a vote tomorrow.
 
 On Mon, Aug 6, 2012 at 9:45 AM, Arun C Murthy a...@hortonworks.com wrote:
 
 Agreed, likewise.
 
 I'd love to get involved and would like to add myself whenever you are
 ready.
 
 thanks,
 Arun
 
 On Aug 3, 2012, at 10:40 AM, Owen O'Malley wrote:
 
 On Thu, Aug 2, 2012 at 3:12 PM, Ted Dunning ted.dunn...@gmail.com
 wrote:
 
 Drill is a distributed system for interactive analysis of large-scale
 datasets, inspired by Google’s Dremel (
 http://research.google.com/pubs/pub36632.html).
 
 
 This sounds really interesting Ted and I would love to help you. Would it
 be ok to add myself as one of the initial committers?
 
 Thanks,
  Owen
 
 --
 Arun C. Murthy
 Hortonworks Inc.
 http://hortonworks.com/
 
 
 

--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/

Re: [PROPOSAL] Drill for the Apache Incubator

[Arun C Murthy]

Agreed, likewise.

I'd love to get involved and would like to add myself whenever you are ready.

thanks,
Arun

On Aug 3, 2012, at 10:40 AM, Owen O'Malley wrote:

 On Thu, Aug 2, 2012 at 3:12 PM, Ted Dunning ted.dunn...@gmail.com wrote:
 
 Drill is a distributed system for interactive analysis of large-scale
 datasets, inspired by Google’s Dremel (
 http://research.google.com/pubs/pub36632.html).
 
 
 This sounds really interesting Ted and I would love to help you. Would it
 be ok to add myself as one of the initial committers?
 
 Thanks,
   Owen

--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/

Re: [VOTE] S4 0.5.0 Release Candidate 1

[Arun C Murthy]

+1. Verified signature and checksums, RAT too.

Arun

On Aug 2, 2012, at 10:24 PM, Patrick Hunt wrote:

 +1. The signature and checksum files all verify for me. I ran through
 the release checklist and that seems fine. RAT check looked good.
 license/notice files look valid for both src and bin artifacts.
 
 Patrick
 
 On Wed, Aug 1, 2012 at 4:11 PM, Flavio Junqueira f...@yahoo-inc.com wrote:
 +1, I checked that the src artifact compiles and tests pass. I have also 
 gone through license and notice files for the bin artifact, and I couldn't 
 spot any issue.
 
 On Aug 1, 2012, at 7:16 PM, Leo Neumeyer wrote:
 
 +1 Thank you for your leadership, Matthieu.
 
 On Wed, Aug 1, 2012 at 7:54 AM, kishore g g.kish...@gmail.com wrote:
 
 +1
 
 On Wed, Aug 1, 2012 at 2:55 AM, Daniel Gómez Ferro
 danie...@yahoo-inc.comwrote:
 
 +1
 
 * Signatures and checksums match
 * I created and ran a simple app using both src and bin packages with a
 clean maven/gradle repository
 * src package matches git tag
 * All tests pass
 
 
 
 On 31/7/12 17:02 , Matthieu Morel wrote:
 
 Hello,
 
 this is the first release candidate for Apache S4, version 0.5.0
 
 It fixes the following issues:
 https://issues.apache.org/**jira/secure/ReleaseNote.jspa?**
 projectId=12312322version=**12318653
 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312322version=12318653
 
 
 *** Please download, test and vote by Friday August 3rd 2012, 16.00 GMT
 
 Note that we are voting upon the source (tag), binaries are provided for
 convenience.
 
 Source and binary packages in zip format:
 http://people.apache.org/~**mmorel/s4-0.5.0-incubating-**
 release-candidate-1/
 http://people.apache.org/~mmorel/s4-0.5.0-incubating-release-candidate-1/
 
 The (git) tag to be voted upon: 0.5.0:
 
 https://git-wip-us.apache.org/**repos/asf?p=incubator-s4.git;**a=tag;h=**
 70806aa1ee0b9154d36fd834dc4907**cd8d3eb791
 https://git-wip-us.apache.org/repos/asf?p=incubator-s4.git;a=tag;h=70806aa1ee0b9154d36fd834dc4907cd8d3eb791
 
 
 S4 KEYS file containing PGP keys we use to sign the release:
 http://svn.apache.org/repos/**asf/incubator/s4/dist/KEYS
 http://svn.apache.org/repos/asf/incubator/s4/dist/KEYS
 
 Please cast your vote.
 
 [ ] +1  approve
 [ ] +0  no opinion
 [ ] -1  disapprove (and reason why)
 
 
 NOTES:
 
 - The vote is open until Friday August 3rd 2012, 16.00 GMT and passes if
 a majority of at least 3 +1 IPMC votes are cast.
 
 - All votes are welcome, only Podling Project Management Committe (PPMC)
 votes are binding, current PPMC = mentors + initial committers
 
 - After approval from the development community, we shall require
 approval from Incubator PMCs through another vote on the general
 incubator mailing list.
 
 
 
 
 
 
 --
 
 Leo Neumeyer (@leoneu)
 
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 

--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/

Re: [VOTE] Accept Crunch into the Apache Incubator

[Arun C Murthy]

-programmers to
 quickly create and run !MapReduce jobs. Crunch is a Java library whose
 primary community is Java developers who are creating scalable data
 pipelines and !MapReduce-based applications. Additionally, Hive and
 Pig both employ a relational, tuple-oriented data model on top of
 HDFS, which introduces overhead and limits expressive power for
 developers who are working with serialized objects and non-relational
 data types. Crunch uses a lower-level data model that gives developers
 the freedom to work with data in a format that is optimized for the
 problem they are trying to solve.
 
 == An Excessive Fascination with the Apache Brand ==
 
 We would like Crunch to become an Apache project to further foster a
 healthy community of contributors and consumers around the project.
 Since Crunch directly interacts with many Apache Hadoop-related
 projects and solves an important problem of many Hadoop users,
 residing in the Apache Software Foundation will increase interaction
 with the larger community.
 
 = Documentation =
 
 * Crunch wiki at GitHub: https://github.com/cloudera/crunch/wiki
 * Crunch jira at Cloudera: https://issues.cloudera.org/browse/crunch
 * Crunch javadoc at GitHub: http://cloudera.github.com/crunch/apidocs/
 
 = Initial Source =
 
 * https://github.com/cloudera/crunch/tree/
 
 == Source and Intellectual Property Submission Plan ==
 
 * The initial source is already licensed under the Apache License,
 Version 2.0. https://github.com/cloudera/crunch/blob/master/LICENSE.txt
 
 == External Dependencies ==
 
 The required external dependencies are all Apache License or
 compatible licenses. Following components with non-Apache licenses are
 enumerated:
 
 * com.google.protobuf : New BSD
 * org.hamcrest: New BSD
 * org.slf4j: MIT-like License
 
 Non-Apache build tools that are used by Crunch are as follows:
 
 * Cobertura: GNU GPLv2
 
 Note that Cobertura is optional and is only used for calculating unit
 test coverage.
 
 == Cryptography ==
 
 Crunch uses standard APIs and tools for SSH and SSL communication
 where necessary.
 
 = Required  Resources =
 
 == Mailing lists ==
 
 * crunch-private (with moderated subscriptions)
 * crunch-dev
 * crunch-commits
 * crunch-user
 
 == Github Repositories ==
 
 http://github.com/apache/crunch
 git://git.apache.org/crunch.git
 
 == Issue Tracking ==
 
 JIRA Crunch (CRUNCH)
 
 == Other Resources ==
 
 The existing code already has unit and integration tests so we would
 like a Jenkins instance to run them whenever a new patch is submitted.
 This can be added after project creation.
 
 = Initial Committers =
 
 * Brock Noland (brock at cloudera dot com)
 * Josh Wills (jwills at cloudera dot com)
 * Gabriel Reid (gabriel dot reid at gmail dot com)
 * Tom White (tom at cloudera dot com)
 * Christian Tzolov (christian dot tzolov at gmail dot com)
 * Robert Chu (robert at wibidata dot com)
 * Vinod Kumar Vavilapalli (vinodkv at hortonworks dot com)
 
 = Affiliations =
 
 * Brock Noland, Cloudera
 * Josh Wills, Cloudera
 * Gabriel Reid, !TomTom
 * Tom White, Cloudera
 * Christian Tzolov, !TomTom
 * Robert Chu, !WibiData
 * Vinod Kumar Vavilapalli, Hortonworks
 
 = Sponsors =
 
 == Champion ==
 
 * Patrick Hunt
 
 == Nominated Mentors ==
 
 * Tom White
 * Patrick Hunt
 * Arun Murthy
 
 == Sponsoring Entity ==
 
 * Apache Incubator PMC
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 

--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/

Re: [DISCUSS] Crunch to join the Apache Incubator

[Arun C Murthy]

Josh,

 Sounds interesting, I've followed Crunch given my leanings towards Apache 
Hadoop MapReduce. Good to see it in the ASF.

 If you don't mind I'll sign up as a volunteer mentor.

thanks,
Arun

On May 15, 2012, at 5:23 PM, Josh Wills wrote:

 Hi all,
 
 I would like to propose Crunch, a library for writing MapReduce
 pipelines in Java and Scala, as an Apache Incubator project. The
 proposal is here:
 
 http://wiki.apache.org/incubator/CrunchProposal
 
 We would gladly welcome additional volunteers to act as mentors on the
 project, so if this sounds like your cup of tea, please feel free to
 sign up or let us know.
 
 Thanks!
 Josh
 
 -- 
 Director of Data Science
 Cloudera
 Twitter: @josh_wills
 
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 

--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/

Re: [VOTE] Release Apache HCatalog 0.4.0-incubating

[Arun C Murthy]

+1 (binding)

Verified sigs etc., looks good.

Arun


On May 11, 2012, at 4:33 PM, Alan Gates wrote:

 Hi,
 
 Please vote for releasing Apache HCatalog 0.4.0-incubating.
 
 rc6 for this release has passed a PPMC vote and is now advancing to an IPMC 
 vote.
 
 The PPMC vote thread is at 
 http://mail-archives.apache.org/mod_mbox/incubator-hcatalog-dev/201205.mbox/%3C47EA6ABF-9675-4988-9BE3-5783CD121146%40hortonworks.com%3E
 
 The release is available at: 
 http://people.apache.org/~gates/hcatalog-0.4.0-incubating-candidate-6/
 
 The keys used to sign this release are available in svn at: 
 http://svn.apache.org/repos/asf/incubator/hcatalog/trunk/KEYS
 
 The release tag is: 
 http://svn.apache.org/repos/asf/incubator/hcatalog/tags/release-0.4.0-rc6/
 
 This vote will be open for at least 72 hours.
 
 Here's my +1.
 
 Alan.
 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org
 

--
Arun C. Murthy
Hortonworks Inc.
http://hortonworks.com/

Re: [VOTE] Graduate Sqoop podling from Apache Incubator

[Arun C Murthy]

Arvind,

(Sorry, I missed this discussion.)

On Feb 28, 2012, at 10:53 AM, Arvind Prabhakar wrote:

 Please see [1] for details on why the code is like this. The short
 summary is that binary compatibility requires us to respect all
 extension points within the code.
 
 [1] https://cwiki.apache.org/confluence/display/SQOOP/Namespace+Migration


This might be prior to your involvement with Sqoop, but it was initially part 
of Apache Hadoop MapReduce as a contrib module prior to being moved out to 
github.
https://issues.apache.org/jira/browse/HADOOP-5815
http://svn.apache.org/viewvc/hadoop/common/branches/branch-0.21-old/mapreduce/src/contrib/sqoop/

Thus, does the Sqoop community also plan to maintain back-compat with 
org.apache.hadoop.sqoop namespace for older users too?

I can't seem to place whether we ever made Apache Hadoop releases which 
included Sqoop before it got moved out...

Arun

Re: [VOTE] Graduate Sqoop podling from Apache Incubator

[Arun C Murthy]

On Feb 29, 2012, at 11:10 AM, Arun C Murthy wrote:

 Arvind,
 
 (Sorry, I missed this discussion.)
 
 On Feb 28, 2012, at 10:53 AM, Arvind Prabhakar wrote:
 
 Please see [1] for details on why the code is like this. The short
 summary is that binary compatibility requires us to respect all
 extension points within the code.
 
 [1] https://cwiki.apache.org/confluence/display/SQOOP/Namespace+Migration
 
 
 This might be prior to your involvement with Sqoop, but it was initially part 
 of Apache Hadoop MapReduce as a contrib module prior to being moved out to 
 github.
 https://issues.apache.org/jira/browse/HADOOP-5815
 http://svn.apache.org/viewvc/hadoop/common/branches/branch-0.21-old/mapreduce/src/contrib/sqoop/
 
 Thus, does the Sqoop community also plan to maintain back-compat with 
 org.apache.hadoop.sqoop namespace for older users too?
 
 I can't seem to place whether we ever made Apache Hadoop releases which 
 included Sqoop before it got moved out...

Uh, hit 'send' too soon...

Never mind - I was looking at the wrong project in ASF jira (HADOOP and not 
MAPREDUCE).

Sqoop was removed via https://issues.apache.org/jira/browse/MAPREDUCE-1644

Turns out we never released Sqoop via Apache Hadoop - so my question is moot. 
Sorry for the noise.

Arun

Re: [VOTE] Release Kafka-0.7.0-incubating

[Arun C Murthy]

+1 (binding)

Verified sigs, checked NOTICE and ran tests.

Arun

On Dec 20, 2011, at 5:42 PM, Neha Narkhede wrote:

 Hi,
 
 Kafka community is excited to share RC 9 for release of
 Kafka-0.7.0-incubating. In the interest of saving time, and with the
 expectation that the one-liner change will pass the vote on
 kafka-users@, we will run a vote in parallel here.
 
 Vote thread http://markmail.org/message/sefgr5lxccty4tjz?q=kafka+candidate+9
 
 Release artifacts
 http://people.apache.org/~nehanarkhede/kafka-0.7.0-incubating-candidate-9/
 
 SVN revision 
 https://svn.apache.org/repos/asf/incubator/kafka/tags/kafka-0.7.0-incubating-candidate-9
 
 PGP release keys http://svn.apache.org/repos/asf/incubator/kafka/KEYS
 
 This vote is open until Friday, Dec 23rd 6pm
 
 Thanks,
 Neha
 
 -
 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] accept DirectMemory as new Apache Incubator podling

[Arun C Murthy]

+1 (binding)

Arun

On Oct 2, 2011, at 12:36 AM, Simone Tripodi wrote:

 Hi all guys,
 
 I'm now calling a formal VOTE on the DirectMemory proposal located here:
 
 http://wiki.apache.org/incubator/DirectMemoryProposal
 
 Proposal text copied at the bottom of this email.
 
 VOTE close on Tuesday, October 4, early 7:30 AM CET.
 
 Please VOTE:
 
 [ ] +1 Accept DirectMemory into the Apache Incubator
 [ ] +0 Don't care
 [ ] -1  Don't Accept DirectMemory into the Apache Incubator because...
 
 Thanks in advance for participating!
 
 All the best, have a nice day,
 Simo
 
 P.S. Here's my +1
 
 http://people.apache.org/~simonetripodi/
 http://www.99soft.org/
 
 = DirectMemory =
 
 == Abstract ==
 The following proposal is about Apache !DirectMemory, a Java
 !OpenSource multi-layered cache implementation featuring off-heap
 memory storage (a-la Terracotta !BigMemory) to enable caching of Java
 objects without degrading JVM performance
 
 == Proposal ==
 !DirectMemory's main purpose is to to act as a second level cache
 (after a heap based one) able to store large amounts of data without
 filling up the Java heap and thus avoiding long garbage collection
 cycles. Although serialization has a runtime cost store/retrieve
 operations are in the sub-millisecond range being pretty acceptable in
 every usage scenario even as a first level cache and, most of all,
 outperforms heap storage when the count of the entries goes over a
 certain amount. !DirectMemory implements cache eviction based on a
 simple LFU (Least Frequently Used) algorythm and also on item
 expiration. Included in the box is a small set of utility classes to
 easily handle off-heap memory buffers.
 
 == Background ==
 !DirectMemory is a project was born in the 2010 thanks to Raffaele P.
 Guidi initial effort under
 [[https://github.com/raffaeleguidi/!DirectMemory/|GitHub]] and already
 licensed under the Apache License 2.0.
 
 == Rationale ==
 The rationale behind !DirectMemory is bringing off-heap caching to the
 open source world, empowering FOSS developers and products with a tool
 that enables breaking the heap barrier and override the JVM garbage
 collection mechanism collection - which could be useful in scenarios
 where RAM needs are over the usual limits (more than 8, 12, 24gb) and
 to ease usage of off-heap memory in general
 
 = Current Status =
 
 == Meritocracy ==
 As a majority of the initial project members are existing ASF
 committers, we recognize the desirability of running the project as a
 meritocracy.  We are eager to engage other members of the community
 and operate to the standard of meritocracy that Apache emphasizes; we
 believe this is the most effective method of growing our community and
 enabling widespread adoption.
 
 == Core Developers ==
 In alphabetical order:
 
 * Christian Grobmeier grobmeier at apache dot org
 * Maurizio Cucchiara mcucchiara at apache dot org
 * Olivier Lamy olamy at apache dot org
 * Raffaele P. Guidi raffaele dot p dot guidi at gmail dot com
 * Simone Gianni simoneg at apache dot org
 * Simone Tripodi simonetripodi at apache dot org
 * Tommaso Teofili tommaso at apache dot org
 
 == Alignment ==
 The purpose of the project is to develop and maintain !DirectMemory
 implementation that can be used by other Apache projects.
 
 = Known Risks =
 == Orphaned Products ==
 !DirectMemory does not have any reported production usage, yet, but is
 getting traction with developers and being evaluated by potential
 users and thus the risks of it being orphaned are minimal
 
 == Inexperience with Open Source ==
 All of the committers have experience working in one or more open
 source projects inside and outside ASF.
 
 == Homogeneous Developers ==
 The list of initial committers are geographically distributed across
 the Europe with no one company being associated with a majority of the
 developers.  Many of these initial developers are experienced Apache
 committers already and all are experienced with working in distributed
 development communities.
 
 == Reliance on Salaried Developers ==
 To the best of our knowledge, none of the initial committers are being
 paid to develop code for this project.
 
 == Relationships with Other Apache Products ==
 !DirectMemory fits naturally in the ASF because it could be
 successfully employed together with a large number of ASF products
 ranging from JCS - as a new cache region between the heap and indexed
 file ones, to ORM systems like Cayenne (i.e. replacing current OSCache
 based implementation), Apache JDO and JPA implementations and also
 java based databases (i.e. Derby) and all systems managing large
 amounts of data from Hadoop to Cassandra
 
 == A Excessive Fascination with the Apache Brand ==
 While the Apache Software Foundation would be a good home for the
 !DirectMemory project it already has some traction and it could live
 on its own - however we see reciprocal benefits for both the ASF and
 the project in adopting the brand to better reach the community
 

Re: [VOTE] Release HCatalog 0.2-incubating (RC1)

[Arun C Murthy]

+1 lgtm!

Downloaded, verified bits and ran unit tests.

Arun

On Sep 26, 2011, at 11:38 AM, Ashutosh Chauhan wrote:

 Hi all,
 
 HCatalog community is excited to share that RC for release of
 HCatalog has been +1'd over at hcatalog-user@incubator Please try it
 out and vote for the Apache HCatalog 0.2-incubating release.
 
 
 Vote thread:
 http://markmail.org/thread/s7b53a4a2xd35jad
 
 Artifact and signatures:
 http://people.apache.org/~hashutosh/hcatalog-0.2.0-incubating-candidate-1/
 
 SVN Tag:
 https://svn.apache.org/repos/asf/incubator/hcatalog/tags/release-0.2.0-rc1/
 
 
 PGP release keys:
 https://svn.apache.org/repos/asf/incubator/hcatalog/trunk/KEYS
 
 [ ] +1 Release the packages as Apache HCatalog 0.2-incubating
 [ ] -1 Do not release the packages because...
 
 Thanks,
 Ashutosh


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

Re: [PROPOSAL] S4 for the Apache Incubator

[Arun C Murthy]

Happy to help mentor S4.

Arun

On Sep 20, 2011, at 9:13 AM, Patrick Hunt wrote:

 There are currently only 2 mentors volunteering to help out (Owen and
 myself), would be great to have 3+ -- any IPMC members out there that
 could help with the mentoring effort?
 
 Regards,
 
 Patrick
 
 On Mon, Sep 19, 2011 at 10:53 PM, Vinod Kumar Vavilapalli
 vino...@hortonworks.com wrote:
 On Mon, Sep 19, 2011 at 10:43 PM, Flavio Junqueira f...@s4.io wrote:
 
 To give you an idea of what we have in mind, here are a few points:
 
 - Monitor Nodes and PEs.
 - Ability to  query specific PE instance variables.
 - Add remove nodes.
 - Monitor logs.
 - Monitor CPU/Memory usage per node.
 - Load/unload apps.
 
 
 
 It does look like some of the resource management can be offloaded to YARN.
 
 
 
 In general, it sounds right to assess if it is viable to use YARN for S4
 cluster management and we would appreciate your help. If it is ok with you,
 I'd rather not include it in the proposal, though, since it is an issue we
 could consider independently of the project going into incubator. Let me
 know if you agree.
 
 
 
 Definitely.
 
 Thanks,
 +Vinod
 
 
 -
 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] S4 to join the Incubator

[Arun C Murthy]

+1 (binding)

Arun

On Sep 20, 2011, at 1:56 PM, Patrick Hunt wrote:

 It's been a nearly a week since the S4 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/S4Proposal
 
 The discussion regarding the proposal can be found at:
 
 http://s.apache.org/RMU
 
 Please cast your votes:
 
 [  ] +1 Accept S4 for incubation
 [  ] +0 Indifferent to S4 incubation
 [  ] -1 Reject S4 for incubation
 
 This vote will close 72 hours from now.
 
 Thanks,
 
 Patrick
 
 --
 = S4 Proposal =
 
 == Abstract ==
 
 S4 (Simple Scalable Streaming System) is a general-purpose,
 distributed, scalable, partially fault-tolerant, pluggable platform
 that allows programmers to easily develop applications for processing
 continuous, unbounded streams of data.
 
 == Proposal ==
 
 S4 is a software platform written in Java. Clients that send and
 receive events can be written in any programming language. S4 also
 includes a collection of modules called Processing Elements (or PEs
 for short) that implement basic functionality and can be used by
 application developers. In S4, keyed data events are routed with
 affinity to Processing Elements (PEs), which consume the events and do
 one or both of the following: (1) ''emit'' one or more events which
 may be consumed by other PEs, (2) ''publish'' results. The
 architecture resembles the Actors model, providing semantics of
 encapsulation and location transparency, thus allowing applications to
 be massively concurrent while exposing a simple programming  interface
 to application developers.
 
 To drive adoption and increase the number of contributors to the
 project, we may need to prioritize the focus based on feedback from
 the community. We believe that one of the top priorities and driving
 design principle for the S4 project is to provide a simple API that
 hides most of the complexity associated with distributed systems and
 concurrency. The project grew out of the need to provide a flexible
 platform for application developers and scientists that can be used
 for quick experimentation and production.
 
 S4 differs from existing Apache projects in a number of fundamental
 ways. Flume is an Incubator project that focuses on log processing,
 performing lightweight processing in a distributed fashion and
 accumulating log data in a centralized repository for batch
 processing. S4 instead performs all stream processing in a distributed
 fashion and enables applications to form arbitrary graphs to process
 streams of events. We see Flume as a complementary project. We also
 expect S4 to complement Hadoop processing and in some cases to
 supersede it. Kafka is another Incubator project that focuses on
 processing large amounts of stream data. The design of Kafka, however,
 follows the pub-sub paradigm, which focuses on delivering messages
 containing arbitrary data from source processes (publishers) to
 consumer processes (subscribers). Compared to S4, Kafka is an
 intermediate step between data generation and processing, while S4 is
 itself a platform for processing streams of events.
 
 S4 overall addresses a need of existing applications to process
 streams of events beyond moving data to a centralized repository for
 batch processing. It complements the features of existing Apache
 projects, such as Hadoop, Flume, and Kafka, by providing a flexible
 platform for distributed event processing.
 
 == Background ==
 
 S4 was initially developed at Yahoo! Labs starting in 2008 to process
 user feedback in the context of search advertising. The project was
 licensed under the Apache License version 2.0 in October 2010. The
 project documentation is currently available at http://s4.io .
 
 == Rationale ==
 
 Stream computing has been growing steadily over the last 20 years.
 However, recently there has been an explosion in real-time data
 sources including the Web, sensor networks, financial securities
 analysis and trading, traffic monitoring, natural language processing
 of news and social data, and much more.
 
 As Hadoop evolved as a standard open source solution for batch
 processing of massive data sets, there is no equivalent community
 supported open source platform for processing data streams in
 real-time. While various research projects have evolved into
 proprietary commercial products, S4 has the potential to fill the gap.
 Many projects that require a scalable stream processing architecture
 currently use Hadoop by segmenting the input stream into data batches.
 This solution is not efficient, results in high latency, and
 introduces unnecessary complexity.
 
 The S4 design is primarily driven by large scale applications for data
 mining and machine learning in a production environment. We think that
 the S4 design 

Re: [VOTE] Change the name of the HMS podling to Ambari.

[Arun C Murthy]

+1

Arun

On Aug 31, 2011, at 10:58 AM, Owen O'Malley wrote:

 When I was doing the initial trademark search for HMS, I found that
 there are a lot of projects (including software) named HMS. It also
 has the problem of being very bad to search for (42.7m hits on
 google).
 
 Before I go through and create the infrastructure for Apache
 incubator, I wanted to discuss changing the name. Suhas did some
 searches and found that the name for the royal chair on top of
 elephants is Ambari, which seems like a very nice name to me.
 
 Toward that end, I'd like to propose changing the name from HMS to Ambari.
 
 -- Owen
 
 -
 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] Accept HMS as an incubator project

[Arun C Murthy]

 to make the project open source and encourage contributors from 
 multiple organizations from the start. We plan to provide plenty of support 
 to new developers and to quickly recruit those who make solid contributions 
 to committer status.
 
 Community
 
 We are happy to report that multiple organizations are already represented by 
 initial team. We hope to extend the user and developer base further in the 
 future and build a solid open source community around HMS.
 
 Core Developers
 
 HMS is currently being developed by four engineers from Hortonworks - Eric 
 Yang, Owen O’Malley, Vitthal (a.k.a Suhas) Gogate and Devaraj Das. In 
 addition, a Yahoo! employee, Jagane Sundar, and an IBM employee, Kan Zhang, 
 are also involved. Eric, Jagane and Kan are the original developers. All the 
 engineers have deep expertise in Hadoop and are quite familiar with the 
 Hadoop Ecosystem.
 
 Alignment
 
 The ASF is a natural host for HMS given that it is already the home of 
 Hadoop, Pig, HBase, Cassandra, and other emerging cloud software projects. 
 HMS has been designed to solve the deployment, management and configuration 
 problems of the Hadoop ecosystem family of products. HMS fills the gap that 
 Hadoop ecosystem has been lacking in the areas of configuration, deployment 
 and manageability.
 
 Known Risks
 
 Orphaned products  Reliance on Salaried Developers
 
 The core developers plan to work full time on the project. There is very 
 little risk of HMS getting orphaned. HMS is in use by companies we work for 
 so the companies have an interest in its continued vitality.
 
 Inexperience with Open Source
 
 All of the core developers are active users and followers of open source. 
 Eric Yang is a committer on Apache Chukwa. Owen O’Malley is the lead of the 
 Apache Hadoop project. Devaraj Das is an Apache Hadoop committer and Apache 
 Hadoop PMC member. Vitthal (Suhas) Gogate has contributed extensively to the 
 Hadoop Vaidya project (part of Apache Hadoop). Jagane Sundar has been 
 contributing, in terms of ideas, to the Hadoop project. Kan Zhang is a Hadoop 
 Committer.
 
 Homogeneous Developers
 
 The current core developers are from Hortonworks, IBM, and, Yahoo!. However, 
 we hope to establish a developer community that includes contributors from 
 several corporations.
 
 Reliance on Salaried Developers
 
 Currently, the developers are paid to do work on HMS. However, once the 
 project has a community built around it, we expect to get committers and 
 developers from outside the current core developers.
 
 Relationships with Other Apache Products
 
 HMS is going to be used by the users of Hadoop and the Hadoop ecosystem in 
 general.
 
 A Excessive Fascination with the Apache Brand
 
 While we respect the reputation of the Apache brand and have no doubts that 
 it will attract contributors and users, our interest is primarily to give HMS 
 a solid home as an open source project following an established development 
 model. We have also given reasons in the Rationale and Alignment sections.
 
 Documentation
 
 There is documentation in Hortonworks’s internal repositories.
 
 Initial Source
 
 The source is currently in Hortonworks’s internal repositories.
 
 Source and Intellectual Property Submission Plan
 
 The complete HMS code is under Apache Software License 2.
 
 External Dependencies
 
 The dependencies all have Apache compatible licenses. These include BSD, MIT 
 licensed dependencies.
 
 Cryptography
 
 None
 
 Required Resources
 
 Mailing lists
 
   • hms-dev AT incubator DOT apache DOT org
   • hms-commits AT incubator DOT apache DOT org
   • hms-user AT hms incubator apache DOT org
   • hms-private AT incubator DOT apache DOT org
 Subversion Directory
 
 https://svn.apache.org/repos/asf/incubator/hms
 
 Issue Tracking
 
 JIRA HMS
 
 Initial Committers
 
   • Devaraj Das (ddas AT apache DOT org)
   • Vitthal Suhas Gogate (gogate AT apache DOT org)
   • Owen O'Malley (omalley AT apache DOT org)
   • Jagane Sunder (jagane AT sundar DOT org)
   • Eric Yang (eyang AT apache DOT org)
   • Kan Zhang (kzhang AT apache DOT org)
 Affiliations
 
   • Devaraj Das (Hortonworks)
   • Vitthal Suhas Gogate (Hortonworks)
   • Owen O'Malley (Hortonworks)
   • Jagane Sunder (Yahoo)
   • Eric Yang (Hortonworks)
   • Kan Zhang (IBM)
   • Chris Douglas (Yahoo)
   • Arun C Murthy (Hortonworks)
 Sponsors
 
 Champion
 
   • Owen O'Malley
 Nominated Mentors
 
   • Owen O'Malley
   • Arun C Murthy
   • Chris Douglas
 Sponsoring Entity
 
 Incubator PMC
 -
 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

Re: [VOTE] Pig graduation to hadoop subproject

[Arun C Murthy]

+1

Arun

On Oct 6, 2008, at 3:32 PM, Olga Natkovich wrote:


Pig Developers and Mentors,

Pig has been incubating for over a year now. In this period of time,  
we

had extended our community with 2 new committers, had a release,
resolved 300 issues. We have made some significant code improvements
including pipeline redesign, addition of streaming and limit
functionality, grunt shell improvements and significant performance
speedup. We have a constant traffic and lively discussions on both
pig-dev and pig-user mailing lists and we conduct our business in the
open by publishing proposals and discussing them in the mailing lists.

As of now, we have completed graduation requirements as described in
http://incubator.apache.org/guides/graduation.html.

I would like to call for a graduation vote at this time.

I would also propose that we graduate as a subproject of Hadoop. There
are several advantages to this approach. First, this would allow us to
extend both our user and developer base. Second, it would bring  
benefits
to the Hadoop community by providing a higher level interface and  
easier

entry point for new users. Third, having an established project to
provide guidance, would help Pig to become a mature participant in the
open source community.

Please, vote by the end of the day on Thursday, 10/9.

Thanks,

Olga

PS: I am ccing  hadoop and incubator general mailing lists; however,  
no

action is required from them at this time. This step is for Pig
community only.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]