Edoardo Comar created KAFKA-19443:
-
Summary: test-common ClusterInstance should make it easy to have
more listeners
Key: KAFKA-19443
URL: https://issues.apache.org/jira/browse/KAFKA-19443
Project
FYI while trying with an AlterConfigPolicy to stop the cleanup.policy
being emptied through a AlterConfigOp.OpType.SUBTRACT,
I stumbled in this behavior
that doesn't allow to block an empty policy in Zookeeper versions of Kafka
https://issues.apache.org/jira/browse/KAFKA-19026
On Tue, 13 May 2025
Luke, TengYao
https://github.com/apache/kafka/pull/19563
On Fri, 25 Apr 2025 at 12:18, Edoardo Comar wrote:
>
> Hi Luke, as discussed in the issue
> https://github.com/apache/kafka-site/pull/685
>
> On Thu, 24 Apr 2025 at 12:04, 黃竣陽 wrote:
> >
> > Hello TengYao,
Hi Luke, as discussed in the issue
https://github.com/apache/kafka-site/pull/685
On Thu, 24 Apr 2025 at 12:04, 黃竣陽 wrote:
>
> Hello TengYao,
>
> I've completed the following tests on my local machine:
>
> - Built from source using JDK 21 & JDK 17 (Zulu)
> - Executed all unit and integration tests
Hi I'd like this fix to make it in 3.9.1
https://github.com/apache/kafka/pull/19263
any review to push it through would be welcome - thanks
On Fri, 28 Mar 2025 at 02:45, Luke Chen wrote:
>
> Hi Stig,
>
> Let's make sure we have consensus from the community for this backporting
> first.
> I've j
Edoardo Comar created KAFKA-19028:
-
Summary: AlterConfigPolicy with OpType.DELETE : inconsistent
behavior between TOPIC and BROKER resource
Key: KAFKA-19028
URL: https://issues.apache.org/jira/browse/KAFKA-19028
Edoardo Comar created KAFKA-19026:
-
Summary: AlterConfigPolicy incompatibility between ZK mode and
KRaft mode when using AlterConfigOp.OpType.SUBTRACT
Key: KAFKA-19026
URL: https://issues.apache.org/jira/browse
Hi Priyanka,
I see I am fashionably late for this party, but, still ...
Thank you for the KIP.
+1 (binding)
Edo
On Wed, 23 Oct 2024 at 18:00, Greg Harris wrote:
>
> Hi Priyanka,
>
> This is definitely an improvement for single-schema Connectors, and simple
> to configure.
> I think mutable or
Edoardo Comar created KAFKA-18982:
-
Summary: Allow ClusterTests to ignore specific thread leaks
Key: KAFKA-18982
URL: https://issues.apache.org/jira/browse/KAFKA-18982
Project: Kafka
Issue
Hi
is it too late to cherry pick
https://github.com/apache/kafka/pull/18833 on 4.0.0 ?
(KAFKA-18758: NullPointerException in shutdown following
InvalidConfigurationException)
it's a clean merges and build - but should I wait for a 4.0.1 ?
thanks, Edo
On Wed, 5 Feb 2025 at 18:45, Chia-Ping Tsai w
Edoardo Comar created KAFKA-18758:
-
Summary: NullPointerException in shutdown following
InvalidConfigurationException
Key: KAFKA-18758
URL: https://issues.apache.org/jira/browse/KAFKA-18758
Project
Congratulations Andrew !
Edoardo
On Mon, 2 Dec 2024 at 15:56, Bruno Cadonna wrote:
>
> Hi,
>
> Congrats!
> Well deserved!
>
> Best,
> Bruno
>
> On 02.12.24 16:21, Lucas Brutschy wrote:
> > Congrats! Well deserved.
> >
> > Cheers,
> > Lucas
> >
> > On Mon, Dec 2, 2024 at 4:20 PM Bill Bejeck wrote
+1 (binding), thanks for this KIP Tina
Edo
On Mon, 18 Nov 2024 at 12:31, Mickael Maison wrote:
>
> Hi,
>
> +1 (binding), thanks for the KIP
>
> Mickael
>
> On Wed, Nov 6, 2024 at 9:05 AM Gantigmaa Selenge wrote:
> >
> > Hi everyone,
> >
> > A quick reminder that this KIP is still awaiting more
[
https://issues.apache.org/jira/browse/KAFKA-7720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edoardo Comar resolved KAFKA-7720.
--
Resolution: Implemented
> kafka-configs script should also describe default broker entr
Edoardo Comar created KAFKA-18020:
-
Summary: Encountered quorum controller fault:
incrementalAlterConfigs .. RuntimeException: 'value' field is too long to be
serialized
Key: KAFKA-18020
Edoardo Comar created KAFKA-17993:
-
Summary: reassign partition tool stuck with uncaught exception:
'value' field is too long to be serialized
Key: KAFKA-17993
URL: https://issues.apache.org/jira/br
Thanks for this KIP, Chris,
+1 (binding)
Edo
On Fri, 14 Jun 2024 at 20:20, Greg Harris wrote:
>
> Hey Chris,
>
> Thanks for the KIP.
>
> I think demonstrating the health of the tick thread through a longer
> request is going to be more reliable than caching the health and status in
> order to r
Chris, I was about to vote too but have one trivial question.
You designed this health check for a completely generic connect runtime,
regardless of which connectors it's running, right?
Because if I run a well-known to me set of connectors, i.e. mm2 :-) ,
then checking the connectors and tasks s
rest of the versions: KAFKA-16960
> > >> <https://issues.apache.org/jira/browse/KAFKA-16960>
> > >> 3. TestKRaftUpgrade failed at "fromVersion"=3.3 ~ 3.5 under combined
> > >> KRaft:
> > >> KAFKA-16961 <https://issues.apache.org/jira/brow
morrow morning (CEST) asking maintainers to stop
> cherry picking commits unless we discuss it beforehand.
>
> Best,
>
> On Wed, Jun 12, 2024 at 6:09 PM Edoardo Comar wrote:
>
> > Hi Josep, I understand I am still in time to cherry-pick on 3.8.0
> > https://github.com/apache
well if you still need to build RC2, I'd cherry pick this that I
missed from the other PR
https://github.com/apache/kafka/pull/16326
On Thu, 13 Jun 2024 at 13:20, Igor Soarez wrote:
>
> Hi Edoardo,
>
> It is late, but not too late. I have cherry-picked your change
> to the 3.7 branch and I'll bui
Thanks !
On Thu, 13 Jun 2024 at 13:20, Igor Soarez wrote:
>
> Hi Edoardo,
>
> It is late, but not too late. I have cherry-picked your change
> to the 3.7 branch and I'll build a second release candidate.
>
> If you could have a look at the first RC, please let me know if
> you spot any issues wit
Hi Igor, is it too late to cherry-pick
https://github.com/apache/kafka/pull/16229 to 3.7.1 ?
Thanks, Edo
On Tue, 11 Jun 2024 at 08:29, Igor Soarez wrote:
>
> Now attaching the container build reports, which I seem to have forgotten to
> include before.
>
> --
> Igor
Hi Josep, I understand I am still in time to cherry-pick on 3.8.0
https://github.com/apache/kafka/pull/16229
right?
thanks
On Wed, 12 Jun 2024 at 11:34, Ivan Yurchenko wrote:
>
> Hi,
>
> I'll try to do all the fixes and changes for KIP-899 [1] sooner today, but
> please proceed with the release
Edoardo Comar created KAFKA-16931:
-
Summary: A transient REST failure to forward fenceZombie request
leaves Connect Task in FAILED state
Key: KAFKA-16931
URL: https://issues.apache.org/jira/browse/KAFKA-16931
[
https://issues.apache.org/jira/browse/KAFKA-14657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edoardo Comar resolved KAFKA-14657.
---
Resolution: Duplicate
duplicate of https://issues.apache.org/jira/browse/KAFKA-16570
[
https://issues.apache.org/jira/browse/KAFKA-16488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edoardo Comar resolved KAFKA-16488.
---
Resolution: Fixed
> fix flaky MirrorConnectorsIntegrationExactlyOnceTest#testReplicat
[
https://issues.apache.org/jira/browse/KAFKA-15905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edoardo Comar reopened KAFKA-15905:
---
reopening for backporting to 3.7.1 to be confermed
> Restarts of MirrorCheckpointTask sho
Edoardo Comar created KAFKA-16622:
-
Summary: Mirromaker2 first Checkpoint not emitted until consumer
group fully catches up once
Key: KAFKA-16622
URL: https://issues.apache.org/jira/browse/KAFKA-16622
Thanks Andrew,
+1 (binding)
Edo
On Mon, 18 Mar 2024 at 16:32, Kenneth Eversole
wrote:
>
> Hi Andrew
>
> + 1 (Non-Binding)
>
> This will be great addition to Kafka
>
> On Mon, Mar 18, 2024 at 8:27 AM Apoorv Mittal
> wrote:
>
> > Hi Andrew,
> > Thanks for writing the KIP. This is indeed going to
Thanks Manikumar, done and marked the issue as resolved
On Mon, 18 Mar 2024 at 16:30, Manikumar wrote:
>
> Hi Edoardo,
>
> sure, pls go ahead and cherry-pick the changes to 3.7 and 3.6 branches.
>
> Thanks,
>
> On Mon, Mar 18, 2024 at 3:53 PM Edoardo Comar wrote:
>
Hi Manikumar,
https://issues.apache.org/jira/browse/KAFKA-16369
is merged in trunk now.
can you please cherry-pick it to 3.6.2 ?
I didn't see it included in the plan, would you like me to add it ?
I'd consider it a blocker since Kafka may stay up and running but useless ...
On Mon, 18 Mar 2024 at
Hi Manikumar,
can we please include
https://issues.apache.org/jira/browse/KAFKA-16369
in 3.6.2 ?
While it's an issue still in trunk we actually discovered it our 3.6.1 systems
thanks,
Edo
On Thu, 14 Mar 2024 at 08:39, Divij Vaidya wrote:
>
> Hi Manikumar,
>
> 1. Can you please take a look at htt
Edoardo Comar created KAFKA-16369:
-
Summary: Broker may not shut down when SocketServer fails to bind
as Address already in use
Key: KAFKA-16369
URL: https://issues.apache.org/jira/browse/KAFKA-16369
Hi Elxan,
+1 (binding).
Thanks,
Edo
On Wed, 10 Jan 2024 at 14:01, Viktor Somogyi-Vass
wrote:
>
> Hi Elxan,
>
> +1 (binding).
>
> Thanks,
> Viktor
>
> On Mon, Jan 8, 2024 at 5:57 PM Dániel Urbán wrote:
>
> > Hi Elxan,
> > +1 (non-binding)
> > Thanks for the KIP, this will be a very useful metri
+1 (binding)
Thanks for the KIP Tina!
Edo
On Tue, 19 Dec 2023 at 10:01, Gantigmaa Selenge wrote:
>
> Thank you Chris and Mickael for the vote!
>
> KIP is missing just one more +1 (binding).
>
> Regards,
> Tina
>
> On Thu, Dec 14, 2023 at 1:48 PM Mickael Maison
> wrote:
>
> > +1 (binding)
> > Th
onsoleConsumer.scala:77)
> at kafka.tools.ConsoleConsumer$.main(ConsoleConsumer.scala:54)
> at kafka.tools.ConsoleConsumer.main(ConsoleConsumer.scala)
>
> If I change the test in SslConfigs.java to test for presence of the TPSv1.3
> protocol rather than testing for Java
Andreas,
do you mean that even if you configure your Java client running on Java8 with
ssl.enabled.protocols=TLSv1.3
you can't connect to a Kafka broker using TLS1.3 ?
On Sat, 28 Oct 2023 at 01:03, Ismael Juma wrote:
>
> Hi Andreas,
>
> The TLS code has run into changes in behavior across differ
Congratulations Yash
On Thu, 21 Sept 2023 at 16:28, Bruno Cadonna wrote:
>
> Hi all,
>
> The PMC of Apache Kafka is pleased to announce a new Kafka committer
> Yash Mayya.
>
> Yash's major contributions are around Connect.
>
> Yash authored the following KIPs:
>
> KIP-793: Allow sink connectors t
On Wed, 5 Jul 2023 at 16:55, Edoardo Comar wrote:
>
> Hi Jorge!
>
> On Fri, 30 Jun 2023 at 15:47, Jorge Esteban Quilcate Otoya
> wrote:
> >
> > Thank you both for the replies! A couple more comments:
> >
> > The current proposal is to have ‘record.validation.po
Hi Jorge!
On Fri, 30 Jun 2023 at 15:47, Jorge Esteban Quilcate Otoya
wrote:
>
> Thank you both for the replies! A couple more comments:
>
> The current proposal is to have ‘record.validation.policy’ per topic
> (default null). A flag would be something like
> ‘record.validation.policy.enable’ (de
[
https://issues.apache.org/jira/browse/KAFKA-15144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edoardo Comar resolved KAFKA-15144.
---
Resolution: Not A Bug
Closing as not a bug.
The "problem" arose as without conf
Edoardo Comar created KAFKA-15144:
-
Summary: Checkpoint downstreamOffset stuck to 1
Key: KAFKA-15144
URL: https://issues.apache.org/jira/browse/KAFKA-15144
Project: Kafka
Issue Type: Bug
Edoardo Comar created KAFKA-15133:
-
Summary: RequestMetrics MessageConversionsTimeMs count is ticked
even when no conversion occurs
Key: KAFKA-15133
URL: https://issues.apache.org/jira/browse/KAFKA-15133
Hi Andrew,
thanks for your comments ! Please see replies inline below.
On Mon, 26 Jun 2023 at 16:51, Andrew Schofield
wrote:
> 4) For a new interface, I wonder whether it would be better to use
> TopicIdPartition rather
> than TopicPartition. Topic IDs are gradually spreading across the public
Hi Tom,
thanks for tour comments, replies inline below.
On Thu, 22 Jun 2023 at 10:58, Tom Bentley wrote:
>
> Hi Edorado and Adrian,
>
> Thanks for the KIP.
>
> I think it would be good to elaborate on exactly how validate() gets
> called, because I think there are a number of potential problems,
Hi Jorge
thanks for the feedback. Comments inline below
> 1. Similar to Kirk's first point, I'm also concerned on how would the
> plugin developers / operators be able to apply multiple policies and how
> configurations would be passed to each policy.
We’ve only attempted to tackle the “one plugi
and/or
> outside the scope of this KIP?
>
> 3. What is the benefit to introducing the inner TopicMetadata and RecordProxy
> interfaces vs. passing the TopicPartition, String (validation policy), and
> Record into the validate() method directly?
>
> Thanks,
> Kirk
>
>
Thanks Николай,
We’d like to open a vote next week.
Hopefully getting some more feedback before then.
Edo
On Wed, 7 Jun 2023 at 19:15, Николай Ижиков wrote:
> Hello.
>
> As author of one of related KIPs I’m +1 for this change.
> Long waited feature.
>
> > 7 июня 2023
Congratulations Divij !
On Wed, 14 Jun 2023 at 10:51, Josep Prat
wrote:
> Congrats Divij!
>
> On Wed, Jun 14, 2023 at 11:45 AM Lucas Brutschy
> wrote:
>
> > Congrats!!
> >
> > On Wed, Jun 14, 2023 at 11:02 AM Federico Valeri
> > wrote:
> > >
> > > Congrats Divij!
> > >
> > > On Wed, Jun 14, 2
Dear all,
Adrian and I would like to start a discussion thread on
KIP-940: Broker extension point for validating record contents at produce time
https://cwiki.apache.org/confluence/display/KAFKA/KIP-940%3A+Broker+extension+point+for+validating+record+contents+at+produce+time
This KIP proposes a
Edoardo Comar created KAFKA-14996:
-
Summary: CreateTopic falis with UnknownServerException if num
partitions >= QuorumController.MAX_RECORDS_PER_BATCH
Key: KAFKA-14996
URL: https://issues.apache.org/jira/bro
Congratulations Mickael !!
On Mon, 24 Apr 2023 at 20:18, Randall Hauch wrote:
> Thank you, Jun, for all your contributions as PMC chair.
>
> And congratulations and thanks, Mickael, for volunteering to take over this
> important role.
>
> Best regards,
> Randall
>
> On Mon, Apr 24, 2023 at 1:39
Hi hudeqi,
thanks for the KIP.
For the purpose of monitoring if partitions of a topic are used "fairly",
the log end offset metric offers a good hint.
Of course, it only expresses a message count, not bytes, but I find it
sufficient and do not need the actual throughput per partition.
Perhaps the
oting this.
This is a significant difference from one of the other KIPs mentioned,
where the intention was for a producer to receive PolicyFailed exceptions.
This should be part of the KIP, IMHO
On Tue, 21 Feb 2023 at 13:53, Edoardo Comar wrote:
> Hi David
> thanks for the KIP.
>
Hi David
thanks for the KIP.
Two initial observations from me.
I think the Rejected Alternatives section could compare your proposal to
the prior art that you rightly mention initially.
Also, the Java interface could extend Kafka's own Configurable.
This allows an implementation to get hold of t
Edoardo Comar created KAFKA-14657:
-
Summary: Admin.fenceProducers fails when Producer has ongoing
transaction - but Producer gets fenced
Key: KAFKA-14657
URL: https://issues.apache.org/jira/browse/KAFKA-14657
[
https://issues.apache.org/jira/browse/KAFKA-7666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edoardo Comar resolved KAFKA-7666.
--
Resolution: Won't Fix
KIP has been retired
> KIP-391: Allow Producing with Off
On 1/6/23 5:15 PM, Luke Chen wrote:
> > > > > > >> Congratulations, Edoardo!
> > > > > > >>
> > > > > > >> Luke
> > > > > > >>
> > > > > > >> On Sat, Jan 7, 2023 at 7:58 AM Mick
Edoardo Comar created KAFKA-14571:
-
Summary: ZkMetadataCache.getClusterMetadata is missing rack
information for aliveNodes
Key: KAFKA-14571
URL: https://issues.apache.org/jira/browse/KAFKA-14571
Mickael,
+1 from me - even if you didn't ask for a vote :-)
Edo
--
Edoardo Comar
Event Streams for IBM Cloud
From: Mickael Maison
Sent: 23 March 2022 11:43
To: dev
Subject: [EXTERNAL] Re: [VOTE] KI
ompatibility section.
HTH
Edo
------
Edoardo Comar
Event Streams for IBM Cloud
From: Luke Chen
Sent: 18 March 2022 07:57
To: dev
Subject: [EXTERNAL] Re: [VOTE] KIP-653: Upgrade log4j to log4j2
Hi Dongjin,
I know there
Hi Dongjin,
+1 (non-binding)
many thanks
Edoardo
On Wed, 19 Jan 2022 at 14:07, Viktor Somogyi-Vass
wrote:
> Hi Dongjin,
>
> +1 (non-binding) from me as well. Thanks for picking this up!
>
> Viktor
>
> On Mon, Jan 17, 2022 at 1:07 PM Mickael Maison
> wrote:
>
> > Hi Dongjin,
> >
> > +1 (binding
Hi Colin
thanks for your comments.
I think your objections to creating an interface for replica placement
could be used against similar server-side plug-ins (Authorizer,
QuotaCallback).
They too are on sensitive code paths, can cause problems if badly
written/poorly tested and may cause a pain on t
Edoardo Comar created KAFKA-10220:
-
Summary: NPE when describing resources
Key: KAFKA-10220
URL: https://issues.apache.org/jira/browse/KAFKA-10220
Project: Kafka
Issue Type: Bug
+1 (non-binding)
Thanks Tom
--
Edoardo Comar
Event Streams for IBM Cloud
IBM UK Ltd, Hursley Park, SO21 2JN
From: Gunnar Morling
To: dev@kafka.apache.org
Date: 19/05/2020 10:35
Subject:[EXTERNAL] Re: [VOTE] KIP 585: Filter and
Ryanne Dolan wrote on 05/05/2020 20:36:49:
> Exactly. Why would 3.1 be the breaking release? No one would expect
> everything to break going from 3.0 to 3.1
Agree completely
>
> Ryanne
>
> On Tue, May 5, 2020 at 2:34 PM Gwen Shapira wrote:
>
> > It sounds like the decision to make the next
+1 (non-binding)
Thanks Mickael
--
Edoardo Comar
Event Streams for IBM Cloud
IBM UK Ltd, Hursley Park, SO21 2JN
From: Mickael Maison
To: dev
Date: 04/05/2020 11:45
Subject:[EXTERNAL] [VOTE] KIP-597: MirrorMaker2 internal
+1 (non-binding)
thanks for the KIP !
On Tue, 14 Jan 2020 at 13:57, Navinder Brar
wrote:
> +1 (non-binding)
> Navinder
> On Tuesday, 14 January, 2020, 07:24:02 pm IST, Ryanne Dolan <
> ryannedo...@gmail.com> wrote:
>
> Bump. We've got 4 non-binding and one binding vote.
>
> Ryanne
>
> On Fr
[
https://issues.apache.org/jira/browse/KAFKA-8564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edoardo Comar resolved KAFKA-8564.
--
Resolution: Fixed
Fix Version/s: 2.2.2
2.1.2
2.3.0
Thanks Andrew.
+1 (non-binding)
--
Edoardo Comar
IBM Event Streams
IBM UK Ltd, Hursley Park, SO21 2JN
From: Mickael Maison
To: dev
Date: 10/04/2019 10:14
Subject:Re: [VOTE] KIP-419: Safely notify Kafka Connect SourceTask
is
Well done Bill!
--
Edoardo Comar
IBM Event Streams
IBM UK Ltd, Hursley Park, SO21 2JN
From: Rajini Sivaram
To: dev
Date: 14/02/2019 09:25
Subject:Re: [ANNOUNCE] New Committer: Bill Bejeck
Congratulations, Bill!
On Thu, Feb
replicating the value as-is - it would edit it by
stripping the epoch.
As previously mentioned, the __consumer_offsets topic does not need to be
replicated by producing-with-offsets to it.
--
Edoardo Comar
IBM Event Streams
On Wed, 23 Jan 2019 at
Edoardo Comar created KAFKA-7861:
Summary: AlterConfig may change the source of another config entry
if it matches the broker default
Key: KAFKA-7861
URL: https://issues.apache.org/jira/browse/KAFKA-7861
Bravo Vahid!!!
Edo
From: Mickael Maison
To: Users
Cc: dev
Date: 16/01/2019 08:48
Subject:Re: [ANNOUNCE] New Committer: Vahid Hashemian
Congratulations Vahid! Well done!
On Wed, Jan 16, 2019 at 6:42 AM Dongjin Lee wrote:
>
> Congratulations, Vahid!!
>
> On Wed, Jan 16
+1 (non-binding)
Thanks Mickael!
On Tue, 8 Jan 2019 at 17:39, Patrik Kleindl wrote:
> +1 (non-binding)
> Thanks, sounds very helpful
> Best regards
> Patrik
>
> > Am 08.01.2019 um 18:10 schrieb Mickael Maison >:
> >
> > Hi all,
> >
> > I'd like to start the vote on KIP-396:
> >
> https://cwiki.
P-391
------
Edoardo Comar
IBM Event Streams
IBM UK Ltd, Hursley Park, SO21 2JN
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
Hi,
I delayed starting the voting thread due to the festive period. I would
like to start it this week.
Has anyone any more feedback ?
--
Edoardo Comar
IBM Event Streams
Edoardo Comar wrote on 13/12/2018 17:50:30:
> From: Edoardo Comar
&
+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
>
[
https://issues.apache.org/jira/browse/KAFKA-7761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edoardo Comar resolved KAFKA-7761.
--
Resolution: Duplicate
if there is a valid reason for a duplicate, feel free to repoen
> CL
ber of client connections on a
different listener.
do you think it would make sense to also allow the `num.network.threads`
to have an optional per-listener prefix ?
ciao,
Edo
--
Edoardo Comar
IBM Event Streams
IBM UK Ltd, Hursley Park, SO
Hi,
as we haven't got any more feedback, we'd like to start a vote on KIP-391
on Monday
https://cwiki.apache.org/confluence/display/KAFKA/KIP-391%3A+Allow+Producing+with+Offsets+for+Cluster+Replication
------
Edoardo Comar
IBM Event Stre
Edoardo Comar created KAFKA-7720:
Summary: kafka-configs script should also describe default broker
entries
Key: KAFKA-7720
URL: https://issues.apache.org/jira/browse/KAFKA-7720
Project: Kafka
(shameless bump) any additional feedback is welcome ... thanks!
Edoardo Comar wrote on 27/11/2018 15:35:09:
> From: Edoardo Comar
> To: dev@kafka.apache.org
> Date: 27/11/2018 15:35
> Subject: Re: [DISCUSS] KIP-391: Allow Producing with Offsets for
> Cluster Replication
>
-partition field in the Kafka ListOffsets
Request API
so you're not exposing the full APi power with the option
------
Edoardo Comar
IBM Event Streams
IBM UK Ltd, Hursley Park, SO21 2JN
From: Mickael Maison
To: dev
Date: 30/11/2018
ime offset be more generic?
> > your producers could checkpoint the last (say log append) timestamp of
> > records theyve seen, and when restoring in the remote site seek to
> > those timestamps (which will be metadata in their committed offsets) -
> > assumming replicatio
since this KIP seems to be designed fro active-passive
> > > failover (there can be no produce traffic except the replicator)
> > > wouldnt a solution based on seeking to a time offset be more
generic?
> > > your producers could checkpoint the last (say log append) timestamp
a in their committed offsets) -
> assumming replication takes > 0 time you'd need to handle some dups,
> but every kafka consumer setup needs to know how to handle those
> anyway.
can you please clarify?
We do not expect any cooperation from users applications.
thanks!
E&M
our interest !
cheers
Edo
----------
Edoardo Comar
IBM Event Streams
IBM UK Ltd, Hursley Park, SO21 2JN
Stanislav Kozlovski wrote on 22/11/2018 22:32:42:
> From: Stanislav Kozlovski
> To: dev@kafka.apache.org
> Date: 22/11/2018 22:33
> Subject: Re: [D
ffsets.
The flag is needed to distinguish a batch with a desired base offset of 0,
from a regular batch for which offsets need to be generated.
I would not restrict a principal to only send-with-offsets (by making that
mandatory via the ACL).
Thanks
Edo & Mickael
-------
al One, Goldman Sachs, ING, LinkedIn, Netflix, Pinterest, Rabobank,
> > Target, The New York Times, Uber, Yelp, and Zalando, among others.
> >
> > A big thank you for the following 100 contributors to this release!
> >
> > Ahmed Al Mehdi, Aleksei Izmalkin, Alex Dunayevsky, Ami
Edoardo Comar created KAFKA-7666:
Summary: KIP-391: Allow Producing with Offsets for Cluster
Replication
Key: KAFKA-7666
URL: https://issues.apache.org/jira/browse/KAFKA-7666
Project: Kafka
nd Mickael
------
Edoardo Comar
IBM Event Streams
IBM UK Ltd, Hursley Park, SO21 2JN
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth,
Thanks for the KIP. +1 (non-binding)
--
Edoardo Comar
IBM Event Streams
From: Harsha Chintalapani
To: Patrick Huang , dev@kafka.apache.org
Cc: "dev@kafka.apache.org"
Date: 30/10/2018 19:11
Subject:Re: [VOT
Well done Manikumar !
--
Edoardo Comar
IBM Event Streams
IBM UK Ltd, Hursley Park, SO21 2JN
From: "Matthias J. Sax"
To: dev
Cc: users
Date: 11/10/2018 23:41
Subject:Re: [ANNOUNCE] New Committer: Manik
Thanks Rajini for the PR review,
as agreed we have updated KIP-302 to match the code
so the new config value for the entry client.dns.lookup is
"use_all_dns_ips"
(underscores instead of dot separators)
------
Edoardo Comar
IBM Event Stre
Thanks Rajini for the PR review,
as agreed we have updated KIP-302 to match the code
so the new config value for the entry client.dns.lookup is
"use_all_dns_ips"
(underscores instead of dot separators)
cheers
Edo
------
Edoardo Comar
Hi Dong
many thanks for driving the release!
KIP-81 previously voted as adopted has a ready-to-review JIRA and PR.
Shall we just amend the wiki ?
--
Edoardo Comar
IBM Event Streams
IBM UK Ltd, Hursley Park, SO21 2JN
From: Dong Lin
To
Congratulations Colin !
--
Edoardo Comar
IBM Event Streams
IBM UK Ltd, Hursley Park, SO21 2JN
From: Ismael Juma
To: Kafka Users , dev
Date: 25/09/2018 09:40
Subject:[ANNOUNCE] New committer: Colin McCabe
Hi all,
The PMC
Many thanks to all that voted,
This KIP has passed the vote - within the COB of 24/09/2018 - with 3
binding votes (Rajini, Damian, Gwen) and 4 non-binding votes (Eno,
Jonathan and implicitly :-) Mickael and me)
Edo
--
Edoardo Comar
IBM Event
1 - 100 of 346 matches
Mail list logo
