r configs, with
> or without prefixes. So, we don't need to add the new config to
> StreamsConfig explicitly.
>
> For KIP-932, it says for each new consumer config, we need to determine
> whether it should be added to ShareConsumer config too.
>
> Thanks,
>
> Jun
>
> On We
> >> On 15 Apr 2024, at 14:16, Chris Egerton
> > wrote:
> > > >>
> > > >> Hi Ivan,
> > > >>
> > > >> Thanks for the KIP. After the recent changes, this LGTM. +1 (binding)
> > > >>
> > > >> Cheers,
>
; > > +1 (non-binding)
> > > > >
> > > > > Andrew
> > > > >
> > > > >> On 15 Apr 2024, at 14:16, Chris Egerton
> > > wrote:
> > > > >>
> > > > >> Hi Ivan,
> > > > >>
&g
[
https://issues.apache.org/jira/browse/KAFKA-16445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Yurchenko resolved KAFKA-16445.
Resolution: Fixed
> PATCH method for connector configurat
gt; > On Mon, Apr 8, 2024, 3:30 PM Chris Egerton
> > > wrote:
> > >
> > > > Thanks Ivan! +1 (binding) from me.
> > > >
> > > > On Mon, Apr 8, 2024, 06:59 Ivan Yurchenko wrote:
> > > >
> > > > > Hello!
> >
Congrats Greg!
On Sun, Apr 14, 2024, at 22:51, Sophie Blee-Goldman wrote:
> Congrats Greg! Happy to have you
>
> On Sun, Apr 14, 2024 at 9:26 AM Jorge Esteban Quilcate Otoya <
> quilcate.jo...@gmail.com> wrote:
>
> > Congrats, Greg!!
> >
> > On Sun 14. Apr 2024 at 15.05, Josep Prat
> > wrote:
gt; > be the best. I think there’s another KIP waiting to be written for
> > ensuring consistency of clusters, but
> > I think that wouldn’t conflict at all with this one.
> >
> > Thanks,
> > Andrew
> >
> > > On 9 Apr 2024, at 19:11, Ivan Yurchenko wrote:
ter ID, so I think
> removing that from this KIP might
> be the best. I think there’s another KIP waiting to be written for ensuring
> consistency of clusters, but
> I think that wouldn’t conflict at all with this one.
>
> Thanks,
> Andrew
>
> > On 9 Apr 2
gt;
> Thanks,
> Andrew
>
> > On 8 Apr 2024, at 18:24, Ivan Yurchenko wrote:
> >
> > Hello!
> >
> > I changed the KIP a bit, specifying that the certain benefit goes to
> > consumers not participating in a group, but that other clients can benefit
&g
/diffpagesbyversion.action?pageId=240881396=10=11
On 2023/07/15 16:37:52 Ivan Yurchenko wrote:
> Hello!
>
> I've made several changes to the KIP based on the comments:
>
> 1. Reduced the scope to producer and consumer clients only.
> 2. Added more details to the description of the r
Hello!
I'd like to put the subj KIP[1] to a vote. Thank you.
Best regards,
Ivan
[1]
https://cwiki.apache.org/confluence/display/KAFKA/KIP-477%3A+Add+PATCH+method+for+connector+config+in+Connect+REST+API
ing the KIP on fixing this.
>
> One final nit: Can you update the Jira ticket link in the KIP?
>
> Cheers,
>
> Chris
>
> On Wed, Mar 27, 2024 at 2:56 PM Ivan Yurchenko wrote:
>
> > Hi,
> >
> > I updated the KIP with the two following changes:
&g
Ivan Yurchenko created KAFKA-16445:
--
Summary: PATCH method for connecto configuration
Key: KAFKA-16445
URL: https://issues.apache.org/jira/browse/KAFKA-16445
Project: Kafka
Issue Type
idea. I can update the KIP.
>
> Ivan
>
>
> On Tue, Mar 26, 2024, at 14:19, Ivan Yurchenko wrote:
> > Hi all,
> >
> > This KIP is a bit old now :) but I think its context hasn't changed much
> > since then and the KIP is still valid. I would like to finall
Congrats!
On Tue, Mar 26, 2024, at 14:48, Lucas Brutschy wrote:
> Congrats!
>
> On Tue, Mar 26, 2024 at 2:44 PM Federico Valeri wrote:
> >
> > Congrats!
> >
> > On Tue, Mar 26, 2024 at 2:27 PM Mickael Maison
> > wrote:
> > >
> > > Congratulations Christo!
> > >
> > > On Tue, Mar 26, 2024 at
acters "null") as the value for to-be-removed
> properties.
This actually makes sense. AFAIU, `null` cannot be in the connector config
since https://github.com/apache/kafka/pull/11333, so using it as a tombstone
value is a good idea. I can update the KIP.
Ivan
On Tue, Mar 26, 2024, at 14
sted in driving it, Ivan.
> Hopefully we can give it the attention it deserves in the upcoming months!
>
> Cheers,
>
> Chris
>
> On Fri, Jun 28, 2019 at 4:56 AM Ivan Yurchenko
> wrote:
>
> > Thank you for your feedback Ryanne!
> > These are all surely valid conce
Ivan Yurchenko created KAFKA-15931:
--
Summary: Cached transaction index gets closed if tiered storage
read is interrupted
Key: KAFKA-15931
URL: https://issues.apache.org/jira/browse/KAFKA-15931
Hello!
`RemoteStorageManager.fetchLogSegment` is called in a background thread by the
broker [1]. When a fetch request times out, the associated Future is cancelled
[2] and the thread is interrupted. If the InterruptedException is propagated
from the `RemoteStorageManager`, it pollutes the
Congrats Satish!
Ivan
On Fri, Oct 27, 2023, at 19:02, Kamal Chandraprakash wrote:
> Congratulations Satish!
>
> On Fri, Oct 27, 2023, 21:10 Jorge Esteban Quilcate Otoya <
> quilcate.jo...@gmail.com> wrote:
>
> > Congratulations Satish!!
> >
> > On Fri, 27 Oct 2023 at 18:38, Mickael Maison
> >
Hi David,
I wonder if you considered interceptors that work not only on produce request,
but on any request type the broker is receiving (apart from maybe internal
request types). For example, being able to rewrite topic names in all the
request types is essential to create a virtual clusters
Hi David and Ahmed,
First, thank you David for the KIP. It would be very valuable for multiple use
cases. Products like Conduktor Gateway [1] validate the demand and offer many
potential use cases [2].
Now, I understand Ahmed's concerns about possible in-band interruptions, the
are valid.
Hi Satish and all,
I wonder if https://issues.apache.org/jira/browse/KAFKA-14993 should be
included in the 3.6 release plan. I'm thinking that when implemented, it would
be a small, but still a change in the RSM contract: throw an exception instead
of returning an empty InputStream. Maybe it
Hello,
The discussion [1] for KIP-899 [2] has been open for quite some time. I'd
like to put the KIP up for a vote.
Best,
Ivan
[1] https://lists.apache.org/thread/m0ncbmfxs5m87sszby2jbmtjx2bdpcdl
[2]
rap only after "
>> metadata.max.age.ms" has elapsed since the last metadata update, and when
>> at least one request has been made to contact each known server and been
>> met with failure?
>>
>> [1] -
>>
>> https://github.com/apache/kafka/blob/c9a42c8
Hi!
For those who are interested, I submitted the PR with the implementation:
https://github.com/apache/kafka/pull/13984
Thanks!
Ivan
On Tue, 13 Jun 2023 at 15:05, Ivan Yurchenko
wrote:
> Hi Satish,
>
> I understand your point and I agree with it. TBH, I didn't take into
t;under discussion" to "approved" and 3.6.0 as the
> version.
>
> Best,
>
> On Mon, Jun 19, 2023 at 12:20 PM Ivan Yurchenko
> wrote:
>
> > Hi all,
> >
> > Thank you for your votes.
> >
> > The voting has been open for 7 days and we have:
hanks,
> Satish.
>
> On Mon, 19 Jun 2023 at 16:03, Ivan Yurchenko
> wrote:
> >
> > Hi,
> >
> > I would like to propose to include the newly accepted "KIP-917:
> Additional
> > custom metadata for remote log segment" [1] in the release plan. W
Ivan Yurchenko created KAFKA-15107:
--
Summary: Additional custom metadata for remote log segment
Key: KAFKA-15107
URL: https://issues.apache.org/jira/browse/KAFKA-15107
Project: Kafka
Issue
Hi,
I would like to propose to include the newly accepted "KIP-917: Additional
custom metadata for remote log segment" [1] in the release plan. Would it
be possible?
Thanks!
Best,
Ivan
[1]
van for addressing the comments in the KIP, LGTM.
>
> +1
>
> On Tue, 13 Jun 2023 at 18:31, Luke Chen wrote:
> >
> > Looks good. Thanks for the update.
> >
> > On Tue, Jun 13, 2023 at 8:08 PM Ivan Yurchenko >
> > wrote:
> >
> > > Hi all!
> >
would be beneficial
> to
> > > > > implement.
> > > > >
> > > > > Vote +1 (non-binding)
> > > > >
> > > > >
> > > > > --
> > > > > Divij Vaidya
> > > > >
> > > >
ata with
> each segment.
>
> ~Satish.
>
>
> On Wed, 7 Jun 2023 at 23:38, Ivan Yurchenko
> wrote:
> >
> > Hi Satish,
> >
> > Thank you for your feedback.
> >
> > I've nothing against going from Map to byte[].
> > Serialization should not be a pro
Hi all
FYI, I opened this for a vote:
https://lists.apache.org/thread/pnrkgomomwb03h8pfgs0k7dzwgpbtloz
On Tue, 13 Jun 2023 at 08:01, Ivan Yurchenko
wrote:
> Hi Luke,
>
> > I saw you add the `RemoteLogSegmentMetadataRecord` and
> > `RemoteLogSegmentMetadataSnapshotRecord`, I
being added in the KIP will be the one affecting
> the public interface, ex: API request/response.
> So I'd like to confirm it.
>
>
> Thanks.
> Luke
>
> On Thu, Jun 8, 2023 at 2:09 AM Ivan Yurchenko
> wrote:
> >
> > Hi Satish,
> >
> > Thank you for your
Hello,
Some interest in KIP-917 was expressed in the discussion thread [1]. After
addressing all the comments there, I'm putting it up to a vote.
Thanks!
Best,
Ivan
[1] https://lists.apache.org/thread/qpccqd3jy5rzvbt5ngtzo3dg9pzp722y
ue and it is the RSM implementation provider's
> responsibility in serializing and deserializing the bytes. We can
> introduce a property to guard the size with a configurable property
> with a default value to avoid any unwanted large size values.
>
> Thanks,
> Satish.
>
> On Tue, 30 Ma
Hi all,
I want to bring this to a conclusion (positive or negative), so if there
are no more questions in a couple of days, I'll put the KIP to the vote.
Best,
Ivan
On Fri, 5 May 2023 at 18:42, Ivan Yurchenko
wrote:
> Hi Alexandre,
>
> > combining custom
> > metadat
the last metadata update, and when
> at least one request has been made to contact each known server and been
> met with failure?
>
> [1] -
>
> https://github.com/apache/kafka/blob/c9a42c85e2c903329b3550181d230527e90e3646/clients/src/main/java/org/apache/kafka/clients/admin/in
lt. What do you think?
>
> I have a vague memory of this being discussed back when the tiered
> storage KIP was started. Maybe Satish has more background on this.
>
> Thanks,
> Alexandre
>
> Le lun. 17 avr. 2023 à 16:50, Ivan Yurchenko
> a écrit :
> >
> > Hi Alex
.
>
> Thanks,
> Alexandre
>
> Le jeu. 6 avr. 2023 à 16:03, hzh0425 a écrit :
> >
> > I think it's a good idea as we may want to store remote segments in
> different buckets
> >
> >
> >
> > | |
> > hzhka...@163.com
> > |
> > |
>
Hello!
I would like to start the discussion thread on KIP-917: Additional custom
metadata for remote log segment [1]
This KIP is fairly small and proposes to add a new field to the remote
segment metadata.
Thank you!
Best,
Ivan
[1]
Ivan Yurchenko created KAFKA-14795:
--
Summary: Provide message formatter for RemoteLogMetadata
Key: KAFKA-14795
URL: https://issues.apache.org/jira/browse/KAFKA-14795
Project: Kafka
Issue
uster a second time. With that second attempt, would we
> immediately resort to the bootstrap servers for any initial metadata
> updates, or would we still try to go through the last-known set of brokers
> first?
>
> Cheers,
>
> Chris
>
> On Mon, Feb 6, 2023 at 4:32 AM Ivan
Hi!
There seems to be not much more discussion going, so I'm planning to start
the vote in a couple of days.
Thanks,
Ivan
On Wed, 18 Jan 2023 at 12:06, Ivan Yurchenko
wrote:
> Hello!
> I would like to start the discussion thread on KIP-899: Allow clients to
> rebootstrap.
> This
nstantiate a new one
> when needed? I'm not familiar with the stream thread, so I don't know if
> that's possible. Another idea here is, would it make sense to expose a
> maybeUpdateMetadata() API to serve such a purpose?
>
> Thanks,
> P
>
>
> On Wed, Jan 18, 2023 at 4:0
a reproducible manual test or by a branch with a
> failing unit/integration test?
>
> Best,
> Christo
>
> > On 18 Jan 2023, at 12:07, Ivan Yurchenko
> wrote:
> >
> > Hello!
> > I would like to start the discussion thread on KIP-899: Allow clients to
> >
Hello!
I would like to start the discussion thread on KIP-899: Allow clients to
rebootstrap.
This KIP proposes to allow Kafka clients to repeat the bootstrap process
when fetching metadata if none of the known nodes are available.
Hi,
Thank you for the KIP.
+1 (non-binding)
Ivan
On Tue, 23 Nov 2021 at 04:18, Luke Chen wrote:
> Hi Matthew,
> Thanks for the KIP.
> It makes sense to allow IPv4 and IPv6 listening on the same port for the
> listener config.
>
> +1 (non-binding)
>
> Thank you.
> Luke
>
> On Mon, Nov 22,
Ivan Yurchenko created KAFKA-13376:
--
Summary: Allow MirrorMaker producer and consumer customization per
replication flow
Key: KAFKA-13376
URL: https://issues.apache.org/jira/browse/KAFKA-13376
Hi Randall,
Could you please share the JIRA ticket or the fixing commit? It might help
to evaluate the impact better.
Thank you!
Ivan
On Tue, 21 Sept 2021 at 19:37, Randall Hauch wrote:
> Severity: moderate
>
> Description:
>
> Some components in Apache Kafka use `Arrays.equals` to validate
the suggestion earlier. I think this will be a great idea
> > for a KIP.
> >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals
> >
> > You were referring to metadata for the actual topic and not its contents.
> >
> > Sorry about th
Hi,
Having metadata for topics seems pretty useful. Currently, one has to use
external storage for this (e.g. a database) and the question of keeping
topic and metadata in sync exists: A topic is deleted, how to delete its
metadata? How to deal with delete-then-recreate scenarios (well, we have
Ivan Yurchenko created KAFKA-12835:
--
Summary: Topic IDs can mismatch on brokers (after interbroker
protocol version update)
Key: KAFKA-12835
URL: https://issues.apache.org/jira/browse/KAFKA-12835
Ivan Yurchenko created KAFKA-12430:
--
Summary: emit.heartbeats.enabled = false should disable heartbeats
topic creation
Key: KAFKA-12430
URL: https://issues.apache.org/jira/browse/KAFKA-12430
Project
Hi,
Great!
+1 (non-binding)
Best,
Ivan
On Mon, 15 Feb 2021 at 22:47, Kowshik Prakasam wrote:
> +1 (non-binding). Thanks for the excellent KIP!
>
>
> Cheers,
> Kowshik
>
>
>
>
>
> On Mon, Feb 15, 2021 at 2:50 AM Manikumar
> wrote:
>
> > Hi Satish,
> >
> > Thanks for driving this KIP. I’m sure
Ivan Yurchenko created KAFKA-12235:
--
Summary: ZkAdminManager.describeConfigs returns no config when 2+
configuration keys are specified
Key: KAFKA-12235
URL: https://issues.apache.org/jira/browse/KAFKA-12235
Ivan Yurchenko created KAFKA-9672:
-
Summary: Dead broker in ISR cause isr-expiration to fail with
exception
Key: KAFKA-9672
URL: https://issues.apache.org/jira/browse/KAFKA-9672
Project: Kafka
Ivan Yurchenko created KAFKA-9478:
-
Summary: Controller may stop react on partition reassignment
command in ZooKeeper
Key: KAFKA-9478
URL: https://issues.apache.org/jira/browse/KAFKA-9478
Project
Hi all,
Jun:
> (a) Cost: S3 list object requests cost $0.005 per 1000 requests. If you
> have 100,000 partitions and want to pull the metadata for each partition
at
> the rate of 1/sec. It can cost $0.5/sec, which is roughly $40K per day.
I want to note here, that no reasonably durable storage
Hi Jun and others.
Jun,
All these are really valid concerns.
Probably we should think about backing implementations like S3 with a
metadata storage whose consistency model and pricing is better that pure
S3, maybe even a Kafka topic (I guess this might be something you refer to
as push-based
Do I understand correctly, that non-commiters can also vote, despite their
votes don't decide?
If so, then +1 from me.
Ivan
On Mon, 18 Nov 2019 at 15:19, Ismael Juma wrote:
> Hi all,
>
> People seemed supportive in general, so I'd like to start a vote on
> KIP-531:
>
>
>
Ivan Yurchenko created KAFKA-9143:
-
Summary: DistributedHerder misleadingly log error on connector
task reconfiguration
Key: KAFKA-9143
URL: https://issues.apache.org/jira/browse/KAFKA-9143
Project
Ivan Yurchenko created KAFKA-9035:
-
Summary: Improve
Key: KAFKA-9035
URL: https://issues.apache.org/jira/browse/KAFKA-9035
Project: Kafka
Issue Type: Improvement
Components
Connect.
An alternative would be to just write your own application that reads from
Kafka and writes to MQTT or vice versa using Kafka's producers and
consumers.
I hope this helps!
Best,
Ivan Yurchenko
[1] https://kafka.apache.org/documentation/#connect
[2] https://docs.lenses.io/connectors/sink
.
>
> about question 2, i'm not following what did you mean about "byte level",
> could you plz to make more explanations?
>
> Best,
> Lisheng
>
>
> Ivan Yurchenko 于2019年8月30日周五 下午8:39写道：
>
> > Hi,
> >
> > Let's say I have a topic-pa
Hi,
Let's say I have a topic-partition replicated to several replicas. On each
replica there is a segment of this topic-partition containing records with
offsets N..M. I'm trying to figure out:
1. Will the content of these segment files be identical on the logical
level? I.e., will they contain
n-racy way.
>
> So I don't think PATCH is strictly necessary nor sufficient for atomic
> partial updates. That said, it doesn't hurt and I'm happy to support the
> KIP.
>
> Ryanne
>
> On Tue, Jun 25, 2019 at 12:15 PM Ivan Yurchenko
> wrote:
>
> > Hi,
> >
&
Hi,
Since Kafka 2.3 has just been release and more people may have time to look
at this now, I'd like to bump this discussion.
Thanks.
Ivan
On Thu, 13 Jun 2019 at 17:20, Ivan Yurchenko
wrote:
> Hello,
>
> I'd like to start the discussion of KIP-477: Add PATCH method for
> conn
Hello,
I'd like to start the discussion of KIP-477: Add PATCH method for connector
config in Connect REST API.
https://cwiki.apache.org/confluence/display/KAFKA/KIP-477%3A+Add+PATCH+method+for+connector+config+in+Connect+REST+API
There is also a draft PR:
Hi,
I'd like to be able to create KIPs. Could someone please set up the
permissions for me? The username is ivanyu .
Thanks!
Ivan
Hello,
Could somebody add me to the Kafka contributor list so I can assign myself
tickets in JIRA? My ID/username is ivanyu.
Thank you.
Best,
Ivan
Hello,
Could somebody add me to the Kafka contributor list so I can assign myself
tickets in JIRA? My ID/username is ivanyu.
Thank you.
Best,
Ivan
73 matches
Mail list logo
