Hey y'all, I'm happy to announce that I've created a PR for MM2:
https://github.com/apache/kafka/pull/6295
Please take a look!
Ryanne
On Tue, Jan 22, 2019 at 11:43 AM Ryanne Dolan wrote:
> Thanks all, this is a large KIP and has sparked a lot of great
> discussion, both on and off the dev
Thanks all, this is a large KIP and has sparked a lot of great
discussion, both on and off the dev list. I'm closing the vote with
the following results:
+12 non-binding
+3 binding
The KIP is accepted!
Thanks,
Ryanne
On Fri, Jan 11, 2019 at 9:48 PM Becket Qin wrote:
>
> Hi Ryanne,
>
> Thanks
Hi Ryanne,
Thanks for the KIP and patient discussion. +1 from me as well.
Jiangjie (Becket) Qin
On Fri, Jan 11, 2019 at 1:11 AM Jun Rao wrote:
> Hi, Ryanne,
>
> Thanks for the explanation. All make sense to me now. +1 on the KIP from
> me.
>
> Jun
>
> On Wed, Jan 9, 2019 at 7:16 PM Ryanne
Hi, Ryanne,
Thanks for the explanation. All make sense to me now. +1 on the KIP from me.
Jun
On Wed, Jan 9, 2019 at 7:16 PM Ryanne Dolan wrote:
> Thanks Jun.
>
> > 103. My point was that the MirrorMakerConnector can die while the
> Heartbeat connector is still alive. So, one can't solely rely
Thanks Jun.
> 103. My point was that the MirrorMakerConnector can die while the
Heartbeat connector is still alive. So, one can't solely rely on Heartbeat
for monitoring?
Each cluster will have a heartbeat topic produced by
MirrorHeartbeatConnector, which doesn't have an associated "source"
Hi, Ryanne,
103. My point was that the MirrorMakerConnector can die while the Heartbeat
connector is still alive. So, one can't solely rely on Heartbeat for
monitoring?
105. Hmm, maybe I don't understand how this is done. Let's say we replica
topic1 from cluster A to cluster B. My understanding
Thanks Jun, I've updated the KIP as requested. Brief notes below:
100. added "...out-of-the-box (without custom handlers)..."
101. done. Good idea to include a MessageFormatter.
102. done.
> 103. [...] why is Heartbeat a separate connector?
Heartbeats themselves are replicated via
Hi, Ryanne,
Thanks for KIP. Still have a few more comments below.
100. "This is not possible with MirrorMaker today -- records would be
replicated back and forth indefinitely, and the topics in either cluster
would be merged inconsistently between clusters. " This is not 100% true
since MM can
02 January 2019 11:10
> To: dev
> Subject: Re: [EXTERNAL] [VOTE] KIP-382 MirrorMaker 2.0
>
> +1 (non-binding)
> Thanks Ryanne
>
> On Wed, Jan 2, 2019 at 4:47 AM McCaig, Rhys
> wrote:
> >
> > +1 (non-binding). Fantastic work on the KIP Ryanne.
> >
> > > On
+1 (non-binding)
Jonathan Skrzypek
-Original Message-
From: Mickael Maison
Sent: 02 January 2019 11:10
To: dev
Subject: Re: [EXTERNAL] [VOTE] KIP-382 MirrorMaker 2.0
+1 (non-binding)
Thanks Ryanne
On Wed, Jan 2, 2019 at 4:47 AM McCaig, Rhys wrote:
>
> +1 (non-binding). Fan
>>
> >>
> >> Harsha wrote on 21/12/2018 20:17:03:
> >>
> >>> From: Harsha
> >>> To: dev@kafka.apache.org
> >>> Date: 21/12/2018 20:17
> >>> Subject: Re: [VOTE] KIP-382 MirrorMaker 2.0
> >>>
> &g
ding
>>
>> thanks for the KIP
>> --
>>
>> Edoardo Comar
>>
>> IBM Event Streams
>>
>>
>> Harsha wrote on 21/12/2018 20:17:03:
>>
>>> From: Harsha
>>> To: dev@kafka.apache.org
>>> Date: 21/12/2018 20:17
m: Harsha
> > To: dev@kafka.apache.org
> > Date: 21/12/2018 20:17
> > Subject: Re: [VOTE] KIP-382 MirrorMaker 2.0
> >
> > +1 (binding). Nice work Ryan.
> > -Harsha
> >
> > On Fri, Dec 21, 2018, at 8:14 AM, Andrew Schofield wrote:
> > > +1
+1 non-binding
thanks for the KIP
--
Edoardo Comar
IBM Event Streams
Harsha wrote on 21/12/2018 20:17:03:
> From: Harsha
> To: dev@kafka.apache.org
> Date: 21/12/2018 20:17
> Subject: Re: [VOTE] KIP-382 MirrorMaker 2.0
>
+1 (binding). Nice work Ryan.
-Harsha
On Fri, Dec 21, 2018, at 8:14 AM, Andrew Schofield wrote:
> +1 (non-binding)
>
> Andrew Schofield
> IBM Event Streams
>
> On 21/12/2018, 01:23, "Srinivas Reddy" wrote:
>
> +1 (non binding)
>
> Thank you Ryan for the KIP, let me know if you
+1 (non-binding)
Andrew Schofield
IBM Event Streams
On 21/12/2018, 01:23, "Srinivas Reddy" wrote:
+1 (non binding)
Thank you Ryan for the KIP, let me know if you need support in implementing
it.
-
Srinivas
- Typed on tiny keys. pls ignore typos.{mobile
+1 (non-binding)
Great stuff!
Eno
On Fri, Dec 21, 2018 at 10:04 AM Sönke Liebau
wrote:
> +1 (non-binding)
>
> Thanks for your effort Ryanne!
>
> On Fri, Dec 21, 2018 at 2:23 AM Srinivas Reddy
> wrote:
> >
> > +1 (non binding)
> >
> > Thank you Ryan for the KIP, let me know if you need support
+1 (non-binding)
Thanks for your effort Ryanne!
On Fri, Dec 21, 2018 at 2:23 AM Srinivas Reddy
wrote:
>
> +1 (non binding)
>
> Thank you Ryan for the KIP, let me know if you need support in implementing
> it.
>
> -
> Srinivas
>
> - Typed on tiny keys. pls ignore typos.{mobile app}
>
>
> On Fri,
+1 (non binding)
Thank you Ryan for the KIP, let me know if you need support in implementing
it.
-
Srinivas
- Typed on tiny keys. pls ignore typos.{mobile app}
On Fri, 21 Dec, 2018, 08:26 Ryanne Dolan Thanks for the votes so far!
>
> Due to recent discussions, I've removed the high-level
Thanks for the votes so far!
Due to recent discussions, I've removed the high-level REST API from the
KIP.
On Thu, Dec 20, 2018 at 12:42 PM Paul Davidson
wrote:
> +1
>
> Would be great to see the community build on the basic approach we took
> with Mirus. Thanks Ryanne.
>
> On Thu, Dec 20,
+1
Would be great to see the community build on the basic approach we took
with Mirus. Thanks Ryanne.
On Thu, Dec 20, 2018 at 9:01 AM Andrew Psaltis
wrote:
> +1
>
> Really looking forward to this and to helping in any way I can. Thanks for
> kicking this off Ryanne.
>
> On Thu, Dec 20, 2018 at
+1
Really looking forward to this and to helping in any way I can. Thanks for
kicking this off Ryanne.
On Thu, Dec 20, 2018 at 10:18 PM Andrew Otto wrote:
> +1
>
> This looks like a huge project! Wikimedia would be very excited to have
> this. Thanks!
>
> On Thu, Dec 20, 2018 at 9:52 AM Ryanne
+1
This looks like a huge project! Wikimedia would be very excited to have
this. Thanks!
On Thu, Dec 20, 2018 at 9:52 AM Ryanne Dolan wrote:
> Hey y'all, please vote to adopt KIP-382 by replying +1 to this thread.
>
> For your reference, here are the highlights of the proposal:
>
> - Leverages
Hey y'all, please vote to adopt KIP-382 by replying +1 to this thread.
For your reference, here are the highlights of the proposal:
- Leverages the Kafka Connect framework and ecosystem.
- Includes both source and sink connectors.
- Includes a high-level driver that manages connectors in a
24 matches
Mail list logo
