Re: [VOTE] Accept Polaris into the ASF Incubator
+1 (non-binding) Best, Ashvin On Mon, Aug 5, 2024 at 9:05 AM Tyler Akidau wrote: > +1 (non-binding) > > -Tyler > > On 2024/08/02 17:26:20 Jean-Baptiste Onofré wrote: > > Hi folks, > > > > Following the discussion about Polaris > > (https://lists.apache.org/thread/ymz26dr3bzldbntdgpctbtkb787x311d), > > and after updating the proposal based on comments, I would like to > > start the formal vote to accept Polaris into the ASF Incubator. > > > > As reminder, this is the Polaris Proposal: > > https://cwiki.apache.org/confluence/display/INCUBATOR/PolarisProposal > > > > Please cast your vote: > > [ ] +1, accept Polaris into the ASF Incubator > > [ ] 0, I don't care either way > > [ ] -1, do not accept Polaris into the ASF Incubator, because ... > > > > The vote will run for one week starting from today. > > > > Thanks ! > > Regards > > JB > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [VOTE] Accept Gluten Into the ASF Incubator
+1 (non-binding) Best, Ashvin On Tue, Jan 9, 2024 at 5:43 PM Jesus Camacho Rodriguez wrote: > +1 (binding) > > Thanks, > Jesús > > On Tue, Jan 9, 2024 at 5:23 PM Markus Weimer wrote: > > > +1 (binding) > > > > Happy coding and good luck! > > > > Markus > > > > On Sun, Jan 7, 2024 at 8:55 PM Xiaoqiao He > wrote: > > > > > > +1 (binding) > > > > > > Best Regards, > > > - He Xiaoqiao > > > > > > On Sun, Jan 7, 2024 at 5:39 PM Nicholas Jiang < > nicholasji...@apache.org> > > > wrote: > > > > > > > +1 (non-binding) > > > > > > > > > > > > Regards, > > > > Nicholas Jiang > > > > At 2024-01-04 10:47:41, "ShaoFeng Shi" > wrote: > > > > >Hi Incubator, > > > > > > > > > >Following the discussion [DISCUSS] Gluten proposal[1], > > > > >I am starting this official vote for the Gluten project. > > > > > > > > > >Here is their proposal: > > > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/GlutenProposal > > > > > > > > > >Please cast your vote: > > > > > > > > > >[ ] +1, bring into the Incubator > > > > >[ ] +0, I don't care either way > > > > >[ ] -1, do not bring Gluten into the Incubator, because... > > > > > > > > > >The vote will open for one week from today. > > > > > > > > > >[1] > https://lists.apache.org/thread/xgsm75t721vgnlthgy84909ggqok77j4 > > > > > > > > > >Best regards, > > > > > > > > > >Shaofeng Shi 史少锋 > > > > >Apache Kylin PMC member, > > > > >Apache Incubator PMC member, > > > > >Email: shaofeng...@apache.org > > > > > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > >
Re: [VOTE] Accept XTable into the ASF Incubator
+1 (non-binding) Best, Ashvin On Fri, Dec 15, 2023 at 9:55 PM Jean-Baptiste Onofré wrote: > +1 (binding) > > Regards > JB > > On Sat, Dec 16, 2023 at 5:17 AM Jesus Camacho Rodriguez > wrote: > > > > Hi All, > > > > Following the discussion in the incubator mailing list [1], I am starting > > this official vote for the XTable project. > > > > Here is the proposal - > > https://cwiki.apache.org/confluence/display/INCUBATOR/XTable+Proposal > > > > Please cast your vote: > > > > [ ] +1, bring XTable into the Incubator > > [ ] +0, I don't care either way > > [ ] -1, do not bring XTable into the Incubator, because... > > > > This majority vote is open for at least 96 hours (due to the weekend). > > > > Only votes from Incubator PMC members are binding, but other votes are > > welcome! > > > > Thanks, > > Jesús > > > > [1] https://lists.apache.org/thread/rx9z8ffrf37qjhpkf1vp5rqg5lhht7jm > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [DISCUSS] OneTable proposal
Hi All, +1 to JB's points. Thanks Jesus for steering this discussion. I wholeheartedly support XTable. The potential of this initiative is immense, especially considering feedback from storage formats users and the benchmark we've been developing. I'm eagerly looking forward to collaborating with all who have committed to this project, as well as those in the pipeline and keeping an eye on our progress. I appreciate everyone's support and valuable feedback. Best, Ashvin On Fri, Dec 15, 2023 at 1:24 AM Jean-Baptiste Onofré wrote: > Hi, > > I think that's also the purpose of the incubation to grow the > community, both users community but also dev communities. > So, I don't see a blocker for incubation but more for graduation. > > I would start with the initial committer list with the target to grow > during incubation, including people from other projects (Iceberg, > Hudi, Paimon, ...). > > Regards > JB > > On Thu, Dec 14, 2023 at 5:06 AM Jesus Camacho Rodriguez > wrote: > > > > Carl, thanks for chiming in. > > > > Certainly, let me address that part. > > > > Concerning the initial list of committers: While the project originated > > from Onehouse (a company whose offering is powered by Apache Hudi), it's > > important to highlight that there has been an effort to have an initial > > list of committers that work for a diverse range of companies invested in > > different table formats, including Onehouse (4 committers), Microsoft > (2), > > Google (1), Walmart (1), Adobe (1), Cloudera (1), and Dremio (1). I > believe > > this diversity dispels the notion of a lack of representation or an > > outsized influence from a single group in the community. > > > > Regarding outreach to other communities: As part of the incubation > > proposal, we extended invitations to participate in this discussion and > > contribute to the project to members of the communities of the most > popular > > OSS table formats [1][2][3][4]. Responses generally fell into four > > categories (including some private responses): (1) Positive reception, > > interest in the proposal/vision, and/or thinking about engaging once/if > the > > project is in the ASF. (2) Technical/feasibility questions, which we > > encouraged them to ask on Github since that is our current communication > > platform in the XTable project. (3) No response received. (4) > Disagreement, > > we should all adopt specific format z. It's important to acknowledge the > > diversity in these communities and recognize that interest on XTable / > > opinions on XTable's viability vary. > > > > Some additional thoughts: I believe everyone involved in XTable is > > genuinely working towards making the right decisions for the project and > > they are demonstrating good faith, e.g., hopefully evident in the prompt > > response to the project's name change when concerns were raised. The goal > > is to create a vendor-neutral project with a thriving, inclusive > community. > > In my view, given the current list of initial committers, there is no > lack > > of diversity, and including other committers from table format > communities > > does not address the remaining concern about the project, which stems > from > > the fact that it actually originated in a company backing one of the > table > > format projects, i.e., Apache Hudi. > > Instead, I'd argue it's more important to focus on establishing XTable as > > an independent project governed by ASF's meritocracy principles. That > will > > naturally serve as an invitation for individuals to contribute, become > > committers, PPMC/PMC members, etc. While we are still in the very early > > stages of that journey, I believe that focusing on these principles and > > building the XTable community around them is ultimately the way to > mitigate > > the remaining concern. > > > > Thanks, > > Jesús > > > > > > [1] Apache Paimon (incubating): > > https://lists.apache.org/thread/t29ghx79cp2rlw20s9p0b8o86c5lzgk7 > > [2] Apache Iceberg: > > https://lists.apache.org/thread/lwlrscyklkxqmp28pbxpxko9r1vw4s4z > > [3] Apache Hudi: > > https://lists.apache.org/thread/3415j1lyp8nkgdv8sk378y8hvvmrt248 > > [4] Delta Lake: https://groups.google.com/g/delta-users/c/8btY3qHydwE > > > > > > On Wed, Dec 13, 2023 at 3:04 PM Carl Steinbach > > wrote: > > > > > Hi Jesús, > > > > > > This is a great project, and I am eager to see it added to the > incubator. > > > > > > It's great to see that the naming issue is being addressed, but could > you > > > also respond to the other concern Jacques raised about the need to > broaden > > > the list of initial committers to include members of the Iceberg and > Delta > > > communities? > > > > > > Thanks. > > > > > > - Carl > > > > > > On Mon, Dec 11, 2023 at 5:08 PM Jesus Camacho Rodriguez < > > > jcama...@apache.org> > > > wrote: > > > > > > > Thanks to everyone who expressed support and offered help. It's > great to > > > > see that the project's mission resonates with so many different > people. > > > > > > > > J
Re: [VOTE] Heron to enter Apache Incubator
+1 On Fri, Jun 16, 2017 at 2:00 PM, Karthik Ramasamy wrote: > +1 > > On 2017-06-16 13:50 (-0700), Roy Lenferink wrote: > > +1 > > > > Op vr 16 jun. 2017 om 22:49 schreef Julien Le Dem < > julien.le...@gmail.com> > > > > > +1 > > > > > > On Fri, Jun 16, 2017 at 1:46 PM, William Markito Oliveira < > > > mark...@apache.org> wrote: > > > > > > > +1 > > > > > > > > On Fri, Jun 16, 2017 at 3:45 PM, Debo Dutta (dedutta) < > dedu...@cisco.com > > > > > > > > wrote: > > > > > > > > > +1 > > > > > > > > > > On 6/16/17, 1:41 PM, "Bill Graham" wrote: > > > > > > > > > > Hi, > > > > > > > > > > Based on the discussion on the incubator mailing list[1] I > would > > > like > > > > > to > > > > > call a vote to add Heron to the Apache Incubator. > > > > > > > > > > The full proposal is available below, and is also available on > the > > > > > Apache > > > > > Incubator wiki at: > > > > > https://wiki.apache.org/incubator/HeronProposal > > > > > > > > > > Please vote: > > > > > [ ] +1, bring Heron into Incubator > > > > > [ ] -1, do not bring Heron into Incubator, because... > > > > > > > > > > The vote will open for 7 days until Friday June 23 at 14:00 PT. > > > > > > > > > > Thank you > > > > > > > > > > 1 - > > > > > > > > https://lists.apache.org/thread.html/fb91f527ef479bb5df45bf2c9d93b7 > > > > > 786c3fa6cdbfeba3128599df79@%3Cgeneral.incubator.apache.org%3E > > > > > > > > > > > > > > > > > > > > = Heron Proposal = > > > > > > > > > > = Abstract = > > > > > Heron is a real-time, distributed, fault-tolerant stream > processing > > > > > engine > > > > > initially developed by Twitter. > > > > > > > > > > = Proposal = > > > > > > > > > > Heron is a real-time stream processing engine built for high > > > > > performance, > > > > > ease of manageability, performance predictability and developer > > > > > productivity[1]. We wish to develop a community around Heron to > > > > > increase > > > > > contributions and see Heron thrive in an open forum. > > > > > > > > > > = Background = > > > > > > > > > > Heron provides the ability for developers to compose directed > > > acyclic > > > > > graphs (DAGs) of real-time query execution logic (i.e. a > topology) > > > > and > > > > > submit the topology to execute on a pluggable job scheduling > system > > > > > (e.g., > > > > > Apache Aurora, YARN, Marathon, etc). Users can employ either > the > > > > native > > > > > Heron API or the Apache Storm API to develop the topology. > Heron > > > > > supports > > > > > the Storm API for ease of migration, but beyond that Heron’s > > > > > architecture > > > > > differs considerably from Storm’s. > > > > > > > > > > Users submit a topology to the scheduler using the Heron > client, > > > > which > > > > > uses > > > > > the Heron binary libraries to deploy all daemons required to > run > > > and > > > > > manage > > > > > the topology. The topology therefore has no reliance on > centrally > > > > > managed > > > > > Heron services, only on a generic job scheduling system, which > > > lends > > > > > itself > > > > > well to be run on top of Apache Aurora/Mesos or Apache > Hadoop/YARN > > > > > (among > > > > > others). > > > > > > > > > > The scheduler runs each topology as a job consisting of > multiple > > > > > containers. One of the containers runs the topology master, > > > > > responsible for > > > > > managing the topology. The remaining containers each runs a > stream > > > > > manager > > > > > responsible for data routing, a metrics manager that collects > and > > > > > reports > > > > > various metrics and a number of processes called Heron > instances > > > > which > > > > > run > > > > > the user-defined logic on the stream of tuples. Parallelism is > > > > > achieved via > > > > > process-based isolation of Heron instances, which provides > > > > predictable > > > > > performance while simplifying debugging. The containers are > > > allocated > > > > > and > > > > > managed by the scheduler framework based on resource > availability > > > of > > > > > nodes > > > > > in the cluster. The metadata for the topology, such as the > physical > > > > > plan > > > > > and execution details, are stored in the pluggable Heron State > > > > Manager > > > > > (e.g. Apache ZooKeeper). > > > > > > > > > > = Rationale = > > > > > > > > > > Heron is a general-purpose, modular and extensible platform > that > > > can > > > > be > > > > > leveraged to support common, real-time analytics use cases. > There > > > is > > > > an > > > > > increasing demand for open-source, scalable real-time analytics > > > > > systems. We > > > > > believe that Heron can be leveraged by other organizations to > build > > > > > streaming applications that can benefit from its robustness, > high > > > > > performance, adaptability to clo
Re: [PROPOSAL] Heron
On Thu, Jun 15, 2017 at 1:24 PM, Bill Graham wrote: ... One of our goals during incubation will be to use open forums of > communication, like the Apache mailing lists, and work to foster a truly > collaborative environment for both Apache Storm and Heron community members > to work within together. > > +1 > > On Thu, Jun 15, 2017 at 10:42 AM, Debo Dutta (dedutta) > wrote: > > > Am happy to help too! > > > > Thx > > Debo > > > > Sent from my iPhone > > > > > On Jun 14, 2017, at 8:05 PM, William Markito Oliveira < > > william.mark...@gmail.com> wrote: > > > > > > Howdy! > > > > > > If Heron is looking for some help around incubation process, I'd love > to > > > help while Geode experience is still fresh in my mind and given that > > it's a > > > project/space that I do have interest. Since I'm not an ASF member, I > > don't > > > think I can offer to be a mentor, but can probably still help and > > > participate on the process. > > > > > > Thanks! > > > > > >> On Wed, Jun 14, 2017 at 7:54 PM, P. Taylor Goetz > > wrote: > > >> > > >> Hi Bill/Supun, > > >> > > >> Sorry for not being a little more clear. I was asking more about how > the > > >> Heron community would seek to engage with Storm community at the > > >> *community* level as opposed to the technical level (i.e. “Community > > over > > >> Code”). > > >> > > >> I’ve been asked by many why this has never happened, and have always > > >> struggled to answer. Maybe you could help answer that question as well > > as > > >> if and how that might change if Heron were to incubate. > > >> > > >> Another quick question: The proposal mentions Heron being used in > > >> production at Google, but some Google employees I recently spoke to > > seemed > > >> to contradict that. Could you explain? Note that’s nothing that would > > >> preclude the project from incubating, I’m just curious. > > >> > > >> -Taylor > > >> > > >>> On Jun 14, 2017, at 7:35 AM, Supun Kamburugamuve > > >> wrote: > > >>> > > >>> Hi Taylor, > > >>> > > >>> For me, one of the interesting differences between Heron and Storm is > > the > > >>> execution model. Storm uses a shared memory model while Heron uses a > > >>> process based model. It will be interesting to see how these two > > evolve. > > >>> > > >>> Thanks, > > >>> Supun.. > > >>> > > >>> On Mon, Jun 12, 2017 at 4:15 PM, Bill Graham > > >> wrote: > > >>> > > Hi Taylor, > > > > Thanks for the mentor offer, we'd be glad to have your help. > > > > I think the best place for collaboration would be around the > evolution > > >> of > > the API. In addition we plan to look more into DSL solutions which > we > > >> could > > potentially collaborate on. This could be Trident, or Beam or > > something > > else, but there could be synergies for future development here. > > > > thanks, > > Bill > > > > On Fri, Jun 9, 2017 at 8:53 PM, P. Taylor Goetz > > >> wrote: > > > > > Hi Bill, > > > > > > Could you comment on how/if the Heron community would be willing to > > >> work > > > with the Storm community? I've seen a number of new features in > Storm > > being > > > ported to Heron, but I have yet to see any attempt by the Heron > > >> community > > > to engage with the Apache Storm community. > > > > > > I don't think it would be too far off to say that the relationship > > between > > > Heron and Apache Storm has been somewhat adversarial. The pre- and > > > post-open sourcing marketing around Heron seemed, at least to me, > > somewhat > > > aggressively negative toward Storm. > > > > > > As a peer to Apache Storm, how would the proposed "Apache Heron" > > community > > > work to collaborate with the Storm community? If Heron is adopting > > API > > > changes in Storm, then it seems there is an opportunity for > > collaboration. > > > > > > Don't take any of this as an objection to incubating the project. I > > >> would > > > support it. I would also be willing to be a mentor, if you would > > >> consider > > > taking on another. > > > > > > -Taylor > > > > > >> On Jun 8, 2017, at 1:23 PM, Bill Graham > > wrote: > > >> > > >> Dear Apache Incubator Community, > > >> > > >> We are excited to share our proposal for discussion and feedback > > >> for entering Apache Incubation. Heron is a real-time, distributed, > > >> fault-tolerant stream processing engine. > > >> > > >> Our proposal can be found at https://wiki.apache.org/ > > > incubator/HeronProposal > > >> and is included below. > > >> > > >> > > >> Thank you, > > >> > > >> Bill Graham on behalf of the Heron developers > > >> > > >> > > >> # Heron Proposal > > >> > > >> ## Abstract > > >> Heron is a real-time, distributed, fault-tolerant stream > processing > > > engine > > >> initially developed by Twitter. >
Re: [PROPOSAL] Heron
Thanks William! It will be great to work with you again. On Thu, Jun 15, 2017 at 10:12 AM, Supun Kamburugamuve wrote: > Thank you, William, for offering to help with the incubation process. It > will be really helpful. > > Supun.. > > On Wed, Jun 14, 2017 at 11:04 PM, William Markito Oliveira < > william.mark...@gmail.com> wrote: > > > Howdy! > > > > If Heron is looking for some help around incubation process, I'd love to > > help while Geode experience is still fresh in my mind and given that > it's a > > project/space that I do have interest. Since I'm not an ASF member, I > don't > > think I can offer to be a mentor, but can probably still help and > > participate on the process. > > > > Thanks! > > > > On Wed, Jun 14, 2017 at 7:54 PM, P. Taylor Goetz > > wrote: > > > > > Hi Bill/Supun, > > > > > > Sorry for not being a little more clear. I was asking more about how > the > > > Heron community would seek to engage with Storm community at the > > > *community* level as opposed to the technical level (i.e. “Community > over > > > Code”). > > > > > > I’ve been asked by many why this has never happened, and have always > > > struggled to answer. Maybe you could help answer that question as well > as > > > if and how that might change if Heron were to incubate. > > > > > > Another quick question: The proposal mentions Heron being used in > > > production at Google, but some Google employees I recently spoke to > > seemed > > > to contradict that. Could you explain? Note that’s nothing that would > > > preclude the project from incubating, I’m just curious. > > > > > > -Taylor > > > > > > > On Jun 14, 2017, at 7:35 AM, Supun Kamburugamuve > > > wrote: > > > > > > > > Hi Taylor, > > > > > > > > For me, one of the interesting differences between Heron and Storm is > > the > > > > execution model. Storm uses a shared memory model while Heron uses a > > > > process based model. It will be interesting to see how these two > > evolve. > > > > > > > > Thanks, > > > > Supun.. > > > > > > > > On Mon, Jun 12, 2017 at 4:15 PM, Bill Graham > > > wrote: > > > > > > > >> Hi Taylor, > > > >> > > > >> Thanks for the mentor offer, we'd be glad to have your help. > > > >> > > > >> I think the best place for collaboration would be around the > evolution > > > of > > > >> the API. In addition we plan to look more into DSL solutions which > we > > > could > > > >> potentially collaborate on. This could be Trident, or Beam or > > something > > > >> else, but there could be synergies for future development here. > > > >> > > > >> thanks, > > > >> Bill > > > >> > > > >> On Fri, Jun 9, 2017 at 8:53 PM, P. Taylor Goetz > > > wrote: > > > >> > > > >>> Hi Bill, > > > >>> > > > >>> Could you comment on how/if the Heron community would be willing to > > > work > > > >>> with the Storm community? I've seen a number of new features in > Storm > > > >> being > > > >>> ported to Heron, but I have yet to see any attempt by the Heron > > > community > > > >>> to engage with the Apache Storm community. > > > >>> > > > >>> I don't think it would be too far off to say that the relationship > > > >> between > > > >>> Heron and Apache Storm has been somewhat adversarial. The pre- and > > > >>> post-open sourcing marketing around Heron seemed, at least to me, > > > >> somewhat > > > >>> aggressively negative toward Storm. > > > >>> > > > >>> As a peer to Apache Storm, how would the proposed "Apache Heron" > > > >> community > > > >>> work to collaborate with the Storm community? If Heron is adopting > > API > > > >>> changes in Storm, then it seems there is an opportunity for > > > >> collaboration. > > > >>> > > > >>> Don't take any of this as an objection to incubating the project. I > > > would > > > >>> support it. I would also be willing to be a mentor, if you would > > > consider > > > >>> taking on another. > > > >>> > > > >>> -Taylor > > > >>> > > > On Jun 8, 2017, at 1:23 PM, Bill Graham > > wrote: > > > > > > Dear Apache Incubator Community, > > > > > > We are excited to share our proposal for discussion and feedback > > > for entering Apache Incubation. Heron is a real-time, distributed, > > > fault-tolerant stream processing engine. > > > > > > Our proposal can be found at https://wiki.apache.org/ > > > >>> incubator/HeronProposal > > > and is included below. > > > > > > > > > Thank you, > > > > > > Bill Graham on behalf of the Heron developers > > > > > > > > > # Heron Proposal > > > > > > ## Abstract > > > Heron is a real-time, distributed, fault-tolerant stream > processing > > > >>> engine > > > initially developed by Twitter. > > > > > > ## Proposal > > > > > > Heron is a real-time stream processing engine built for high > > > >> performance, > > > ease of manageability, performance predictability and developer > > > productivity[1]. We wish to develop a community around Heron to > > > >>
