Fwd: [VOTE] Graduate Helix from Apache Incubator to TLP
FYI - Helix community is taking a vote on graduating Helix to TLP -- Forwarded message -- From: kishore g Date: Mon, Nov 11, 2013 at 7:06 PM Subject: [VOTE] Graduate Helix from Apache Incubator to TLP To: dev Hi, As the discussion about Graduation have settled down, I am calling for the vote. Apache Helix entered Incubator in October 2012. We have made significant progress in incubation. Some of the highlights being - Cut two releases with PPMC being the release managers. Well documented release process that makes it easy to cut new releases. - Added 3 new committers, 2 from LinkedIn and 1 outside of LinkedIn. We already have 2 committers outside of LinkedIn. - Added 1 member to PPMC. - Kept the status page uptodate with all relevant information. - Followed Apache process and almost self governed. Community - We have been responsive to inquiries from user. Also adding additional features as needed. - We are in development mode and constantly making improvements and refactoring. 574 commits over the last 12 months. http://www.ohloh.net/p/apachehelix - 250+ Jiras - 45 in dev mailing list and 57 in user mailing list - Gaining adoption outside of LinkedIn. http://mvnrepository.com/artifact/org.apache.helix - All code reviews done via Apache review board. Please cast your votes: [ ] +1 Graduate Apache Helix from Incubator [ ] +0 Indifferent to graduation status of Apache Helix [ ] -1 Reject graduation of Apache Helix from Incubator This vote will remain open for at least 72 hours from now. Thanks, Kishore G
Re: [VOTE] helix-0.6.2-incubating
Hello, We are short of 1 binding vote. Appreciate if any one can review. Thanks, Kishore G On Nov 18, 2013 6:51 PM, "Kanak Biscuitwala" wrote: > Hi, > > This is to call for a vote on releasing the following candidate as Apache > Helix 0.6.2-incubating. This is the first release candidate of our third > release at Apache. > > Apache Helix is a generic cluster management framework that makes it easy > to build partitioned and replicated, fault tolerant and scalable > distributed systems. > > Release notes: > > http://helix.incubator.apache.org/site-releases/0.6.2-incubating-site/releasenotes/release-0.6.2-incubating.html > > Our vote thread on helix-dev: > http://markmail.org/message/f2odmc7ga2i5qqmh > > The following IPMC members have voted +1 > Patrick Hunt > Olivier Lamy > > Release artifacts: > https://repository.apache.org/content/repositories/orgapachehelix-138 > > Distribution: > * binaries: > > https://dist.apache.org/repos/dist/dev/incubator/helix/0.6.2-incubating/binaries/ > * sources: > > https://dist.apache.org/repos/dist/dev/incubator/helix/0.6.2-incubating/src/ > > The 0.6.2-incubating release tag > > https://git-wip-us.apache.org/repos/asf?p=incubator-helix.git;a=tag;h=74efd57c9f7bcb54cb6007dd34646722d6133340 > > KEYS file available here: > https://dist.apache.org/repos/dist/dev/incubator/helix/KEYS > > Please vote on the release. The vote will be open for 72 hours. > > [+1] > [0] > [-1] > > Thanks, > The Apache Helix Team > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
[PROPOSAL] Helix for the Apache Incubator
Hi, I would like to propose Helix to be an Apache Incubator project. The proposal can be found here: http://wiki.apache.org/incubator/HelixProposal I have included the contexts of the proposal below. Thanks, Kishore G == Abstract == Helix is a cluster management system for managing partitioned and replicated resources in distributed data systems. == Proposal == Helix provides an abstraction that separates coordination and management tasks from functional tasks of a distributed system. The developer defines the system behavior via a state machine, the transitions between those states, and constraints on states and transitions that govern the system’s valid settings. Helix ensures the distributed system satisfies the state machine, controlling state changes as appropriate during common operational activities such as upgrades, component failures, bootstrapping, running maintenance tasks, and adding capacity. == Background == Helix was developed at LinkedIn to manage large clusters for several diverse applications, including a distributed, partitioned, replicated, highly available document store with a master-slave model, a search service with multiple replicas that are updated atomically and in near real-time, and a change data capture service for reliably transporting database changes to caches, other dependent databases and indexes. These services use Helix to reliably manage dozens of clusters in multiple data centers. These services meet stringent SLAs at large scale for mission-critical production applications such as search, social gestures, and profiles. Helix has proven to be flexible for a wide variety of system configurations and operational patterns, is easy to integrate, with pluggable interfaces enabling custom behavior. It depends on Apache Zookeeper for coordination and tracking of system state across the cluster, as well as providing fault tolerance. Helix is written in Java. It was developed internally at LinkedIn to meet our particular use cases, but will be useful to many organizations facing a similar need to manage large clusters. Therefore, we would like to share it the ASF and begin developing a community of developers and users within Apache. == Rationale == Many organizations can benefit from a generalized cluster management system such as Helix. While our distributed data systems use-cases for a very large website like LinkedIn has driven the design of Helix, its uses are varied and we expect many new use cases to emerge. == Current Status == === Meritocracy === Our intent with this incubator proposal is to start building a diverse developer community around Helix following the Apache meritocracy model. Since Helix was initially developed in late 2011, we have had fast adoption and contributions by multiple teams at LinkedIn. We plan to continue support for new contributors and work with those who contribute significantly to the project to make them committers. === Community === Helix is currently being used internally at LinkedIn and is in production in that company for customer-facing features. Recent public presentations of Helix and its goals garnered much interest from potential contributors. We hope to extend our contributor base significantly and invite all those who are interested in building large-scale distributed systems to participate. To further this goal, we use GitHub issue tracking and branching facilities. === Core Developers === Helix is currently being developed by three engineers at LinkedIn: Kishore Gopalakrishna, Shi Lu and Jason Zheng, and Adam Silberstein, an engineer at Trifacta. Kishore, the lead developer and architect, has experience within Apache as an S4 committer. Shi developed the partition to node mapping and rebalancing algorithm, cluster admin APIs, and the health check framework. Jason developed the cluster controller and most of the test framework. Adam developed the rich alerting framework that enables cluster-wide, “intelligent“ alerts. === Alignment === The ASF is the natural choice to host the Helix project as its goal of encouraging community-driven open-source projects fits with our vision for Helix. Many projects that can benefit from Helix will rely on Apache ZooKeeper for cluster state management, and can far more easily achieve their operational goals by using Helix. == Known Risks == === Orphaned Products === The core developers plan to work full time on the project. There is very little risk of Helix being abandoned as it is a critical part of LinkedIn's internal infrastructure and is in production use. === Inexperience with Open Source === Only one of the core developers has experience with open source development. Kishore has been actively involved with the ASF as a committer and lead developer of S4. === Homogeneous Developers === The current core developers are all from LinkedIn. However, we hope to establish a developer community that includes contributors from several corporations and we are act
Re: [PROPOSAL] Helix for the Apache Incubator
Thanks Jakob. We do use Cobertura for coverage. I will fix the proposal. On Tue, Oct 9, 2012 at 12:04 PM, Jakob Homan wrote: >>> 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. > > What do Crunch and Cobertura have to do with Helix? Is this a bit on > incomplete proposal recycling? > > - > 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: [PROPOSAL] Helix for the Apache Incubator
Hello, The proposal is fixed http://wiki.apache.org/incubator/HelixProposal. We have also made the Github link public. Home Page: http://linkedin.github.com/helix/ Github source: https://github.com/linkedin/helix Documentation: https://github.com/linkedin/helix/wiki Javadocs: http://linkedin.github.com/helix/apidocs/ Thanks, Kishore G On Tue, Oct 9, 2012 at 12:50 PM, kishore g wrote: > Thanks Jakob. We do use Cobertura for coverage. I will fix the proposal. > > On Tue, Oct 9, 2012 at 12:04 PM, Jakob Homan wrote: >>>> 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. >> >> What do Crunch and Cobertura have to do with Helix? Is this a bit on >> incomplete proposal recycling? >> >> - >> 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
[VOTE] Accept Helix into Apache Incubator
Hi, I would like to call a vote for accepting Helix for incubation in the Apache Incubator. I have pasted the full proposal below. Please cast your vote: [ ] +1, bring Helix into Incubator [ ] +0, I don't care either way, [ ] -1, do not bring Helix into Incubator, because ... This vote will be open for 72 hours and only votes from the Incubator PMC are binding. Thanks, Kishore G == Abstract == Helix is a cluster management system for managing partitioned and replicated resources in distributed data systems. == Proposal == Helix provides an abstraction that separates coordination and management tasks from functional tasks of a distributed system. The developer defines the system behavior via a state machine, the transitions between those states, and constraints on states and transitions that govern the system’s valid settings. Helix ensures the distributed system satisfies the state machine, controlling state changes as appropriate during common operational activities such as upgrades, component failures, bootstrapping, running maintenance tasks, and adding capacity. == Background == Helix was developed at LinkedIn to manage large clusters for several diverse applications, including a distributed, partitioned, replicated, highly available document store with a master-slave model, a search service with multiple replicas that are updated atomically and in near real-time, and a change data capture service for reliably transporting database changes to caches, other dependent databases and indexes. These services use Helix to reliably manage dozens of clusters in multiple data centers. These services meet stringent SLAs at large scale for mission-critical production applications such as search, social gestures, and profiles. Helix has proven to be flexible for a wide variety of system configurations and operational patterns, is easy to integrate, with pluggable interfaces enabling custom behavior. It depends on Apache Zookeeper for coordination and tracking of system state across the cluster, as well as providing fault tolerance. Helix is written in Java. It was developed internally at LinkedIn to meet our particular use cases, but will be useful to many organizations facing a similar need to manage large clusters. Therefore, we would like to share it the ASF and begin developing a community of developers and users within Apache. == Rationale == Many organizations can benefit from a generalized cluster management system such as Helix. While our distributed data systems use-cases for a very large website like LinkedIn has driven the design of Helix, its uses are varied and we expect many new use cases to emerge. == Current Status == === Meritocracy === Our intent with this incubator proposal is to start building a diverse developer community around Helix following the Apache meritocracy model. Since Helix was initially developed in late 2011, we have had fast adoption and contributions by multiple teams at LinkedIn. We plan to continue support for new contributors and work with those who contribute significantly to the project to make them committers. === Community === Helix is currently being used internally at LinkedIn and is in production in that company for customer-facing features. Recent public presentations of Helix and its goals garnered much interest from potential contributors. We hope to extend our contributor base significantly and invite all those who are interested in building large-scale distributed systems to participate. To further this goal, we use GitHub issue tracking and branching facilities. === Core Developers === Helix is currently being developed by three engineers at LinkedIn: Kishore Gopalakrishna, Shi Lu and Jason Zheng, and Adam Silberstein, an engineer at Trifacta. Kishore, the lead developer and architect, has experience within Apache as an S4 committer. Shi developed the partition to node mapping and rebalancing algorithm, cluster admin APIs, and the health check framework. Jason developed the cluster controller and most of the test framework. Adam developed the rich alerting framework that enables cluster-wide, “intelligent“ alerts. === Alignment === The ASF is the natural choice to host the Helix project as its goal of encouraging community-driven open-source projects fits with our vision for Helix. Many projects that can benefit from Helix will rely on Apache ZooKeeper for cluster state management, and can far more easily achieve their operational goals by using Helix. == Known Risks == === Orphaned Products === The core developers plan to work full time on the project. There is very little risk of Helix being abandoned as it is a critical part of LinkedIn's internal infrastructure and is in production use. === Inexperience with Open Source === Only one of the core developers has experience with open source development. Kishore has been actively involved with the ASF as a committer and lead developer of S4. === Homogeneous Developers === The cu
Re: [VOTE] Accept Helix into Apache Incubator
Thanks Olivier for your interest. I am happy to have you as mentor. I am still having issues in editing the wiki, but will add you as mentor once I resolve it. thanks, Kishore G On Sat, Oct 13, 2012 at 7:38 AM, Olivier Lamy wrote: > +1 (binding). > Looks very interesting. Let me know if you need an other mentor for > the incubation. > > 2012/10/10 kishore g : >> Hi, >> >> I would like to call a vote for accepting Helix for incubation in the >> Apache Incubator. I have pasted the full proposal below. >> >> Please cast your vote: >> >> [ ] +1, bring Helix into Incubator >> [ ] +0, I don't care either way, >> [ ] -1, do not bring Helix into Incubator, because ... >> >> This vote will be open for 72 hours and only votes from the Incubator >> PMC are binding. >> >> Thanks, >> Kishore G >> >> >> == Abstract == >> Helix is a cluster management system for managing partitioned and >> replicated resources in distributed data systems. >> >> == Proposal == >> Helix provides an abstraction that separates coordination and >> management tasks from functional tasks of a distributed system. The >> developer defines the system behavior via a state machine, the >> transitions between those states, and constraints on states and >> transitions that govern the system’s valid settings. Helix ensures the >> distributed system satisfies the state machine, controlling state >> changes as appropriate during common operational activities such as >> upgrades, component failures, bootstrapping, running maintenance >> tasks, and adding capacity. >> >> == Background == >> Helix was developed at LinkedIn to manage large clusters for several >> diverse applications, including a distributed, partitioned, >> replicated, highly available document store with a master-slave model, >> a search service with multiple replicas that are updated atomically >> and in near real-time, and a change data capture service for reliably >> transporting database changes to caches, other dependent databases and >> indexes. >> >> These services use Helix to reliably manage dozens of clusters in >> multiple data centers. These services meet stringent SLAs at large >> scale for mission-critical production applications such as search, >> social gestures, and profiles. >> Helix has proven to be flexible for a wide variety of system >> configurations and operational patterns, is easy to integrate, with >> pluggable interfaces enabling custom behavior. It depends on Apache >> Zookeeper for coordination and tracking of system state across the >> cluster, as well as providing fault tolerance. >> Helix is written in Java. It was developed internally at LinkedIn to >> meet our particular use cases, but will be useful to many >> organizations facing a similar need to manage large clusters. >> Therefore, we would like to share it the ASF and begin developing a >> community of developers and users within Apache. >> >> == Rationale == >> Many organizations can benefit from a generalized cluster management >> system such as Helix. While our distributed data systems use-cases for >> a very large website like LinkedIn has driven the design of Helix, its >> uses are varied and we expect many new use cases to emerge. >> >> == Current Status == >> === Meritocracy === >> Our intent with this incubator proposal is to start building a diverse >> developer community around Helix following the Apache meritocracy >> model. Since Helix was initially developed in late 2011, we have had >> fast adoption and contributions by multiple teams at LinkedIn. >> We plan to continue support for new contributors and work with those >> who contribute significantly to the project to make them committers. >> >> === Community === >> Helix is currently being used internally at LinkedIn and is in >> production in that company for customer-facing features. Recent public >> presentations of Helix and its goals garnered much interest from >> potential contributors. We hope to extend our contributor base >> significantly and invite all those who are interested in building >> large-scale distributed systems to participate. >> To further this goal, we use GitHub issue tracking and branching facilities. >> >> === Core Developers === >> Helix is currently being developed by three engineers at LinkedIn: >> Kishore Gopalakrishna, Shi Lu and Jason Zheng, and Adam Silberstein, >> an engineer at Trifacta. Kishore, the lead developer and architect, >> has experience within Apache as an
[RESULT][VOTE] Accept Helix into Apache Incubator
Hello, Since 72 hours passed, I am closing the vote. Helix has been accepted for Apache Incubator with the following vote tally: +1 : 11 (8 binding) -1 : 0 Thanks, Kishore G Details: 1. Ted Dunning (binding) 2. Jakob Homan (binding) 3. Chris Douglas (binding) 4. Jukka Zitting (binding) 5. Roman Shaposhnik (non binding) 6. Patrick Hunt (binding) 7. Ahmed Radwan (non-binding) 8. Mahadev Konar (binding) 9. Suresh Maru (binding) 10. Bruno Mahe (non binding) 11. Olivier Lamy (binding)
Re: [ANNOUNCE] Welcome Roman Shaposhnik to the Apache Incubator PMC
Congrats Roman. On Fri, Oct 19, 2012 at 11:26 AM, Jarek Jarcec Cecho wrote: > Wow, > congratulations Roman! > > Jarcec > > On Oct 19, 2012, at 11:09 AM, Christian Grobmeier > wrote: > > > Welcome! > > > > On Fri, Oct 19, 2012 at 7:47 PM, Mattmann, Chris A (388J) > > wrote: > >> Hey Folks, > >> > >> The Apache Incubator PMC has VOTEd to add Roman Shaposhnik to our ranks. > >> > >> Welcome, Roman! Feel free to say a bit about yourself. > >> > >> Cheers, > >> Chris > >> > >> - > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > >> For additional commands, e-mail: general-h...@incubator.apache.org > >> > > > > > > > > -- > > http://www.grobmeier.de > > https://www.timeandbill.de > > > > - > > 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: Permission to edit wiki
Hi Marvin, I gave the wrong id, my apache id is kishoreg. Can you please fix it. thanks, Kishore G On Thu, Oct 11, 2012 at 4:59 PM, Marvin Humphrey wrote: > On Thu, Oct 11, 2012 at 4:52 PM, kishore g wrote: > > I may have to edit the Helix Proposal wiki. Can you please grant me > > the permission. My id is k4j > > Done. > > Marvin Humphrey > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [DISCUSS] Apache Mayhem proposal
As part of Helix incubation, we migrated to Apache Git from github and we havent faced any problems till now and we were able to maintain the history. On Thu, Nov 1, 2012 at 11:59 AM, Christian Grobmeier wrote: > Hello, > > I would prefer GIT, even when I am not a GIT guru. The reason is simple: > there is no way to save history when moving from git to svn. At least two > or three incubating projects had to fight with that recently (Wave, Cordova > i think). Somebody from the Apache committers started an effort to make a > migration tool but its not finished to my knowledge. > > That said, I welcome the opportunity to work with git in a big team. And I > would not like to loose history. > > Not sure about the entry criteria for the GIT experiment right now, but I > think it should be pretty stable - lets ask infra? > > Cheers > Christian > > > On Thu, Nov 1, 2012 at 1:04 PM, Simone Tripodi >wrote: > > > Hi Mohammad, > > > > what about having SVN+Git mirror? I personally just need a SCM, don't > > have a strong preference, so recommendations are more than welcome! > > What do you suggest? > > > > Many thanks in advance, all the best! > > -Simo > > > > http://people.apache.org/~simonetripodi/ > > http://simonetripodi.livejournal.com/ > > http://twitter.com/simonetripodi > > http://www.99soft.org/ > > > > > > On Thu, Nov 1, 2012 at 11:11 AM, Mohammad Nour El-Din > > wrote: > > > Hi > > > > > > I noticed that the code is hosted on github but u r asking for an svn > > rep > > > while we can have a git repo, or u don't want to continue using git ? > > > > > > Sent from my Samsung Galaxy S3 > > > Apologies for any typos > > > On Nov 1, 2012 11:59 AM, "Mohammad Nour El-Din" < > nour.moham...@gmail.com > > > > > > wrote: > > >> > > >> Hi Simone > > >> > > >>I like the idea pretty much and I would like to be a mentor of this > > > project. But I can't edit the wiki page at the moment would u please > add > > me > > > :) > > >> Thanks for bringing the project to ASF > > >> > > >> Sent from my Samsung Galaxy S3 > > >> Apologies for any typos > > >> > > >> On Nov 1, 2012 10:30 AM, "Eric Charles" wrote: > > >> > > > >> > I was waiting this since a long time, especially since guiceyfruit > is > > > not officially update to guice3. > > >> > > > >> > It's great time to do this, as more well-known 3rd parties provide > > > their own extensions [1]. With such a good code base coming from 99soft > > > foundation, we will be good on track. > > >> > > > >> > Big +1 and thx again, > > >> > > > >> > Eric > > >> > > > >> > [1] > > > > > > http://techblog.netflix.com/2012/10/governator-lifecycle-and-dependency.html > > >> > > > >> > > > >> > On 31/10/2012 22:16, Christian Grobmeier wrote: > > >> >> > > >> >> I like that proposal (you have guessed it as I signed up to > mentor). > > >> >> Guice is something cool as I found out recently. And I really like > > the > > >> >> logging component in there (surprise) > > >> >> > > >> >> > > >> >> On Wed, Oct 31, 2012 at 8:55 PM, Donald Whytock < > dwhyt...@gmail.com> > > > wrote: > > >> >> > > >> >>> Just giving a post-hurricane nudge. > > >> >>> > > >> >>> On Tue, Oct 30, 2012 at 11:49 AM, Simone Tripodi > > >> >>> wrote: > > >> > > >> Hi all guys, > > >> > > >> I prepared a new proposal[1] for the incubator, concerning the > > >> creation of a new community focused on all aspects of Google > Guice > > >> extensions, starting from a rather than small codebase that I and > > >> other friends - already ASF committers/members - would like to > > donate > > >> to the ASF. > > >> > > >> We still need at least one mentor, is there any volunteer > available > > > on > > >> joining to provide help on bringing that new community up? > > >> > > >> Many thanks in advance, all the best!!! > > >> -Simo > > >> > > >> [1] http://wiki.apache.org/incubator/MayhemProposal > > >> > > >> http://people.apache.org/~simonetripodi/ > > >> http://simonetripodi.livejournal.com/ > > >> http://twitter.com/simonetripodi > > >> http://www.99soft.org/ > > >> > > >> > > - > > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > >> For additional commands, e-mail: > general-h...@incubator.apache.org > > >> > > >> >>> > > >> >>> > > - > > >> >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > >> >>> For additional commands, e-mail: > general-h...@incubator.apache.org > > >> >>> > > >> >>> > > >> >> > > >> >> > > >> > > > >> > > - > > >> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > >> > For additional commands, e-mail: general-h...@incubator.apache.org > > >> > > > > > ---
Re: Karma for incubator wiki
Apologize. My bad, I first gave my Jira Id and then Apache Id. I dint realize there was a separate username for wiki. I created one now and it worked. On Wed, Dec 5, 2012 at 5:17 PM, Marvin Humphrey wrote: > On Wed, Dec 5, 2012 at 4:56 PM, kishore g wrote: > > Can some one grant me access to incubator wiki to update podling report. > My > > apache id is kishoreg. > > I added you as "k4j" in response to your requrest on October 11, then David > Crossley added you as "kishoreg" in response to your updated request on > October 21. > > http://markmail.org/message/xr77lgmfuv3usjws > > The wiki login "kishoreg" is still there in > <http://wiki.apache.org/incubator/ContributorsGroup>. Things ought to > work. > > Marvin Humphrey > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
[VOTE] Apache Helix 0.6.0-incubating release [RC3]
Hi, This is to call for a vote on releasing the following candidate as Apache Helix 0.6.0-incubating. This is the third release candidate of our first release at Apache. Apache Helix is a generic cluster management framework that makes it easy to build partitioned and replicated, fault tolerant and scalable distributed systems. Release notes: http://helix.incubator.apache.org/releasenotes/release-0.6.0-incubating.html Our vote thread on helix-dev: http://mail-archives.apache.org/mod_mbox/helix-dev/201301.mbox/%3CCABaj-QZdZkNA7CAsbciokYBNBWSJwQ_LkBRaoju7Pa56h12S9A%40mail.gmail.com%3E The following IPMC members have voted +1 Patrick Hunt Olivier Lamy Mahadev Konar Release artifacts: https://repository.apache.org/content/repositories/orgapachehelix-121 Distribution: * binaries: https://dist.apache.org/repos/dist/dev/incubator/helix/0.6.0-incubating/binaries/ * sources: https://dist.apache.org/repos/dist/dev/incubator/helix/0.6.0-incubating/src/ The 0.6.0-incubating release tag https://git-wip-us.apache.org/repos/asf?p=incubator-helix.git;a=commit;h=2e7f33d8fae7e3049a4bf0d909d7135d28fc16ee KEYS file available here: https://dist.apache.org/repos/dist/release/incubator/helix/KEYS Please vote on the release. The vote will be open for 72 hours. Thanks, Apache Helix team.
[RESULT][VOTE] Apache Helix 0.6.0-incubating release [RC3]
Hi, Closing the vote since its past 72 hours. Here is the result. Patrick Hunt( Binding) Olivier Lamy(Binding) Mahadev Konar(Binding) The vote passed with 3 binding votes. Thanks to the mentors for support. thanks, Helix team On Fri, Jan 25, 2013 at 1:11 PM, kishore g wrote: > Hi, > > This is to call for a vote on releasing the following candidate as Apache > Helix 0.6.0-incubating. This is the third release candidate of our first > release at Apache. > > Apache Helix is a generic cluster management framework that makes it easy > to build partitioned and replicated, fault tolerant and scalable > distributed systems. > > Release notes: > > http://helix.incubator.apache.org/releasenotes/release-0.6.0-incubating.html > > Our vote thread on helix-dev: > > http://mail-archives.apache.org/mod_mbox/helix-dev/201301.mbox/%3CCABaj-QZdZkNA7CAsbciokYBNBWSJwQ_LkBRaoju7Pa56h12S9A%40mail.gmail.com%3E > > The following IPMC members have voted +1 > Patrick Hunt > Olivier Lamy > Mahadev Konar > > > Release artifacts: > https://repository.apache.org/content/repositories/orgapachehelix-121 > > Distribution: > * binaries: > https://dist.apache.org/repos/dist/dev/incubator/helix/0.6.0-incubating/binaries/ > * sources: > https://dist.apache.org/repos/dist/dev/incubator/helix/0.6.0-incubating/src/ > > The 0.6.0-incubating release tag > > https://git-wip-us.apache.org/repos/asf?p=incubator-helix.git;a=commit;h=2e7f33d8fae7e3049a4bf0d909d7135d28fc16ee > > KEYS file available here: > https://dist.apache.org/repos/dist/release/incubator/helix/KEYS > > Please vote on the release. The vote will be open for 72 hours. > > > Thanks, > Apache Helix team. > >
Re: [VOTE] Accept Provisionr into the Apache Incubator
+1 (non-binding) Good luck On Sun, Mar 3, 2013 at 11:05 PM, Ashish wrote: > +1 (non-binding) > > > On Sun, Mar 3, 2013 at 5:05 AM, Andrei Savu wrote: > > > Hi Guys, > > > > I'd like to call a VOTE for acceptance of Provisionr into the Apache > > Incubator. > > > > The vote will close on March 8. > > > > [] +1 Accept Provisionr into the Apache incubator > > [] +0 Don't care. > > [] -1 Don't accept Provisionr into the incubator because... > > > > Full proposal is pasted at the bottom on this email, and the > corresponding > > wiki is http://wiki.apache.org/incubator/ProvisionrProposal > > > > Only VOTEs from Incubator PMC members are binding, but all are welcome to > > express their thoughts. > > > > Thanks, > > Andrei Savu > > > > -- > > Provisionr Proposal > > > > == Abstract == > > > > Provisionr is an effort to develop a service that can be used to create > and > > manage pools of virtual machines on multiple clouds. Our focus is on > > semi-automated workflows and cloud portability. > > > > == Proposal == > > > > Provisionr solves the problem of cloud portability by hiding completely > the > > APIs and only focusing on building a cluster that matches the same set of > > assumptions on all clouds, assumptions like: running a specific operating > > system (e.g. Ubuntu 12.04 LTS), having the same set of pre-installed > > packages and binaries, sane dns settings (forward & reverse ip > resolution - > > as needed for Hadoop), ntp settings, networking settings, firewall, ssh > > admin access, vpn access etc. > > > > As a secondary goal Provisionr should also provide primitives for > building > > automatic or semi-automatic workflows for configuring services, workflows > > that assume that all the machines share a common set of characteristics > as > > described above. > > > > == Background == > > > > Creating clusters on cloud infrastructure is non-trivial because careful > > orchestration is required. To make it easy to deploy services we need to > > start from a foundation that matches a common set of assumptions on > > multiple providers. > > > > == Rationale == > > > > This project started as a re-write of the core of Apache Whirr but has a > > different target being more focused on semi-automated workflows and cloud > > portability. > > > > == Initial Goals == > > > > * Build a community > > * Provide an excellent user experience for semi-automatic workflows > (e.g. > > using Rundeck) > > * Implement a REST service and a Web Console > > * Add support for more providers > > > > == Current Status == > > > > Provisionr had four releases on [[ > > https://github.com/axemblr/axemblr-provisionr/wiki|GitHub]] and it's > used > > to deploy Hadoop clusters on-demand at Axemblr and infrastructure for > > testing / QA. > > > > === 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 community interested in cloud service infrastructure is currently > > spread across many smaller projects, and one of the main goals of this > > project is to build a vibrant community to share best practices and build > > common infrastructure. > > > > === Core developers === > > > > Core developers are very experienced in the Apache ecosystem. To achieve > > more diversity of developers, we will be eager to recruit developers from > > diverse companies. > > > > * Andrei Savu - asavu at apache dot org (Apache Whirr PMC) > > * Ioan Eugen Stan - ieugen at apache dot org (Apache James PMC) > > * Alex Ciminian - alex.ciminian at gmail dot org > > > > === Alignment === > > > > Provisionr complements Apache Whirr and later on it should provide a > robust > > foundation for more advanced functionalities. > > > > == Known Risks == > > > > === Orphaned products === > > > > The contributors have significant open source experience and the project > is > > being used as part of a commercial product, so the risk of being orphaned > > is relatively low. We plan to mitigate this risk by recruiting additional > > committers. > > > > === Inexperience with Open Source === > > > > Most of the initial committers have experience working on open source > > projects. Andrei Savu and Ioan Eugen Stan have experience as committers > and > > PMC members on other Apache projects. > > > > === Homogenous Developers === > > > > We are committed to recruiting additional committers from other companies > > based on their contributions to the project. > > > > === Reliance on Salaried Developers === > > > > It is expected that Provisionr development will occur on both salaried > time > > and on volunteer time, after hours. The majority of initial committers > are > > paid by their em
Re: [VOTE] S4 0.6.0 Incubating Release Candidate 5
+1 verified sigs built code, tools and ran tests rat check passed Thanks, Kishore G On Mon, May 6, 2013 at 5:37 AM, Matthieu Morel wrote: > Hello, > > this is the *fifth* release candidate for Apache S4, version 0.6.0 > > We fixed 2 blocking issues wrt RC1, related to s4 tools, 1 blocking issue > in RC2, related to metrics logging configuration, issues related to the > package contents and license headers in RC3, and removed included javadoc > files in RC4. > > > > This release fixes the following issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312322&version=12321702 > > > *** Please download, test and vote by Thursday, May 9th 2013, 13:00:00 GMT > *** > > > Note that we are voting upon the source (tag). > > > Source package in zip format: > > http://people.apache.org/~mmorel/s4-0.6.0-incubating-release-candidate-5/ > > > > The (git) tag to be voted upon: 0.6.0-RC5: > > > https://git-wip-us.apache.org/repos/asf?p=incubator-s4.git;a=tree;h=8b43b317104cfc9ebc42f6e8ec9c9557867155aa;hb=2f474503e2da111601bb92ca7186c136ba28e5b0 > > > > S4 KEYS file containing PGP keys we use to sign the release: > > http://svn.apache.org/repos/asf/incubator/s4/dist/KEYS > > > The README.md file contains instructions for installing the gradle wrapper > (which is not shipped with the source release). > > > We include a RAT check task. (Can be used by fetching rat from /lib dir in > the git repo and using the .rat-excludes file at the root of the git repo) > > It can be run with : > gradlew rat > output > > > Please cast your vote, thanks! > > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > > > NOTES: > > - All releases by podlings must be approved by the Incubator PMC. The > conventional process is for the podling to follow the usual Apache process > and then call for a Incubator PMC VOTE on the general incubator list. > For RC5 however, following recommendations from our mentors, we are > proceeding to a parallel vote on both general@incubator and s4-dev > >
Re: [VOTE] helix 0.6.1-incubating
Hi Henry, You are right. It is supposed to be https://repository.apache.org/content/repositories/orgapachehelix-021, we had the correct url original email sent to dev. http://markmail.org/message/xymuvmcjxobmhjd3?q=+list:org%2Eapache%2Ehelix%2Edev . Thanks for pointing this. Thanks, Kishore G On Sun, May 19, 2013 at 6:23 PM, Henry Saputra wrote: > Looks like the release artifact does not exist: > https://repository.apache.org/content/repositories/orgapachehelix-121 > > Is it suppose to be > https://repository.apache.org/content/repositories/orgapachehelix-021 ? > > - Henry > > > On Sun, May 12, 2013 at 12:18 AM, Shi Lu wrote: > > > Hi, > > > > This is to call for a vote on releasing the following candidate as Apache > > Helix 0.6.1-incubating. This is the first release candidate of our second > > release at Apache. > > > > Apache Helix is a generic cluster management framework that makes it easy > > to build partitioned and replicated, fault tolerant and scalable > > distributed systems. > > > > Release notes: > > > > > http://helix.incubator.apache.org/releasenotes/release-0.6.1-incubating.html > > > > Our vote thread on helix-dev: > > > > > http://markmail.org/message/xymuvmcjxobmhjd3?q=+list:org%2Eapache%2Ehelix%2Edev > > > > The following IPMC members have voted +1 > > Patrick Hunt > > Olivier Lamy > > > > > > Release artifacts: > > https://repository.apache.org/content/repositories/orgapachehelix-121 > > > > Distribution: > > * binaries: > > > > > https://dist.apache.org/repos/dist/dev/incubator/helix/0.6.1-incubating/binaries/ > > * sources: > > > > > https://dist.apache.org/repos/dist/dev/incubator/helix/0.6.1-incubating/src/ > > > > > > The 0.6.1-incubating release tag > > > > > https://git-wip-us.apache.org/repos/asf?p=incubator-helix.git;a=commit;h=355d1692a9036fa8741ef828db45446515ff018f > > > > KEYS file available here: > > https://dist.apache.org/repos/dist/release/incubator/helix/KEYS > > > > Please vote on the release. The vote will be open for 72 hours. > > > > Thanks, > > Apache Helix team. > > >
[DISCUSS] Apache Pinot Incubator Proposal
Hello, I would like to propose Pinot as an Apache Incubator project. The proposal is available as a draft at https://wiki.apache.org/incubator/PinotProposal. I have also included the text of the proposal below. Any feedback from the community is much appreciated. Regards, Kishore G = Pinot Proposal = == Abstract == Pinot is a distributed columnar storage engine that can ingest data in real-time and serve analytical queries at low latency. There are two modes of data ingestion - batch and/or realtime. Batch mode allows users to generate pinot segments externally using systems such as Hadoop. These segments can be uploaded into Pinot via simple curl calls. Pinot can ingest data in near real-time from streaming sources such as Kafka. Data ingested into Pinot is stored in a columnar format. Pinot provides a SQL like interface (PQL) that supports filters, aggregations, and group by operations. It does not support joins by design, in order to guarantee predictable latency. It leverages other Apache projects such as Zookeeper, Kafka, and Helix, along with many libraries from the ASF. == Proposal == Pinot was open sourced by LinkedIn and hosted on GitHub. Majority of the development happens at LinkedIn with other contributions from Uber and Slack. We believe that being a part of Apache Software Foundation will improve the diversity and help form a strong community around the project. LinkedIn submits this proposal to donate the code base to Apache Software Foundation. The code is already under Apache License 2.0. Code and the documentation are hosted on Github. * Code: http://github.com/linkedin/pinot * Documentation: https://github.com/linkedin/pinot/wiki == Background == LinkedIn, similar to other companies, has many applications that provide rich real-time insights to members and customers (internal and external). The workload characteristics for these applications vary a lot. Some internal applications simply need ad-hoc query capabilities with sub-second to multiple seconds latency. But external site facing applications require strong SLA even very high workloads. Prior to Pinot, LinkedIn had multiple solutions depending on the workload generated by the application and this was inefficient. Pinot was developed to be the one single platform that addresses all classes of applications. Today at LinkedIn, Pinot powers more than 50 site facing products with workload ranging from few queries per second to 1000’s of queries per second while maintaining the 99th percentile latency which can be as low as few milliseconds. All internal dashboards at LinkedIn are powered by Pinot. == Rationale == We believe that requirement to develop rich real-time analytic applications is applicable to other organizations. Both Pinot and the interested communities would benefit from this work being openly available. == Current Status == Pinot is currently open sourced under the Apache License Version 2.0 and available at github.com/linkedin/pinot. All the development is done using GitHub Pull Requests. We cut releases on a weekly basis and deploy it at LinkedIn. mp-0.1.468 is the latest release tag that is deployed in production. == Meritocracy == Following the Apache meritocracy model, we intend to build an open and diverse community around Pinot. We will encourage the community to contribute to discussion and codebase. == Community == Pinot is currently used extensively at LinkedIn and Uber. Several companies have expressed interest in the project. We hope to extend the contributor base significantly by bringing Pinot into Apache. == Core Developers == Pinot was started by engineers at LinkedIn, and now has committers from Uber. == Alignment == Apache is the most natural home for taking Pinot forward. Pinot leverages several existing Apache Projects such as Kafka, Helix, Zookeeper, and Avro. As Pinot gains adoption, we plan to add support for the ORC and Parquet formats, as well as adding integration with Yarn and Mesos. == Known Risks == === Orphaned Products === The risk of the Pinot project being abandoned is minimal. The teams at LinkedIn and Uber are highly incentivized to continue development of Pinot as it is a critical part of their infrastructure. === Inexperience with Open Source === Post open sourcing, Pinot was completely developed on GitHub. All the current developers on Pinot are well aware of the open source development process. However, most of the developers are new to the Apache process. Kishore Gopalakrishna, one of the lead developers in Pinot, is VP and committer of the Apache Helix project. === Homogenous Developers === The current core developers are all from LinkedIn and Uber. However, we hope to establish a developer community that includes contributors from several corporations and we are actively encouraging new contributors via the mailing lists and public presentations of Pinot. === Reliance on Salaried Developers === It is expected that Pinot development will occur
Re: [DISCUSS] Apache Pinot Incubator Proposal
Kevin, Increasing the adoption of Pinot is one thing that can help build a good diverse community. Few things that come to my mind - Improve documentation - Better integration with cloud providers - Meetup and blog posts. We would also love to get additional mentors from ASF to help us build the community around Pinot. On Tue, Feb 13, 2018 at 4:29 PM, Timothy Chen wrote: > Love to see this in the incubator as well. +1 > > Tim > > On Tue, Feb 13, 2018 at 4:22 PM, Kevin A. McGrail > wrote: > > Agreed. It could use more mentors from ASF which I'm too overloaded to > help > > with but I'd be inclined to +1 this. Do you have some thoughts on > getting > > more community people outside of LI and Uber to help? > > > > On 2/13/2018 7:07 PM, Dave Fisher wrote: > >> > >> Noir or Blanc? Gris or Grigio? What’s the vintage? > >> > >> All kidding aside this looks interesting. > >> > >> Regards, > >> Dave > >> > >> Sent from my iPhone > >> > >>> On Feb 13, 2018, at 12:10 AM, kishore g wrote: > >>> > >>> Hello, > >>> > >>> I would like to propose Pinot as an Apache Incubator project. The > >>> proposal > >>> is available as a draft at > >>> https://wiki.apache.org/incubator/PinotProposal. I > >>> have also included the text of the proposal below. > >>> > >>> Any feedback from the community is much appreciated. > >>> > >>> Regards, > >>> Kishore G > >>> > >>> = Pinot Proposal = > >>> > >>> == Abstract == > >>> > >>> Pinot is a distributed columnar storage engine that can ingest data in > >>> real-time and serve analytical queries at low latency. There are two > >>> modes > >>> of data ingestion - batch and/or realtime. Batch mode allows users to > >>> generate pinot segments externally using systems such as Hadoop. These > >>> segments can be uploaded into Pinot via simple curl calls. Pinot can > >>> ingest > >>> data in near real-time from streaming sources such as Kafka. Data > >>> ingested > >>> into Pinot is stored in a columnar format. Pinot provides a SQL like > >>> interface (PQL) that supports filters, aggregations, and group by > >>> operations. It does not support joins by design, in order to guarantee > >>> predictable latency. It leverages other Apache projects such as > >>> Zookeeper, > >>> Kafka, and Helix, along with many libraries from the ASF. > >>> > >>> == Proposal == > >>> > >>> Pinot was open sourced by LinkedIn and hosted on GitHub. Majority of > the > >>> development happens at LinkedIn with other contributions from Uber and > >>> Slack. We believe that being a part of Apache Software Foundation will > >>> improve the diversity and help form a strong community around the > >>> project. > >>> > >>> LinkedIn submits this proposal to donate the code base to Apache > Software > >>> Foundation. The code is already under Apache License 2.0. Code and the > >>> documentation are hosted on Github. > >>> * Code: http://github.com/linkedin/pinot > >>> * Documentation: https://github.com/linkedin/pinot/wiki > >>> > >>> > >>> == Background == > >>> > >>> LinkedIn, similar to other companies, has many applications that > provide > >>> rich real-time insights to members and customers (internal and > external). > >>> The workload characteristics for these applications vary a lot. Some > >>> internal applications simply need ad-hoc query capabilities with > >>> sub-second > >>> to multiple seconds latency. But external site facing applications > >>> require > >>> strong SLA even very high workloads. Prior to Pinot, LinkedIn had > >>> multiple > >>> solutions depending on the workload generated by the application and > this > >>> was inefficient. Pinot was developed to be the one single platform that > >>> addresses all classes of applications. Today at LinkedIn, Pinot powers > >>> more > >>> than 50 site facing products with workload ranging from few queries per > >>> second to 1000’s of queries per second while maintaining the 99th > >>> percentile latency which can be as low as few milliseconds. All > internal > >>> dash
[VOTE] Accept Pinot into Apache Incubator
Hi all, I would like to call a VOTE to accept Pinot into the Apache Incubator. The full proposal is available on the wiki <https://wiki.apache.org/incubator/PinotProposal> Please cast your vote: [ ] +1, bring Pinot into Incubator [ ] +0, I don't care either way, [ ] -1, do not bring Pinot into Incubator, because... The vote will open at least for 72 hours and only votes from the Incubator PMC are binding. Thanks, Kishore G Discussion thread: https://lists.apache.org/thread.html/8119f9478ea1811371f1bf6685290b22b57b1a3e0849d1d778d77dcb@%3Cgeneral.incubator.apache.org = Pinot Proposal = == Abstract == Pinot is a distributed columnar storage engine that can ingest data in real-time and serve analytical queries at low latency. There are two modes of data ingestion - batch and/or realtime. Batch mode allows users to generate pinot segments externally using systems such as Hadoop. These segments can be uploaded into Pinot via simple curl calls. Pinot can ingest data in near real-time from streaming sources such as Kafka. Data ingested into Pinot is stored in a columnar format. Pinot provides a SQL like interface (PQL) that supports filters, aggregations, and group by operations. It does not support joins by design, in order to guarantee predictable latency. It leverages other Apache projects such as Zookeeper, Kafka, and Helix, along with many libraries from the ASF. == Proposal == Pinot was open sourced by LinkedIn and hosted on GitHub. Majority of the development happens at LinkedIn with other contributions from Uber and Slack. We believe that being a part of Apache Software Foundation will improve the diversity and help form a strong community around the project. LinkedIn submits this proposal to donate the code base to Apache Software Foundation. The code is already under Apache License 2.0. Code and the documentation are hosted on Github. * Code: http://github.com/linkedin/pinot * Documentation: https://github.com/linkedin/pinot/wiki == Background == LinkedIn, similar to other companies, has many applications that provide rich real-time insights to members and customers (internal and external). The workload characteristics for these applications vary a lot. Some internal applications simply need ad-hoc query capabilities with sub-second to multiple seconds latency. But external site facing applications require strong SLA even very high workloads. Prior to Pinot, LinkedIn had multiple solutions depending on the workload generated by the application and this was inefficient. Pinot was developed to be the one single platform that addresses all classes of applications. Today at LinkedIn, Pinot powers more than 50 site facing products with workload ranging from few queries per second to 1000’s of queries per second while maintaining the 99th percentile latency which can be as low as few milliseconds. All internal dashboards at LinkedIn are powered by Pinot. == Rationale == We believe that requirement to develop rich real-time analytic applications is applicable to other organizations. Both Pinot and the interested communities would benefit from this work being openly available. == Current Status == Pinot is currently open sourced under the Apache License Version 2.0 and available at github.com/linkedin/pinot. All the development is done using GitHub Pull Requests. We cut releases on a weekly basis and deploy it at LinkedIn. mp-0.1.468 is the latest release tag that is deployed in production. == Meritocracy == Following the Apache meritocracy model, we intend to build an open and diverse community around Pinot. We will encourage the community to contribute to discussion and codebase. == Community == Pinot is currently used extensively at LinkedIn and Uber. Several companies have expressed interest in the project. We hope to extend the contributor base significantly by bringing Pinot into Apache. == Core Developers == Pinot was started by engineers at LinkedIn, and now has committers from Uber. == Alignment == Apache is the most natural home for taking Pinot forward. Pinot leverages several existing Apache Projects such as Kafka, Helix, Zookeeper, and Avro. As Pinot gains adoption, we plan to add support for the ORC and Parquet formats, as well as adding integration with Yarn and Mesos. == Known Risks == === Orphaned Products === The risk of the Pinot project being abandoned is minimal. The teams at LinkedIn and Uber are highly incentivized to continue development of Pinot as it is a critical part of their infrastructure. === Inexperience with Open Source === Post open sourcing, Pinot was completely developed on GitHub. All the current developers on Pinot are well aware of the open source development process. However, most of the developers are new to the Apache process. Kishore Gopalakrishna, one of the lead developers in Pinot, is VP and committer of the Apache Helix project. === Homogenous Developers === The current core developers are all from Linked
Re: [DISCUSS] Apache Pinot Incubator Proposal
@John, will start that process asap. @Felix Yes, we are looking for mentors. I can remove myself since I will be actively participating the project anyways. On Fri, Mar 9, 2018 at 8:58 AM, Felix Cheung wrote: > Hi Kishore - do you need one more mentor? > > > On Tue, Feb 13, 2018 at 12:10 AM kishore g wrote: > > > Hello, > > > > I would like to propose Pinot as an Apache Incubator project. The > proposal > > is available as a draft at https://wiki.apache.org/ > incubator/PinotProposal. > > I > > have also included the text of the proposal below. > > > > Any feedback from the community is much appreciated. > > > > Regards, > > Kishore G > > > > = Pinot Proposal = > > > > == Abstract == > > > > Pinot is a distributed columnar storage engine that can ingest data in > > real-time and serve analytical queries at low latency. There are two > modes > > of data ingestion - batch and/or realtime. Batch mode allows users to > > generate pinot segments externally using systems such as Hadoop. These > > segments can be uploaded into Pinot via simple curl calls. Pinot can > ingest > > data in near real-time from streaming sources such as Kafka. Data > ingested > > into Pinot is stored in a columnar format. Pinot provides a SQL like > > interface (PQL) that supports filters, aggregations, and group by > > operations. It does not support joins by design, in order to guarantee > > predictable latency. It leverages other Apache projects such as > Zookeeper, > > Kafka, and Helix, along with many libraries from the ASF. > > > > == Proposal == > > > > Pinot was open sourced by LinkedIn and hosted on GitHub. Majority of the > > development happens at LinkedIn with other contributions from Uber and > > Slack. We believe that being a part of Apache Software Foundation will > > improve the diversity and help form a strong community around the > project. > > > > LinkedIn submits this proposal to donate the code base to Apache Software > > Foundation. The code is already under Apache License 2.0. Code and the > > documentation are hosted on Github. > > * Code: http://github.com/linkedin/pinot > > * Documentation: https://github.com/linkedin/pinot/wiki > > > > > > == Background == > > > > LinkedIn, similar to other companies, has many applications that provide > > rich real-time insights to members and customers (internal and external). > > The workload characteristics for these applications vary a lot. Some > > internal applications simply need ad-hoc query capabilities with > sub-second > > to multiple seconds latency. But external site facing applications > require > > strong SLA even very high workloads. Prior to Pinot, LinkedIn had > multiple > > solutions depending on the workload generated by the application and this > > was inefficient. Pinot was developed to be the one single platform that > > addresses all classes of applications. Today at LinkedIn, Pinot powers > more > > than 50 site facing products with workload ranging from few queries per > > second to 1000’s of queries per second while maintaining the 99th > > percentile latency which can be as low as few milliseconds. All internal > > dashboards at LinkedIn are powered by Pinot. > > > > == Rationale == > > > > We believe that requirement to develop rich real-time analytic > applications > > is applicable to other organizations. Both Pinot and the interested > > communities would benefit from this work being openly available. > > > > == Current Status == > > > > Pinot is currently open sourced under the Apache License Version 2.0 and > > available at github.com/linkedin/pinot. All the development is done > using > > GitHub Pull Requests. We cut releases on a weekly basis and deploy it at > > LinkedIn. mp-0.1.468 is the latest release tag that is deployed in > > production. > > > > == Meritocracy == > > > > Following the Apache meritocracy model, we intend to build an open and > > diverse community around Pinot. We will encourage the community to > > contribute to discussion and codebase. > > > > == Community == > > > > Pinot is currently used extensively at LinkedIn and Uber. Several > companies > > have expressed interest in the project. We hope to extend the contributor > > base significantly by bringing Pinot into Apache. > > > > == Core Developers == > > > > Pinot was started by engineers at LinkedIn, and now has committers from > > Uber. > > > > == Alignment == >
Re: [DISCUSS] Apache Pinot Incubator Proposal
Thanks Jim. I will update the proposal. On Fri, Mar 9, 2018 at 1:37 PM, Jim Jagielski wrote: > If still looking for mentors, I'll throw my hat in. > > > On Mar 9, 2018, at 1:19 PM, kishore g wrote: > > > > @John, will start that process asap. > > > > @Felix Yes, we are looking for mentors. I can remove myself since I will > be > > actively participating the project anyways. > > > > On Fri, Mar 9, 2018 at 8:58 AM, Felix Cheung > wrote: > > > >> Hi Kishore - do you need one more mentor? > >> > >> > >> On Tue, Feb 13, 2018 at 12:10 AM kishore g wrote: > >> > >>> Hello, > >>> > >>> I would like to propose Pinot as an Apache Incubator project. The > >> proposal > >>> is available as a draft at https://wiki.apache.org/ > >> incubator/PinotProposal. > >>> I > >>> have also included the text of the proposal below. > >>> > >>> Any feedback from the community is much appreciated. > >>> > >>> Regards, > >>> Kishore G > >>> > >>> = Pinot Proposal = > >>> > >>> == Abstract == > >>> > >>> Pinot is a distributed columnar storage engine that can ingest data in > >>> real-time and serve analytical queries at low latency. There are two > >> modes > >>> of data ingestion - batch and/or realtime. Batch mode allows users to > >>> generate pinot segments externally using systems such as Hadoop. These > >>> segments can be uploaded into Pinot via simple curl calls. Pinot can > >> ingest > >>> data in near real-time from streaming sources such as Kafka. Data > >> ingested > >>> into Pinot is stored in a columnar format. Pinot provides a SQL like > >>> interface (PQL) that supports filters, aggregations, and group by > >>> operations. It does not support joins by design, in order to guarantee > >>> predictable latency. It leverages other Apache projects such as > >> Zookeeper, > >>> Kafka, and Helix, along with many libraries from the ASF. > >>> > >>> == Proposal == > >>> > >>> Pinot was open sourced by LinkedIn and hosted on GitHub. Majority of > the > >>> development happens at LinkedIn with other contributions from Uber and > >>> Slack. We believe that being a part of Apache Software Foundation will > >>> improve the diversity and help form a strong community around the > >> project. > >>> > >>> LinkedIn submits this proposal to donate the code base to Apache > Software > >>> Foundation. The code is already under Apache License 2.0. Code and the > >>> documentation are hosted on Github. > >>> * Code: http://github.com/linkedin/pinot > >>> * Documentation: https://github.com/linkedin/pinot/wiki > >>> > >>> > >>> == Background == > >>> > >>> LinkedIn, similar to other companies, has many applications that > provide > >>> rich real-time insights to members and customers (internal and > external). > >>> The workload characteristics for these applications vary a lot. Some > >>> internal applications simply need ad-hoc query capabilities with > >> sub-second > >>> to multiple seconds latency. But external site facing applications > >> require > >>> strong SLA even very high workloads. Prior to Pinot, LinkedIn had > >> multiple > >>> solutions depending on the workload generated by the application and > this > >>> was inefficient. Pinot was developed to be the one single platform that > >>> addresses all classes of applications. Today at LinkedIn, Pinot powers > >> more > >>> than 50 site facing products with workload ranging from few queries per > >>> second to 1000’s of queries per second while maintaining the 99th > >>> percentile latency which can be as low as few milliseconds. All > internal > >>> dashboards at LinkedIn are powered by Pinot. > >>> > >>> == Rationale == > >>> > >>> We believe that requirement to develop rich real-time analytic > >> applications > >>> is applicable to other organizations. Both Pinot and the interested > >>> communities would benefit from this work being openly available. > >>> > >>> == Current Status == > >>> > >>> Pinot is currently open sourced under the Ap
Re: [VOTE] Accept Pinot into Apache Incubator
Added Jim Jagielski to the mentor's list. On Fri, Mar 9, 2018 at 6:35 PM, Olivier Lamy wrote: > +1 > > On 9 March 2018 at 17:11, kishore g wrote: > > > Hi all, > > > > I would like to call a VOTE to accept Pinot into the Apache Incubator. > The > > full proposal is available on the wiki > > <https://wiki.apache.org/incubator/PinotProposal> > > > > Please cast your vote: > > > > [ ] +1, bring Pinot into Incubator > > [ ] +0, I don't care either way, > > [ ] -1, do not bring Pinot into Incubator, because... > > > > The vote will open at least for 72 hours and only votes from the > Incubator > > PMC are binding. > > > > Thanks, > > Kishore G > > > > Discussion thread: > > https://lists.apache.org/thread.html/8119f9478ea1811371f1bf6685290b > > 22b57b1a3e0849d1d778d77dcb@%3Cgeneral.incubator.apache.org > > > > > > = Pinot Proposal = > > > > == Abstract == > > > > Pinot is a distributed columnar storage engine that can ingest data in > > real-time and serve analytical queries at low latency. There are two > modes > > of data ingestion - batch and/or realtime. Batch mode allows users to > > generate pinot segments externally using systems such as Hadoop. These > > segments can be uploaded into Pinot via simple curl calls. Pinot can > ingest > > data in near real-time from streaming sources such as Kafka. Data > ingested > > into Pinot is stored in a columnar format. Pinot provides a SQL like > > interface (PQL) that supports filters, aggregations, and group by > > operations. It does not support joins by design, in order to guarantee > > predictable latency. It leverages other Apache projects such as > Zookeeper, > > Kafka, and Helix, along with many libraries from the ASF. > > > > == Proposal == > > > > Pinot was open sourced by LinkedIn and hosted on GitHub. Majority of the > > development happens at LinkedIn with other contributions from Uber and > > Slack. We believe that being a part of Apache Software Foundation will > > improve the diversity and help form a strong community around the > project. > > > > LinkedIn submits this proposal to donate the code base to Apache Software > > Foundation. The code is already under Apache License 2.0. Code and the > > documentation are hosted on Github. > > * Code: http://github.com/linkedin/pinot > > * Documentation: https://github.com/linkedin/pinot/wiki > > > > > > == Background == > > > > LinkedIn, similar to other companies, has many applications that provide > > rich real-time insights to members and customers (internal and external). > > The workload characteristics for these applications vary a lot. Some > > internal applications simply need ad-hoc query capabilities with > sub-second > > to multiple seconds latency. But external site facing applications > require > > strong SLA even very high workloads. Prior to Pinot, LinkedIn had > multiple > > solutions depending on the workload generated by the application and this > > was inefficient. Pinot was developed to be the one single platform that > > addresses all classes of applications. Today at LinkedIn, Pinot powers > more > > than 50 site facing products with workload ranging from few queries per > > second to 1000’s of queries per second while maintaining the 99th > > percentile latency which can be as low as few milliseconds. All internal > > dashboards at LinkedIn are powered by Pinot. > > > > == Rationale == > > > > We believe that requirement to develop rich real-time analytic > applications > > is applicable to other organizations. Both Pinot and the interested > > communities would benefit from this work being openly available. > > > > == Current Status == > > > > Pinot is currently open sourced under the Apache License Version 2.0 and > > available at github.com/linkedin/pinot. All the development is done > using > > GitHub Pull Requests. We cut releases on a weekly basis and deploy it at > > LinkedIn. mp-0.1.468 is the latest release tag that is deployed in > > production. > > > > == Meritocracy == > > > > Following the Apache meritocracy model, we intend to build an open and > > diverse community around Pinot. We will encourage the community to > > contribute to discussion and codebase. > > > > == Community == > > > > Pinot is currently used extensively at LinkedIn and Uber. Several > companies > > have expressed interest in the project. We hope to extend the contributo
Re: [VOTE] Accept Pinot into Apache Incubator
Hi, Want to revive this thread. Can I go ahead and close the vote and start the incubation process or should I start a new thread? thanks, Kishore G On Wed, Mar 21, 2018 at 6:47 PM Olivier Lamy wrote: > Hi > @Kishore I guess we have enough votes so maybe we can close the vote and > start the process? > > > On Wed, 14 Mar 2018 at 02:06, Kevin A. McGrail > wrote: > > > +1 binding. Apologies if this is a dupe. I thought I voted days ago. > > > > On Mar 9, 2018 02:11, "kishore g" wrote: > > > > > Hi all, > > > > > > I would like to call a VOTE to accept Pinot into the Apache Incubator. > > The > > > full proposal is available on the wiki > > > <https://wiki.apache.org/incubator/PinotProposal> > > > > > > Please cast your vote: > > > > > > [ ] +1, bring Pinot into Incubator > > > [ ] +0, I don't care either way, > > > [ ] -1, do not bring Pinot into Incubator, because... > > > > > > The vote will open at least for 72 hours and only votes from the > > Incubator > > > PMC are binding. > > > > > > Thanks, > > > Kishore G > > > > > > Discussion thread: > > > https://lists.apache.org/thread.html/8119f9478ea1811371f1bf6685290b > > > 22b57b1a3e0849d1d778d77dcb@%3Cgeneral.incubator.apache.org > > > > > > > > > = Pinot Proposal = > > > > > > == Abstract == > > > > > > Pinot is a distributed columnar storage engine that can ingest data in > > > real-time and serve analytical queries at low latency. There are two > > modes > > > of data ingestion - batch and/or realtime. Batch mode allows users to > > > generate pinot segments externally using systems such as Hadoop. These > > > segments can be uploaded into Pinot via simple curl calls. Pinot can > > ingest > > > data in near real-time from streaming sources such as Kafka. Data > > ingested > > > into Pinot is stored in a columnar format. Pinot provides a SQL like > > > interface (PQL) that supports filters, aggregations, and group by > > > operations. It does not support joins by design, in order to guarantee > > > predictable latency. It leverages other Apache projects such as > > Zookeeper, > > > Kafka, and Helix, along with many libraries from the ASF. > > > > > > == Proposal == > > > > > > Pinot was open sourced by LinkedIn and hosted on GitHub. Majority of > the > > > development happens at LinkedIn with other contributions from Uber and > > > Slack. We believe that being a part of Apache Software Foundation will > > > improve the diversity and help form a strong community around the > > project. > > > > > > LinkedIn submits this proposal to donate the code base to Apache > Software > > > Foundation. The code is already under Apache License 2.0. Code and the > > > documentation are hosted on Github. > > > * Code: http://github.com/linkedin/pinot > > > * Documentation: https://github.com/linkedin/pinot/wiki > > > > > > > > > == Background == > > > > > > LinkedIn, similar to other companies, has many applications that > provide > > > rich real-time insights to members and customers (internal and > external). > > > The workload characteristics for these applications vary a lot. Some > > > internal applications simply need ad-hoc query capabilities with > > sub-second > > > to multiple seconds latency. But external site facing applications > > require > > > strong SLA even very high workloads. Prior to Pinot, LinkedIn had > > multiple > > > solutions depending on the workload generated by the application and > this > > > was inefficient. Pinot was developed to be the one single platform that > > > addresses all classes of applications. Today at LinkedIn, Pinot powers > > more > > > than 50 site facing products with workload ranging from few queries per > > > second to 1000’s of queries per second while maintaining the 99th > > > percentile latency which can be as low as few milliseconds. All > internal > > > dashboards at LinkedIn are powered by Pinot. > > > > > > == Rationale == > > > > > > We believe that requirement to develop rich real-time analytic > > applications > > > is applicable to other organizations. Both Pinot and the interested > > > communities would benefit from this work being openly available. > > > > > &
Re: [VOTE] Accept Pinot into Apache Incubator
Thanks Justin. On Fri, Oct 12, 2018 at 6:08 PM Justin Mclean wrote: > Hi, > > And I think I've found one for you. He'll reply here a little later. > > Thanks, > Justin > > On Sat., 13 Oct. 2018, 8:30 am Justin Mclean, > wrote: > > > Hi, > > > > I'd like to see another mentor being added before calling a vote. > > > > Thanks, > > Justin > > > > On Sat., 13 Oct. 2018, 8:26 am kishore g, wrote: > > > >> Hi, > >> > >> Want to revive this thread. Can I go ahead and close the vote and start > >> the > >> incubation process or should I start a new thread? > >> > >> thanks, > >> Kishore G > >> > >> On Wed, Mar 21, 2018 at 6:47 PM Olivier Lamy wrote: > >> > >> > Hi > >> > @Kishore I guess we have enough votes so maybe we can close the vote > and > >> > start the process? > >> > > >> > > >> > On Wed, 14 Mar 2018 at 02:06, Kevin A. McGrail > >> > wrote: > >> > > >> > > +1 binding. Apologies if this is a dupe. I thought I voted days > ago. > >> > > > >> > > On Mar 9, 2018 02:11, "kishore g" wrote: > >> > > > >> > > > Hi all, > >> > > > > >> > > > I would like to call a VOTE to accept Pinot into the Apache > >> Incubator. > >> > > The > >> > > > full proposal is available on the wiki > >> > > > <https://wiki.apache.org/incubator/PinotProposal> > >> > > > > >> > > > Please cast your vote: > >> > > > > >> > > > [ ] +1, bring Pinot into Incubator > >> > > > [ ] +0, I don't care either way, > >> > > > [ ] -1, do not bring Pinot into Incubator, because... > >> > > > > >> > > > The vote will open at least for 72 hours and only votes from the > >> > > Incubator > >> > > > PMC are binding. > >> > > > > >> > > > Thanks, > >> > > > Kishore G > >> > > > > >> > > > Discussion thread: > >> > > > > https://lists.apache.org/thread.html/8119f9478ea1811371f1bf6685290b > >> > > > 22b57b1a3e0849d1d778d77dcb@%3Cgeneral.incubator.apache.org > >> > > > > >> > > > > >> > > > = Pinot Proposal = > >> > > > > >> > > > == Abstract == > >> > > > > >> > > > Pinot is a distributed columnar storage engine that can ingest > data > >> in > >> > > > real-time and serve analytical queries at low latency. There are > two > >> > > modes > >> > > > of data ingestion - batch and/or realtime. Batch mode allows users > >> to > >> > > > generate pinot segments externally using systems such as Hadoop. > >> These > >> > > > segments can be uploaded into Pinot via simple curl calls. Pinot > can > >> > > ingest > >> > > > data in near real-time from streaming sources such as Kafka. Data > >> > > ingested > >> > > > into Pinot is stored in a columnar format. Pinot provides a SQL > like > >> > > > interface (PQL) that supports filters, aggregations, and group by > >> > > > operations. It does not support joins by design, in order to > >> guarantee > >> > > > predictable latency. It leverages other Apache projects such as > >> > > Zookeeper, > >> > > > Kafka, and Helix, along with many libraries from the ASF. > >> > > > > >> > > > == Proposal == > >> > > > > >> > > > Pinot was open sourced by LinkedIn and hosted on GitHub. Majority > of > >> > the > >> > > > development happens at LinkedIn with other contributions from Uber > >> and > >> > > > Slack. We believe that being a part of Apache Software Foundation > >> will > >> > > > improve the diversity and help form a strong community around the > >> > > project. > >> > > > > >> > > > LinkedIn submits this proposal to donate the code base to Apache > >> > Software > >> > > > Foundation. The code is already under Apache License 2.0. Code > and > >> the > >
Re: [VOTE] Accept Pinot into Apache Incubator
Justin, I haven’t heard from anyone. We have Oliver and Jean so far. I can sign up as a mentor if it’s must. I will be involved with the project anyway. On Fri, Oct 12, 2018 at 9:29 PM kishore g wrote: > Thanks Justin. > > On Fri, Oct 12, 2018 at 6:08 PM Justin Mclean > wrote: > >> Hi, >> >> And I think I've found one for you. He'll reply here a little later. >> >> Thanks, >> Justin >> >> On Sat., 13 Oct. 2018, 8:30 am Justin Mclean, >> wrote: >> >> > Hi, >> > >> > I'd like to see another mentor being added before calling a vote. >> > >> > Thanks, >> > Justin >> > >> > On Sat., 13 Oct. 2018, 8:26 am kishore g, wrote: >> > >> >> Hi, >> >> >> >> Want to revive this thread. Can I go ahead and close the vote and start >> >> the >> >> incubation process or should I start a new thread? >> >> >> >> thanks, >> >> Kishore G >> >> >> >> On Wed, Mar 21, 2018 at 6:47 PM Olivier Lamy wrote: >> >> >> >> > Hi >> >> > @Kishore I guess we have enough votes so maybe we can close the vote >> and >> >> > start the process? >> >> > >> >> > >> >> > On Wed, 14 Mar 2018 at 02:06, Kevin A. McGrail >> >> > wrote: >> >> > >> >> > > +1 binding. Apologies if this is a dupe. I thought I voted days >> ago. >> >> > > >> >> > > On Mar 9, 2018 02:11, "kishore g" wrote: >> >> > > >> >> > > > Hi all, >> >> > > > >> >> > > > I would like to call a VOTE to accept Pinot into the Apache >> >> Incubator. >> >> > > The >> >> > > > full proposal is available on the wiki >> >> > > > <https://wiki.apache.org/incubator/PinotProposal> >> >> > > > >> >> > > > Please cast your vote: >> >> > > > >> >> > > > [ ] +1, bring Pinot into Incubator >> >> > > > [ ] +0, I don't care either way, >> >> > > > [ ] -1, do not bring Pinot into Incubator, because... >> >> > > > >> >> > > > The vote will open at least for 72 hours and only votes from the >> >> > > Incubator >> >> > > > PMC are binding. >> >> > > > >> >> > > > Thanks, >> >> > > > Kishore G >> >> > > > >> >> > > > Discussion thread: >> >> > > > >> https://lists.apache.org/thread.html/8119f9478ea1811371f1bf6685290b >> >> > > > 22b57b1a3e0849d1d778d77dcb@%3Cgeneral.incubator.apache.org >> >> > > > >> >> > > > >> >> > > > = Pinot Proposal = >> >> > > > >> >> > > > == Abstract == >> >> > > > >> >> > > > Pinot is a distributed columnar storage engine that can ingest >> data >> >> in >> >> > > > real-time and serve analytical queries at low latency. There are >> two >> >> > > modes >> >> > > > of data ingestion - batch and/or realtime. Batch mode allows >> users >> >> to >> >> > > > generate pinot segments externally using systems such as Hadoop. >> >> These >> >> > > > segments can be uploaded into Pinot via simple curl calls. Pinot >> can >> >> > > ingest >> >> > > > data in near real-time from streaming sources such as Kafka. Data >> >> > > ingested >> >> > > > into Pinot is stored in a columnar format. Pinot provides a SQL >> like >> >> > > > interface (PQL) that supports filters, aggregations, and group by >> >> > > > operations. It does not support joins by design, in order to >> >> guarantee >> >> > > > predictable latency. It leverages other Apache projects such as >> >> > > Zookeeper, >> >> > > > Kafka, and Helix, along with many libraries from the ASF. >> >> > > > >> >> > > > == Proposal == >> >> > > > >> >> > > > Pinot was open sourced by LinkedIn and hosted on GitHub. >> Majority of >> &
Re: [VOTE] Accept Pinot into Apache Incubator
Thanks Justin. Would love to have Roman as the mentor. I will close the vote and start the process. On Sat, Oct 13, 2018 at 3:31 PM Justin Mclean wrote: > Hi, > > > Justin, I haven’t heard from anyone. We have Oliver and Jean so far. I > can > > sign up as a mentor if it’s must. I will be involved with the project > > anyway. > > I spoke to Roman and he is interested in being a mentor, he is currently > travelling so probably hasn’t had a chance to respond. He can be added > after the vote, assuming you want him as a mentor for your project. > > Thanks, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Accept Pinot into Apache Incubator
72 hours have passed and the vote for accepting Pinot into Apache Incubator has passed with: 5 binding "+1" votes 2 non-binding "+1" votes No "0" or "-1" votes Binding Votes - Olivier Lamy - Carl Steinbach - Julian Hyde - William Jiang - Kevin A McGrail non-binding votes - Pierre Smits - Felix Cheung thanks, Kishore G On Sat, Oct 13, 2018 at 5:00 PM kishore g wrote: > Thanks Justin. Would love to have Roman as the mentor. I will close the > vote and start the process. > > On Sat, Oct 13, 2018 at 3:31 PM Justin Mclean wrote: > >> Hi, >> >> > Justin, I haven’t heard from anyone. We have Oliver and Jean so far. I >> can >> > sign up as a mentor if it’s must. I will be involved with the project >> > anyway. >> >> I spoke to Roman and he is interested in being a mentor, he is currently >> travelling so probably hasn’t had a chance to respond. He can be added >> after the vote, assuming you want him as a mentor for your project. >> >> Thanks, >> Justin >> - >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >>
Re: [VOTE] Apache Pinot (incubating) 0.7.0 RC1
Apologies for the mistake. We have done multiple releases until now and this is the first time we missed the step to get the approval from IPMC was missed before making the release. What is the right thing to do at this point? Should we cut another release or can we go ahead with this and ensure that this does not happen again. thanks, Kishore G On Wed, Mar 17, 2021 at 10:59 AM Felix Cheung wrote: > Unfortunately this isn’t the right process for a podling release. > > As the mentor, I am sorry to see the release is not up to the standard > upheld by previous releases. > > > On Wed, Mar 17, 2021 at 7:02 AM kezhenxu94@apache > wrote: > > > I think this release violates the Apache release policy because it didn’t > > get the approvals from IPMC but was released actually (in both dist.a.o > and > > GitHub). > > > > — > > Zhenxu Ke (柯振旭) > > GitHub @kezhenxu94 > > > > > On Mar 17, 2021, at 06:14, Yupeng Fu wrote: > > > > > > Hi all, > > > > > > This is a call for vote to the release Apache Pinot (incubating) > version > > > 0.7.0. > > > > > > Apache Pinot (incubating) is a distributed columnar storage engine that > > can > > > ingest data in realtime and serve analytical queries at low latency. > > > > > > Pinot community has voted and approved this release. > > > > > > Vote thread: > > > > > > https://lists.apache.org/thread.html/r850cee1e6fc23804d161a31d465e30d5d12b7a4e1cc8035264ea91d6%40%3Cdev.pinot.apache.org%3E > > > > > > > > > Result thread: > > > > > > https://lists.apache.org/thread.html/r80672ac39a6a6eb7f63c7dbbf595de2f7350cf75d2a7a598601da638%40%3Cdev.pinot.apache.org%3E > > > > > > The release candidate: > > > > > > https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.7.0-rc1/ > > > > > > > > > Git tag for this release: > > > <https://github.com/apache/incubator-pinot/tree/release-0.7.0-rc0> > > > https://github.com/apache/incubator-pinot/tree/release-0.7.0-rc1 > > > > > > Git hash for this release: > > > 695ca390a8080409b3b76f250f2315b81b86b362 > > > > > > The artifacts have been signed with key: F41AB2B856C6C29D, which can be > > > found in the following KEYS file. > > > https://dist.apache.org/repos/dist/release/incubator/pinot/KEYS > > > > > > Release notes: > > > > https://github.com/apache/incubator-pinot/releases/tag/release-0.7.0-rc1 > > > > > > Staging repository: > > > < > https://repository.apache.org/content/repositories/orgapachepinot-1023> > > > https://repository.apache.org/content/repositories/orgapachepinot-1024 > > > > > > Documentation on verifying a release candidate: > > > > > > https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate > > > > > > > > > The vote will be open for at least 72 hours or until the necessary > > number of > > > votes are reached. > > > > > > Please vote accordingly, > > > > > > [ ] +1 approve > > > [ ] +0 no opinion > > > [ ] -1 disapprove with the reason > > > > > > Thanks, > > > Apache Pinot (incubating) team > > > > > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > >
Re: [VOTE] Apache Pinot (incubating) 0.7.0 RC1
That would be great. We will update the release runbook to make sure this doesn't happen again. Here is my +1 On Thu, Mar 18, 2021 at 11:03 AM Jim Jagielski wrote: > I propose that we run the vote anyway, thus ensuring IPMC oversight and > (post)approval, and then update the release runbook to make sure this > doesn't happen again. Make sense? > > > On Mar 17, 2021, at 11:35 PM, Felix Cheung > wrote: > > > > It is unclear the guidance on this but since it is impossible remove from > > maven > > > > https://repository.apache.org/#nexus-search;classname~Pinot > > > > Once it is published, I’d suggest we update all the links and git hash > and > > still proceed to vote on this. If there is any issue we should vote on > > another release with fix ASAP. Otherwise hopefully IPMC can continue to > > sign off on this release. > > > > > > > > On Wed, Mar 17, 2021 at 3:09 PM kishore g wrote: > > > >> Apologies for the mistake. We have done multiple releases until now and > >> this is the first time we missed the step to get the approval from IPMC > was > >> missed before making the release. > >> > >> What is the right thing to do at this point? Should we cut another > release > >> or can we go ahead with this and ensure that this does not happen again. > >> > >> thanks, > >> Kishore G > >> > >> On Wed, Mar 17, 2021 at 10:59 AM Felix Cheung > >> wrote: > >> > >>> Unfortunately this isn’t the right process for a podling release. > >>> > >>> As the mentor, I am sorry to see the release is not up to the standard > >>> upheld by previous releases. > >>> > >>> > >>> On Wed, Mar 17, 2021 at 7:02 AM kezhenxu94@apache < > kezhenx...@apache.org > >>> > >>> wrote: > >>> > >>>> I think this release violates the Apache release policy because it > >> didn’t > >>>> get the approvals from IPMC but was released actually (in both > dist.a.o > >>> and > >>>> GitHub). > >>>> > >>>> — > >>>> Zhenxu Ke (柯振旭) > >>>> GitHub @kezhenxu94 > >>>> > >>>>> On Mar 17, 2021, at 06:14, Yupeng Fu wrote: > >>>>> > >>>>> Hi all, > >>>>> > >>>>> This is a call for vote to the release Apache Pinot (incubating) > >>> version > >>>>> 0.7.0. > >>>>> > >>>>> Apache Pinot (incubating) is a distributed columnar storage engine > >> that > >>>> can > >>>>> ingest data in realtime and serve analytical queries at low latency. > >>>>> > >>>>> Pinot community has voted and approved this release. > >>>>> > >>>>> Vote thread: > >>>>> > >>>> > >>> > >> > https://lists.apache.org/thread.html/r850cee1e6fc23804d161a31d465e30d5d12b7a4e1cc8035264ea91d6%40%3Cdev.pinot.apache.org%3E > >>>>> > >>>>> > >>>>> Result thread: > >>>>> > >>>> > >>> > >> > https://lists.apache.org/thread.html/r80672ac39a6a6eb7f63c7dbbf595de2f7350cf75d2a7a598601da638%40%3Cdev.pinot.apache.org%3E > >>>>> > >>>>> The release candidate: > >>>>> > >>>> > >>> > >> > https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.7.0-rc1/ > >>>>> > >>>>> > >>>>> Git tag for this release: > >>>>> <https://github.com/apache/incubator-pinot/tree/release-0.7.0-rc0> > >>>>> https://github.com/apache/incubator-pinot/tree/release-0.7.0-rc1 > >>>>> > >>>>> Git hash for this release: > >>>>> 695ca390a8080409b3b76f250f2315b81b86b362 > >>>>> > >>>>> The artifacts have been signed with key: F41AB2B856C6C29D, which can > >> be > >>>>> found in the following KEYS file. > >>>>> https://dist.apache.org/repos/dist/release/incubator/pinot/KEYS > >>>>> > >>>>> Release notes: > >>>>> > >>> > https://github.com/apache/incubator-pinot/releases/tag/release-0.7.0-rc1 > >>>>> > >>>>> Staging repository: > >>>>> < > >>> https://repository.apache.org/content/repositories/orgapachepinot-1023 > > > >>>>> > >> https://repository.apache.org/content/repositories/orgapachepinot-1024 > >>>>> > >>>>> Documentation on verifying a release candidate: > >>>>> > >>>> > >>> > >> > https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate > >>>>> > >>>>> > >>>>> The vote will be open for at least 72 hours or until the necessary > >>>> number of > >>>>> votes are reached. > >>>>> > >>>>> Please vote accordingly, > >>>>> > >>>>> [ ] +1 approve > >>>>> [ ] +0 no opinion > >>>>> [ ] -1 disapprove with the reason > >>>>> > >>>>> Thanks, > >>>>> Apache Pinot (incubating) team > >>>> > >>>> > >>>> > >>>> - > >>>> 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] Apache Pinot (incubating) 0.7.0 RC1
Jim/Felix and others Do we have your +1 to go ahead with the release. Thanks Kishore G On Thu, Mar 18, 2021 at 9:32 PM kishore g wrote: > That would be great. We will update the release runbook to make sure this > doesn't happen again. > > Here is my +1 > > > > On Thu, Mar 18, 2021 at 11:03 AM Jim Jagielski wrote: > >> I propose that we run the vote anyway, thus ensuring IPMC oversight and >> (post)approval, and then update the release runbook to make sure this >> doesn't happen again. Make sense? >> >> > On Mar 17, 2021, at 11:35 PM, Felix Cheung >> wrote: >> > >> > It is unclear the guidance on this but since it is impossible remove >> from >> > maven >> > >> > https://repository.apache.org/#nexus-search;classname~Pinot >> > >> > Once it is published, I’d suggest we update all the links and git hash >> and >> > still proceed to vote on this. If there is any issue we should vote on >> > another release with fix ASAP. Otherwise hopefully IPMC can continue to >> > sign off on this release. >> > >> > >> > >> > On Wed, Mar 17, 2021 at 3:09 PM kishore g wrote: >> > >> >> Apologies for the mistake. We have done multiple releases until now and >> >> this is the first time we missed the step to get the approval from >> IPMC was >> >> missed before making the release. >> >> >> >> What is the right thing to do at this point? Should we cut another >> release >> >> or can we go ahead with this and ensure that this does not happen >> again. >> >> >> >> thanks, >> >> Kishore G >> >> >> >> On Wed, Mar 17, 2021 at 10:59 AM Felix Cheung >> >> wrote: >> >> >> >>> Unfortunately this isn’t the right process for a podling release. >> >>> >> >>> As the mentor, I am sorry to see the release is not up to the standard >> >>> upheld by previous releases. >> >>> >> >>> >> >>> On Wed, Mar 17, 2021 at 7:02 AM kezhenxu94@apache < >> kezhenx...@apache.org >> >>> >> >>> wrote: >> >>> >> >>>> I think this release violates the Apache release policy because it >> >> didn’t >> >>>> get the approvals from IPMC but was released actually (in both >> dist.a.o >> >>> and >> >>>> GitHub). >> >>>> >> >>>> — >> >>>> Zhenxu Ke (柯振旭) >> >>>> GitHub @kezhenxu94 >> >>>> >> >>>>> On Mar 17, 2021, at 06:14, Yupeng Fu wrote: >> >>>>> >> >>>>> Hi all, >> >>>>> >> >>>>> This is a call for vote to the release Apache Pinot (incubating) >> >>> version >> >>>>> 0.7.0. >> >>>>> >> >>>>> Apache Pinot (incubating) is a distributed columnar storage engine >> >> that >> >>>> can >> >>>>> ingest data in realtime and serve analytical queries at low latency. >> >>>>> >> >>>>> Pinot community has voted and approved this release. >> >>>>> >> >>>>> Vote thread: >> >>>>> >> >>>> >> >>> >> >> >> https://lists.apache.org/thread.html/r850cee1e6fc23804d161a31d465e30d5d12b7a4e1cc8035264ea91d6%40%3Cdev.pinot.apache.org%3E >> >>>>> >> >>>>> >> >>>>> Result thread: >> >>>>> >> >>>> >> >>> >> >> >> https://lists.apache.org/thread.html/r80672ac39a6a6eb7f63c7dbbf595de2f7350cf75d2a7a598601da638%40%3Cdev.pinot.apache.org%3E >> >>>>> >> >>>>> The release candidate: >> >>>>> >> >>>> >> >>> >> >> >> https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.7.0-rc1/ >> >>>>> >> >>>>> >> >>>>> Git tag for this release: >> >>>>> <https://github.com/apache/incubator-pinot/tree/release-0.7.0-rc0> >> >>>>> https://github.com/apache/incubator-pinot/tree/release-0.7.0-rc1 >> >>>>> >> >>>>> Git hash for this release: >> >>>>> 695ca390a8080
Re: [VOTE] Release Apache Pinot (incubating) 0.7.1 RC0
+1 (binding) On Tue, Apr 13, 2021 at 6:41 PM Felix Cheung wrote: > Carry over my vote > > +1 binding > > > On Sat, Apr 10, 2021 at 4:04 PM Fu Xiang wrote: > > > Hi all, > > > > This is a call for a vote to release Apache Pinot (incubating) version > > 0.7.1. > > > > Apache Pinot (incubating) is a distributed columnar storage engine that > can > > ingest data in realtime and serve analytical queries at low latency. > > > > Pinot community has voted and approved this release. > > > > Vote threads: > > > > > https://lists.apache.org/thread.html/rf3737f7739a085fd17120807ea41dfe501137ff26ccc6fa40f96ae4a%40%3Cdev.pinot.apache.org%3E > > > > Result thread: > > > > > https://lists.apache.org/thread.html/ra630b726e8a8e2a449555d75cfbe876a7b04a9f10880ea1ea5bb%40%3Cdev.pinot.apache.org%3E > > > > The release candidate: > > https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot- > > incubating-0.7.1-rc0/ > > < > https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.7.1-rc0/ > > > > > > Git tag for this release: > > https://github.com/apache/incubator-pinot/tree/release-0.7.1-rc0 > > > > Git hash for this release: > > *e22be7c3a39e840321d3658e7505f21768b228d6* > > > > The artifacts have been signed with key: *CDEDB21B862F6C66*, which can be > > found in the following KEYS file. > > https://dist.apache.org/repos/dist/release/incubator/pinot/KEYS > > > > Release notes: > > https://github.com/apache/incubator-pinot/releases/tag/release-0.7.1-rc0 > > > > Staging repository: > > https://repository.apache.org/content/repositories/orgapachepinot-1025 > > > > Documentation on verifying a release candidate: > > https://cwiki.apache.org/confluence/display/PINOT > > /Validating+a+release+candidate > > > > The vote will be open for at least 72 hours or until the necessary number > > of votes are reached. > > > > Please vote accordingly, > > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason > > > > Thanks, > > > > Apache Pinot (incubating) team > > >
Re: [VOTE] Graduate Apache Pinot as TLP
+1 On Wed, Jun 23, 2021 at 3:10 PM Xiaotian Jiang wrote: > +1 > > Jackie > > On Tue, Jun 22, 2021 at 12:44 PM Mayank Shrivastava > wrote: > >> Dear Incubator Community, >> >> We have discussed Apache Pinot Podling graduation in the general@incubator >> DISCUSS thread [1], and addressed all the questions and concerns brought >> up >> in the thread. Please refer to [1] for details on the questions and >> concerns brought up, as well as their resolutions. With no objections >> brought up in the discussion, we would like to proceed with the voting >> process. >> >> Here is the official vote for graduating Apache Pinot project as TLP. >> >> Please provide your in the following options: >> >> [ ] +1 - Recommend graduation of Apache Pinot as a TLP >> >> [ ] 0 - I don't feel strongly about it, but don't object >> >> [ ] -1 - Do not recommend the graduation of Apache Pinot because… >> >> The VOTE will remain open for at least 72 hours. >> >> To summarize a few of the community's achievements: >> >> >>- >> >>7800+ contributions from 168 contributors >>- >> >>7 releases by various release managers >>- >> >>6 new committers and 2 new PPMCs invited (all accepted) >>- >> >>Diverse committers and PPMCs (from 7 companies/institutes) >>- >> >>Apache website setup [4] >>- >> >>Dev conversations at d...@pinot.apache.org >>- >> >>Assessed ourselves against the Apache Project maturity matrix [5] >>- > > >> >>We have built a meritocratic and open collaborative process (the Apache >>way) >> >> >> >> = >> >> Establish the Apache Pinot Project >> >> WHEREAS, the Board of Directors deems it to be in the best interests of >> the >> Foundation and consistent with the Foundation's purpose to establish a >> Project Management Committee charged with the creation and maintenance of >> open-source software, for distribution at no charge to the public, related >> to a distributed data integration framework that simplifies common aspects >> of big data integration such as data ingestion, replication, organization >> and lifecycle management for both streaming and batch data ecosystems. >> >> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), >> to be known as the "Apache Pinot Project", be and hereby is established >> pursuant to Bylaws of the Foundation; and be it further >> >> RESOLVED, that the Apache Pinot Project be and hereby is responsible for >> the creation and maintenance of software related to distributed OLAP data >> store to provide Real-time Analytics to power wide variety of analytical >> use case; and be it further >> >> RESOLVED, that the office of "Vice President, Apache Pinot" 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 Pinot Project, and to have >> primary responsibility for management of the projects within the scope of >> responsibility of the Apache Pinot 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 Pinot Project: >> >>- >> >>Felix Cheung >>- >> >>Jackie Jiang >>- >> >>Jim Jagielski >>- >> >>Kishore G >>- >> >>Mayank Shrivastava >>- >> >>Neha Pawar >>- >> >>Olivier Lamy >>- >> >>Seunghyun Lee >>- >> >>Siddharth Teotia >>- >> >>Subbu Subramaniam >>- >> >>Xiang Fu >> >> >> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Kishore Gopalakrishna be >> appointed to the office of Vice President, Apache Pinot, 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 >> of disqualification, or until a successor is appointed; and be it further >> >> RESOLVED, that the Apache Pinot Project be and hereby is tasked with the >> migration and rationalization of the Apache Incubator Pinot podling; and >> be >> it further >> >> RES
Re: [VOTE] Release Apache Pinot (incubating) 0.2.0 RC0
+1 Thanks, KIshore G On Wed, Nov 20, 2019 at 8:48 PM Jean-Baptiste Onofré wrote: > +1 (binding) > > Regards > JB > > On 18/11/2019 20:35, Subbu Subramaniam wrote: > > Hi all, > > > > This is a call for vote to the release Apache Pinot (incubating) version > > 0.2.0. > > > > Apache Pinot (incubating) is a distributed columnar storage engine that > can > > ingest data in realtime and serve analytical queries at low latency. > > > > Pinot community has voted and approved this release. > > > > Vote threads: > > > https://lists.apache.org/thread.html/302ea5dd91e731eaaf9ce3881e027613ebc76a8c01472c0517b56e89@%3Cdev.pinot.apache.org%3E > > > https://lists.apache.org/thread.html/3d785c502905b23f1d4d1da8718501a7cb4ef8245dd665fe99bf6daf@%3Cdev.pinot.apache.org%3E > > > > Result thread: > > > https://lists.apache.org/thread.html/c425825f7d9da198adfbc5c5633dd0300f77f0ce3f9b88dba92dbe60@%3Cdev.pinot.apache.org%3E > > > > The release candidate: > > > https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.2.0-rc0 > > > > Git tag for this release: > > https://github.com/apache/incubator-pinot/tree/release-0.2.0-rc0 > > > > Git hash for this release: > > f8e1980c4160ac7fd2686d9edefab9ac0a825c5b > > > > The artifacts have been signed with key: B530034C, which can be > > found in the following KEYS file. > > https://dist.apache.org/repos/dist/release/incubator/pinot/KEYS > > > > Release notes: > > https://github.com/apache/incubator-pinot/releases/tag/release-0.2.0-rc0 > > > > Staging repository: > > https://repository.apache.org/content/repositories/orgapachepinot-1003 > > > > Documentation on verifying a release candidate: > > > https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate > > > > > > The vote will be open for at least 72 hours or until necessary number of > > votes are reached. > > > > Please vote accordingly, > > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason > > > > Thanks, > > > > -Subbu Subramaniam > > (on behalf of Apache Pinot (incubating) team) > > > > -- > Jean-Baptiste Onofré > jbono...@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Apache Pinot (incubating) 0.3.0 RC2
+1 On Thu, Mar 19, 2020 at 9:53 AM Fu Xiang wrote: > Hi all, > > This is a call for vote to the release Apache Pinot (incubating) version > 0.3.0. > > Apache Pinot (incubating) is a distributed columnar storage engine that can > ingest data in realtime and serve analytical queries at low latency. > > Pinot community has voted and approved this release. > > Vote threads: > > https://lists.apache.org/thread.html/r2b9a26398aa529c13a9f871499a116547819be20129cf91f2be16d07%40%3Cdev.pinot.apache.org%3E > > Result thread: > > https://lists.apache.org/thread.html/r4c3c9e4025e5a69bd19317d1a123c3f8a55039b4712aeb019ad015e0%40%3Cdev.pinot.apache.org%3E > > The release candidate: > > https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.3.0-rc2 > > Git tag for this release: > https://github.com/apache/incubator-pinot/tree/release-0.3.0-rc2 > > Git hash for this release: > 9b2dc20c07dec6cf33df08cd996e8202c3ba > > The artifacts have been signed with key: CDEDB21B862F6C66, which can be > found in the following KEYS file. > https://dist.apache.org/repos/dist/release/incubator/pinot/KEYS > > Release notes: > GitHub: > https://github.com/apache/incubator-pinot/releases/tag/release-0.3.0-rc2 > GitBook: > https://apache-pinot.gitbook.io/apache-pinot-cookbook/releases/0.3.0 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachepinot-1010 > > Documentation on verifying a release candidate: > > https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate > > > The vote will be open for at least 72 hours or until necessary number of > votes are reached. > > Please vote accordingly, > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove with the reason > > Thanks, > > Xiang Fu > (On behalf of Apache Pinot (incubating) team) >
Re: [VOTE] Release Apache Pinot (incubating) 0.3.0 RC2
Thanks Justin, we will take care of it in the next release. On Tue, Mar 24, 2020 at 9:23 PM Justin Mclean wrote: > Hi, > > +1 (binding) but license need a little work. Please fix before the next > release. > > I checked: > - incubating in name > - signatures and hashes are fine > - DISCLAIMER exists > - LICENSE is missing a license > - NOTICE is fine > - No unexpected binary files > - all source files have ASF headers > > LICENSE file is missing license for: > - jquery.requestAnimationFrame Copyright (c) 2012 Corey Frang in [1] This > is also missing in licenses. > - Sizzle.js in [2] This is also missing in licenses. This is one danger > with including minified files. > > Thanks, > Justin > > 1. > ./pinot-controller/src/main/resources/webapp/js/lib/foundation/foundation.js > 2, ./pinot-controller/src/main/resources/webapp/js/lib/jquery-2.1.3.min.js > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Release Apache Pinot (incubating) 0.4.0 RC2
+1 On Tue, Jun 9, 2020 at 7:34 PM Felix Cheung wrote: > +1 > > But a couple of things to follow up: > > mailing list link at the bottom of the web site seems to be broken > > - binary files are in the source package > ./kubernetes/helm/pinot-0.2.0.tgz > ./kubernetes/helm/pinot/charts/zookeeper-2.1.3.tgz > ./kubernetes/helm/presto-0.2.0.tgz > > - ASF license header is not in one java file > /pinot-spi/src/test/resources/TestRecordReader.java > > - build from source > could be helpful to have steps on to getting the right version of and setup > mvn > > Other checks done and are fine: > - incubating in name > - signature and hash fine > - DISCLAIMER is fine > - LICENSE and NOTICE are fine > > > On Mon, Jun 8, 2020 at 9:20 PM H wrote: > > > This is a call for vote to the release Apache Pinot (incubating) version > > 0.4.0 > > > > Apache Pinot (incubating) is a distributed columnar storage engine that > can > > ingest data in realtime and serve analytical queries at low latency. > > > > Pinot community has voted and approved this release. > > > > Vote thread: > > > > > https://lists.apache.org/thread.html/r866256b82048845ed732cb49638294314a0d475c2ea908c2e11bc7a1%40%3Cdev.pinot.apache.org%3E > > > > Result thread: > > > > > https://lists.apache.org/thread.html/rdff8e67f8680fd9d4ed61e0baacad3c7c3ad141567fa7325776c85b1%40%3Cdev.pinot.apache.org%3E > > > > The release candidate: > > > > > https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.4.0-rc2 > > > > Git tag for this release: > > https://github.com/apache/incubator-pinot/tree/release-0.4.0-rc2 > > > > Git hash for this release: > > 8355d2e0e489a8d127f2e32793671fba505628a8 > > > > The artifacts have been signed with key: 6CC169A6FC19C470, which can be > > found in the following KEYS file. > > https://dist.apache.org/repos/dist/release/incubator/pinot/KEYS > > > > Release notes: > > https://github.com/apache/incubator-pinot/releases/tag/release-0.4.0-rc2 > > > > Staging repository: > > https://repository.apache.org/content/repositories/orgapachepinot-1013 > > > > Documentation on verifying a release candidate: > > > > > https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate > > > > > > The vote will be open for at least 72 hours or until necessary number of > > votes are reached. > > > > Please vote accordingly, > > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove with the reason > > > > Thanks, > > Apache Pinot (incubating) team > > >
Re: [VOTE] Release Apache Pinot (incubating) 0.5.0 RC2
+1
On Tue, Sep 8, 2020 at 10:50 AM Jialiang Li wrote:
> +1
>
> On 2020/09/04 19:06:15, Ting Chen wrote:
> > Hi all,
> >
> > This is a call for a vote to release Apache Pinot (incubating) version
> > 0.5.0.
> >
> > Apache Pinot (incubating) is a distributed columnar storage engine that
> can
> > ingest data in realtime and serve analytical queries at low latency.
> >
> > The Pinot community has voted and approved this release.
> >
> > Vote thread:
> >
> https://lists.apache.org/thread.html/rd12f8915647996cc027299181b0665fd422021bb20cd1a308f467045%40%3Cdev.pinot.apache.org%3E
> >
> > Result thread:
> >
> https://lists.apache.org/thread.html/rd12f8915647996cc027299181b0665fd422021bb20cd1a308f467045%40%3Cdev.pinot.apache.org%3E
> >
> > The release candidate:
> >
> https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.5.0-rc2
> >
> > Diff with apache-pinot-incubating-0.5.0-rc1
> > https://github.com/apache/incubator-pinot/commit/d902c1a (Remove the
> > node_modules codes from the src package)
> >
> > Git tag for this release:
> > https://github.com/apache/incubator-pinot/tree/release-0.5.0-rc2
> >
> > Git hash for this release:
> > d87bbc9032c6efe626eb5f9ef1db4de7aa067179
> >
> > The artifacts have been signed with a key: C650A5210408F8F4, which can be
> > found in the following KEYS file.
> > https://dist.apache.org/repos/dist/release/incubator/pinot/KEYS
> >
> > Release notes:
> > https://github.com/apache/incubator-pinot/releases/tag/release-0.5.0-rc2
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachepinot-1016
> >
> > Documentation on verifying a release candidate:
> >
> https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate
> >
> >
> > *Special notes for verification: During this step "diff -r
> > apache-pinot-incubating-${VERSION}-src pinot-git-src", due to Cluster
> > Manager UI & Query Console UI revamp (#5684), you might see the extra
> lines
> > below. It is fine because they are generated code for the revamped
> > controller UI.*
> >
> > *Only in
> > apache-pinot-incubating-0.5.0-src/pinot-controller/src/main/resources:
> dist*
> > *Only in
> > apache-pinot-incubating-0.5.0-src/pinot-controller/src/main/resources:
> > package-lock.json*
> >
> >
> > The vote will be open for at least 72 hours or until a necessary number
> of
> > votes are reached.
> >
> > Please vote accordingly,
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > Thanks,
> > Apache Pinot (incubating) team
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>
Re: [VOTE] Release Apache Pinot (incubating) 0.6.0 RC1
+1 On Wed, Nov 11, 2020 at 6:09 PM Felix Cheung wrote: > It was discussed several times in private@pinot, we can take it from > there. > > It will probably best if one of you simply edit that line right now in the > git repo so we don’t get into this again in 0.7 release. > > > On Wed, Nov 11, 2020 at 10:58 AM Jialiang Li wrote: > > > Hi Felix, > > > > Thanks for the feedback! Sorry I don't have the context on including > > thirdeye into the pinot open source release. Could you share the related > > email thread? If it's not urgent, maybe we can add some notes in pinot > > release page (https://github.com/apache/incubator-pinot/releases), so > > that the next POC will pick it up. > > > > Thanks, > > Jack > > > > On 2020/11/11 04:05:49, Felix Cheung wrote: > > > +1 but > > > > > > it was discussed before, but thirdeye is not included in the source > > release > > > > > > https://github.com/apache/incubator-pinot/blob/master/pinot-distribution/pinot-source-assembly.xml#L39 > > > > > > - incubating in name > > > - signature and hash fine > > > - DISCLAIMER is fine > > > - LICENSE and NOTICE are fine > > > - No unexpected binary files > > > Event for testing, ideally you want to build the test tarball from > > > source paddingPercent.tar.gz, paddingOld.tar.gz, paddingNull.tar.gz, > > > fake_stream_avro_data.tar.gz > > > - All source files have ASF headers > > > > > > On Tue, Nov 10, 2020 at 5:29 PM Jialiang Li wrote: > > > > > > > Hi all, > > > > > > > > This is a call for vote to the release Apache Pinot (incubating) > > version > > > > 0.6.0. > > > > > > > > Apache Pinot (incubating) is a distributed columnar storage engine > > that can > > > > ingest > > > > data in realtime and serve analytical queries at low latency. > > > > > > > > Pinot community has voted and approved this release. > > > > > > > > Vote thread: > > > > > > > > > > > https://lists.apache.org/thread.html/r9c715527f12e425ee15024cdbae7b597c04942a8901711f521f53a34%40%3Cdev.pinot.apache.org%3E > > > > > > > > Result thread: > > > > > > > > > > > https://lists.apache.org/thread.html/r646618892a671155fe810c945c7e16f2ad1de7d7c92bc9e24c0a3290%40%3Cdev.pinot.apache.org%3E > > > > > > > > The release candidate: > > > > > > > > > > > https://dist.apache.org/repos/dist/dev/incubator/pinot/apache-pinot-incubating-0.6.0-rc1 > > > > > > > > Git tag for this release: > > > > https://github.com/apache/incubator-pinot/tree/release-0.6.0-rc1 > > > > > > > > Git hash for this release: > > > > bb646baceafcd9b849a1ecdec7a11203c7027e21 > > > > > > > > The artifacts have been signed with key: FC4005F4DCB8B2F4, which can > be > > > > found in the following KEYS file. > > > > https://dist.apache.org/repos/dist/release/incubator/pinot/KEYS > > > > > > > > Release notes: > > > > > > https://github.com/apache/incubator-pinot/releases/tag/release-0.6.0-rc1 > > > > > > > > Staging repository: > > > > > https://repository.apache.org/content/repositories/orgapachepinot-1022 > > > > > > > > Documentation on verifying a release candidate: > > > > > > > > > > > https://cwiki.apache.org/confluence/display/PINOT/Validating+a+release+candidate > > > > > > > > > > > > The vote will be open for at least 72 hours or until necessary number > > of > > > > votes are reached. > > > > > > > > Please vote accordingly, > > > > > > > > [ ] +1 approve > > > > [ ] +0 no opinion > > > > [ ] -1 disapprove with the reason > > > > > > > > Thanks, > > > > Apache Pinot (incubating) team > > > > > > > > > > > > - > > > > 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 > > > > >
