[
https://issues.apache.org/jira/browse/KAFKA-14567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853201#comment-17853201
]
Matthias J. Sax edited comment on KAFKA-14567 at 6/7/24 4:14 PM
[
https://issues.apache.org/jira/browse/KAFKA-14567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853201#comment-17853201
]
Matthias J. Sax commented on KAFKA-14567:
-
[~cadonna] – you recent fix should address this issue
[
https://issues.apache.org/jira/browse/KAFKA-16911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-16911:
Description:
The docs for topology optimization are incomplete:
[https
Matthias J. Sax created KAFKA-16911:
---
Summary: Kafka Streams topology optimization docs incomplete
Key: KAFKA-16911
URL: https://issues.apache.org/jira/browse/KAFKA-16911
Project: Kafka
Matthias J. Sax created KAFKA-16911:
---
Summary: Kafka Streams topology optimization docs incomplete
Key: KAFKA-16911
URL: https://issues.apache.org/jira/browse/KAFKA-16911
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-16903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax resolved KAFKA-16903.
-
Resolution: Fixed
> Task should consider producer error previously occur
[
https://issues.apache.org/jira/browse/KAFKA-16903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-16903:
Fix Version/s: 3.8.0
> Task should consider producer error previously occur
[
https://issues.apache.org/jira/browse/KAFKA-16903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax resolved KAFKA-16903.
-
Resolution: Fixed
> Task should consider producer error previously occur
[
https://issues.apache.org/jira/browse/KAFKA-16811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17852531#comment-17852531
]
Matthias J. Sax commented on KAFKA-16811:
-
Let's more the discussion on the PR
> Punctu
[
https://issues.apache.org/jira/browse/KAFKA-16811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17852231#comment-17852231
]
Matthias J. Sax commented on KAFKA-16811:
-
[~ganesh_6] – WordCountProcessorDemo does not contain
[
https://issues.apache.org/jira/browse/KAFKA-16874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-16874:
Component/s: streams
> Remove old TaskAssignor interf
[
https://issues.apache.org/jira/browse/KAFKA-15905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-15905:
Fix Version/s: 3.8.0
(was: 3.8)
> Restarts of MirrorCheckpointT
[
https://issues.apache.org/jira/browse/KAFKA-16622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-16622:
Fix Version/s: 3.8.0
(was: 3.8)
> Mirromaker2 first Checkpo
[
https://issues.apache.org/jira/browse/KAFKA-16757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-16757:
Fix Version/s: 3.8.0
(was: 3.8)
> Fix broker re-registrat
[
https://issues.apache.org/jira/browse/KAFKA-16692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-16692:
Fix Version/s: 3.8.0
(was: 3.8)
> InvalidRequestExcept
[
https://issues.apache.org/jira/browse/KAFKA-15045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-15045:
Fix Version/s: 3.8.0
> Move Streams task assignor to public conf
[
https://issues.apache.org/jira/browse/KAFKA-16875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-16875:
Component/s: streams
> Replace ClientState with TaskAssignment when creating individ
[
https://issues.apache.org/jira/browse/KAFKA-16873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-16873:
Component/s: streams
> Remove StreamsConfig.INTERNAL_TASK_ASSIGNOR_CL
[
https://issues.apache.org/jira/browse/KAFKA-16872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-16872:
Component/s: streams
> Remove ClientState cl
[
https://issues.apache.org/jira/browse/KAFKA-16871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-16871:
Component/s: streams
> Clean up internal AssignmentConfigs class in Stre
[
https://issues.apache.org/jira/browse/KAFKA-16868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-16868:
Component/s: streams
> Post KIP-924 StreamsPartitionAssignor code clea
Jiang,
Thanks for the KIP. I think it make sense. I agree with Sophie that the
KIP writeup should be improved a little bit, with regard to public API
(ie, config) which are changed.
The only other idea I had to avoid this issue would be some internal
change: we would introduce a new logger
Ayoub,
thanks for resurrecting this KIP. I think a built-in de-duplication
operator will be very useful.
Couple of questions:
100: `deduplicationKeySelector`
Is this the best name? It might indicate that we select a "key" what is
an overloaded term... Maybe we could use `Field` or `Id`
going to be working on 1035 starting today.
I'll update the KIP first, and then call a vote.
Regards,
Nick
On Wed, 29 May 2024 at 07:25, Bruno Cadonna wrote:
Totally agree on moving forward and starting the VOTE!
However, the KIP should be updated with the new info before starting the
VOT
_TASK_ASSIGNED_MULTIPLE_TIMES,
ACTIVE_AND_STANDBY_TASK_ASSIGNED_TO_SAME_KAFKASTREAMS,
INVALID_STANDBY_TASK,
UNKNOWN_PROCESS_ID,
UNKNOWN_TASK_ID
}
Anything missing?
(also updated all the code block headings, thanks for noticing that
Bruno)
On Fri, May 3, 2024 at 9
Chris,
Subscription is self-service. Please follow the instruction from the web
page: https://kafka.apache.org/contact
-Matthias
On 6/3/24 1:59 AM, Chris wrote:
[
https://issues.apache.org/jira/browse/KAFKA-16248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax reassigned KAFKA-16248:
---
Assignee: Alieh Saeedi
> Kafka consumer should cache leader offset ran
[
https://issues.apache.org/jira/browse/KAFKA-16863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850869#comment-17850869
]
Matthias J. Sax commented on KAFKA-16863:
-
I think `traffic_cost` was on purpose... But I really
Matthias J. Sax created KAFKA-16863:
---
Summary: Consider removing `default.` prefix for exception handler
config
Key: KAFKA-16863
URL: https://issues.apache.org/jira/browse/KAFKA-16863
Project
Matthias J. Sax created KAFKA-16863:
---
Summary: Consider removing `default.` prefix for exception handler
config
Key: KAFKA-16863
URL: https://issues.apache.org/jira/browse/KAFKA-16863
Project
due to the expected higher latency since it
happens actually before the Kafka Streams client joins the rebalance.
Best,
Bruno
On 5/4/24 12:05 AM, Matthias J. Sax wrote:
That's good questions... I could think of a few approaches, but I
admit
it might all be a little bit tricky to code up...
H
Mailing list subscription is self-service. Please follow the instruction
from the web-page: https://kafka.apache.org/contact
-Matthias
On 5/21/24 2:00 AM, Prashant Lohia wrote:
thanks
prashant lohia
prash...@gsl.in
of the application will
process records? For example, if the input topics each have 6 partitions,
and I use the repartition method to set the number of partitions for the
streams to 2, how many instances of the application will process records?
Thanks,
Chad
On Wed, May 1, 2024 at 6:47 PM Matthias J. Sax
[
https://issues.apache.org/jira/browse/KAFKA-16586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848476#comment-17848476
]
Matthias J. Sax commented on KAFKA-16586:
-
I did suspect a bug, too, and did include the seed
[
https://issues.apache.org/jira/browse/KAFKA-16586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-16586:
Description:
{code:java}
java.lang.AssertionError: Assertion failed in randomized test
/main/src/test/java/com/example/demo/MyFixedKeyProcessorTest.java
On Mon, May 20, 2024 at 9:05 PM Matthias J. Sax wrote:
Had a discussion on https://issues.apache.org/jira/browse/KAFKA-15242
and it was pointed out, that we also need to do something about
`FixedKeyRecord`. It does not have
You should be all set.
On 5/21/24 8:30 AM, Harry Fallows wrote:
Hello,
I am following the[Getting Started guide for writing
KIPs](https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals).
Could someone give me the permissions to write a KIP please? My Wiki ID is
You should be all set.
On 5/21/24 6:58 PM, 黃竣陽 wrote:
I want to create a KIP, and my
wiki id : m1a2st and Jira id : m1a2st, Thanks for your help.
jiang dou 於 2024年5月22日 上午9:01 寫道:
You should send your jira ID and wiki ID,
Please refer to this address :
_____
From: Matthias J. Sax
Sent: Saturday, May 18, 2024 4:06
To: users@kafka.apache.org
Subject: Re: 回复: Request to be added to kafka contributors list
Did you sign out and sign in again?
On 5/17/24 9:49 AM, Yang Fan wrote:
Thanks Matthias,
I still can't find "Assign to me" button beside A
[
https://issues.apache.org/jira/browse/KAFKA-15242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax resolved KAFKA-15242.
-
Assignee: (was: Alexander Aghili)
Resolution: Duplicate
> FixedKeyProces
[
https://issues.apache.org/jira/browse/KAFKA-15242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax resolved KAFKA-15242.
-
Assignee: (was: Alexander Aghili)
Resolution: Duplicate
> FixedKeyProces
Done. You should be all set :)
-Matthias
On 5/20/24 10:10 AM, bou...@ulukai.net wrote:
Dear Apache Kafka Team,
I hope to post in the right place: my name is Franck LEDAY, under
Apache-Jira ID "handfreezer".
I opened an issue as Improvement KAFKA-16707 but I failed to
assigned
What is your Jira ID?
-Matthias
On 5/20/24 9:55 AM, Brenden Deluna wrote:
Hello, I am requesting to be added to the contributor list to take care of
some tickets. Thank you.
Zookeeper is already deprecated (since 3.5):
https://kafka.apache.org/documentation/#zk_depr
It's planned to be fully removed in 4.0 release.
It's not confirmed yet, but there is a high probability that there won't
be a 3.9 release, and that 4.0 will follow 3.8.
-Matthias
On 5/20/24 2:11
[
https://issues.apache.org/jira/browse/KAFKA-16801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848022#comment-17848022
]
Matthias J. Sax commented on KAFKA-16801:
-
There packages contain code for system tests. We put
[
https://issues.apache.org/jira/browse/KAFKA-16794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-16794:
Component/s: streams
> Can't open videos in streams documentat
would extend `FixedKeyRecord`? -- Or maybe an even better solution? I
could not think of something else so far.
Thoughts?
On 5/3/24 9:46 AM, Matthias J. Sax wrote:
Please also update the KIP.
To get a wiki account created, please request it via a commet on this
ticket: https
[
https://issues.apache.org/jira/browse/KAFKA-15143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848021#comment-17848021
]
Matthias J. Sax commented on KAFKA-15143:
-
As pointed out on KAFKA-15242 cf comments, we also
[
https://issues.apache.org/jira/browse/KAFKA-15242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848020#comment-17848020
]
Matthias J. Sax commented on KAFKA-15242:
-
I don't think that `TestRecord` has anything to do
Did you sign out and sign in again?
On 5/17/24 9:49 AM, Yang Fan wrote:
Thanks Matthias,
I still can't find "Assign to me" button beside Assignee and Reporter. Could
you help me set it again?
Best regards,
Fan
发件人: Matthias J. Sax
发送时间: 2024年5月17
[
https://issues.apache.org/jira/browse/KAFKA-16774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847064#comment-17847064
]
Matthias J. Sax commented on KAFKA-16774:
-
Ah. Nice. Glad it's not a bug. Thanks for the PR
[
https://issues.apache.org/jira/browse/KAFKA-15242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847063#comment-17847063
]
Matthias J. Sax commented on KAFKA-15242:
-
The example
([https://github.com/zveljkovic/kafka
of a more obvious metric name.
Nit: the KIP says it's a store-level metric, but I think it
would
be
good to say explicitly that it's recorded with DEBUG level only?
Yes, I've already updated the KIP with this information in the
table.
Regards,
Nick
On Sun, 31 Mar 2024 at 10:53, Matthias J. S
Hello Kay,
What you describe is "by design" -- unfortunately.
The problem is, that when we build the `Topology` we don't know the
partition count of the input topics, and thus, StreamsBuilder cannot
insert a repartition topic for this case (we always assume that the
partition count is the
Thanks for reaching out Yang. You should be all set.
-Matthias
On 5/16/24 7:40 AM, Yang Fan wrote:
Dear Apache Kafka Team,
I hope this email finds you well. My name is Fan Yang, JIRA ID is fanyan, I
kindly request to be added to the contributors list for Apache Kafka. Being
part of this
[
https://issues.apache.org/jira/browse/KAFKA-16448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax reassigned KAFKA-16448:
---
Assignee: Loïc Greffier
> Add Kafka Streams exception handler for excepti
[
https://issues.apache.org/jira/browse/KAFKA-16333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846821#comment-17846821
]
Matthias J. Sax commented on KAFKA-16333:
-
In general yes. But we should wait until a final
[
https://issues.apache.org/jira/browse/KAFKA-16329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846820#comment-17846820
]
Matthias J. Sax commented on KAFKA-16329:
-
In general yes. But we should wait until a final
[
https://issues.apache.org/jira/browse/KAFKA-16330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846819#comment-17846819
]
Matthias J. Sax commented on KAFKA-16330:
-
In general yes. But we should wait until a final
[
https://issues.apache.org/jira/browse/KAFKA-16448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846818#comment-17846818
]
Matthias J. Sax commented on KAFKA-16448:
-
[~muralibasani] – Thanks for you interest
[
https://issues.apache.org/jira/browse/KAFKA-16774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846815#comment-17846815
]
Matthias J. Sax commented on KAFKA-16774:
-
Wondering if this is actually a flaky test
[
https://issues.apache.org/jira/browse/KAFKA-16774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-16774:
Labels: flaky-test (was: )
> fix flaky StreamThreadT
[
https://issues.apache.org/jira/browse/KAFKA-16774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-16774:
Component/s: streams
unit tests
> fix flaky StreamThreadT
[
https://issues.apache.org/jira/browse/KAFKA-15242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846814#comment-17846814
]
Matthias J. Sax edited comment on KAFKA-15242 at 5/16/24 5:32 AM
[
https://issues.apache.org/jira/browse/KAFKA-15242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846814#comment-17846814
]
Matthias J. Sax commented on KAFKA-15242:
-
There is https://issues.apache.org/jira/browse/KAFKA
If I read this correctly, your upstream producer which writes into the
input topic of you KS app is using a custom partitioner?
If you do a `groupByKey()` and change the key upstream, it would result
in a repartition step, which would fall back to the default partioner.
If you want to use a
+1 (binding)
On 5/14/24 9:19 AM, Lucas Brutschy wrote:
Hi Nick!
Thanks for the KIP.
+1 (binding)
On Tue, May 14, 2024 at 5:16 PM Nick Telford wrote:
Hi everyone,
I'd like to call a vote on the Kafka Streams KIP-989: RocksDB Iterator
Metrics:
+1 (binding)
On 5/13/24 5:54 PM, Sophie Blee-Goldman wrote:
Thanks for the KIP guys!
+1 (binding)
On Mon, May 13, 2024 at 6:02 AM Bill Bejeck wrote:
Thanks for the KIP, this will be a great addition!
+1(binding)
-Bill
On Fri, May 3, 2024 at 4:48 AM Bruno Cadonna wrote:
Hi Damien,
[
https://issues.apache.org/jira/browse/KAFKA-16584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17845111#comment-17845111
]
Matthias J. Sax commented on KAFKA-16584:
-
I am on the PMC and can help you. :)
After you wiki
Self-service to create an account is currently not working. Please reply
on https://issues.apache.org/jira/browse/INFRA-25451 to request a wiki
account.
I'll update the wiki page for now until the issue is resolved.
-Matthias
On 5/7/24 8:25 AM, 黃竣陽 wrote:
Hello, I want to create a KIP, but
ProductionExceptionHandler...
Just explaining my reasoning -- in the end I leave it up to the KIP authors
and anyone who will actually be using this feature in their applications :)
On Tue, May 7, 2024 at 8:35 PM Matthias J. Sax wrote:
@Loic, yes, what you describe is exactly what I had i
rRecord as the input parameter of the
handle()
method
as
well.
- increased the response types to 3 to have fail and two
types
of
continue.
- The default behaviour is having no custom handler,
having
the
corresponding config parameter set to null. Therefore, the
KIP
provides
no
default
@Loic, yes, what you describe is exactly what I had in mind.
@Sophie, can you elaborate a little bit?
First of all, I agree that it makes sense to maintain the two separate
callbacks for the ProductionExceptionHandler, since one of them is
specifically for serialization exceptions while the
On 5/3/24 6:29 PM, Matthias J. Sax wrote:
101: Yes, but what I am saying is, that we don't need to flush the
.position file to disk periodically, but only maintain it in main
memory, and only write it to disk on close() to preserve it across
restarts. This way, it would never be ahead
-3910-4c25-bfad-ea2b98953db3-StreamThread-9
Message: [Consumer
clientId=kafka-streams-exec-0-test-store-6d676cf0-3910-4c25-bfad-ea2b98953db3-StreamThread-9-consumer,
groupId=kafka-streams-exec-0-test-store ] Node 102 disconnected.
On Mon, Apr 22, 2024 at 7:16 AM Matthias J. Sax wrote
, May 1, 2024 at 11:00 PM Matthias J. Sax wrote:
Any updates on this KIP?
On 3/28/24 4:11 AM, Matthias J. Sax wrote:
It seems that `MockRecordMetadata` is a private class, and thus not part
of the public API. If there are any changes required, we don't need to
discuss on the KIP
:43 AM, Matthias J. Sax wrote:
Thanks Sophie. My bad. You are of course right about `TaskAssignment`
and the StreamsPartitionAssignor's responsibitliy to map tasks of a
instance to consumers. When I wrote my reply, I forgot about this detail.
Seems you did not add `UNKNOWN_TASK_ID` error yet as pr
eams/state/internals/RocksDBStore.java#L397
On 5/1/24 3:00 AM, Matthias J. Sax wrote:
Thanks Bruno.
101: I think I understand this better now. But just want to make sure
I do. What do you mean by "they can diverge" and "Recovering after a
failure might load inconsistent offse
+1 (binding)
On 5/3/24 8:52 AM, Federico Valeri wrote:
Hi Fred, this is a useful addition.
+1 non binding
Thanks
On Fri, May 3, 2024 at 4:11 PM Andrew Schofield
wrote:
Hi Fred,
Thanks for the KIP. It’s turned out nice and elegant I think. Definitely a
worthwhile improvement.
+1
What about (106) to unify both exiting callback methods of
`ProductionExceptionHandler` into a single one, instead of adding two
new ones?
Damien's last reply about it was:
I will think about unifying, I do agree it would be cleaner.
There was not follow up on this question, and the KIP
I left one more nit on the discuss thread. But overall LGTM.
+1 (binding)
Thanks Rohan and Sophie for driving this KIP.
-Matthias
On 4/29/24 2:07 PM, Sophie Blee-Goldman wrote:
+1 (binding)
thanks for driving this KIP!
On Tue, Apr 16, 2024 at 1:46 PM Rohan Desai wrote:
have a lower level indention? It caught me for a sec until I
realized there are just two categories.
* In TaskAssignmentUtils , why not let those util functions return
`TaskAssignment` (to me it feels more consistent with the user APIs),
but instead return a Map?
Guozhang
On Tue, Apr 30, 2024
[
https://issues.apache.org/jira/browse/KAFKA-16260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-16260:
Component/s: clients
> Deprecate window.size.ms and window.inner.serde.cl
[
https://issues.apache.org/jira/browse/KAFKA-16260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-16260:
Description:
{{window.size.ms}} and {{window.inner.serde.class}} are not a true
[
https://issues.apache.org/jira/browse/KAFKA-16260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-16260:
Description:
{{indwindow.size.ms}} and `is not a true KafkaStreams config, and results
[
https://issues.apache.org/jira/browse/KAFKA-16260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-16260:
Description:
{{window.size.ms}} and `is not a true KafkaStreams config, and results
[
https://issues.apache.org/jira/browse/KAFKA-16260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-16260:
Summary: Deprecate window.size.ms and window.inner.serde.class in
StreamsConfig
[
https://issues.apache.org/jira/browse/KAFKA-16260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-16260:
Summary: Deprecate window.size.ms and inner.serde.class in StreamsConfig
(was: Deprecate
[
https://issues.apache.org/jira/browse/KAFKA-16260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-16260:
Description:
{{window.size.ms}} is not a true KafkaStreams config, and results
[
https://issues.apache.org/jira/browse/KAFKA-16260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-16260:
Labels: KIP (was: needs-kip)
> Deprecate window.size.ms in StreamsCon
Any updates on this KIP?
On 3/28/24 4:11 AM, Matthias J. Sax wrote:
It seems that `MockRecordMetadata` is a private class, and thus not part
of the public API. If there are any changes required, we don't need to
discuss on the KIP.
For `CapturedPunctuator` and `CapturedForward` it's
oes process one sided joins after the
skipped record. Do you have any docs on the "dropper records" metric? I did
a Google search and didn't find many good results for that.
Thanks,
Chad
On Tue, Apr 30, 2024 at 2:49 PM Matthias J. Sax wrote:
Thanks for the information. I ran the cod
[
https://issues.apache.org/jira/browse/KAFKA-16514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842805#comment-17842805
]
Matthias J. Sax commented on KAFKA-16514:
-
Thanks for the background! Makes sense.
> Ka
[
https://issues.apache.org/jira/browse/KAFKA-16644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax resolved KAFKA-16644.
-
Resolution: Duplicate
> FK join emits duplicate tombstone on left-side del
[
https://issues.apache.org/jira/browse/KAFKA-16644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax resolved KAFKA-16644.
-
Resolution: Duplicate
> FK join emits duplicate tombstone on left-side del
Thanks for the update.
I am wondering if we should use `ReadOnlyHeaders` instead of
`ImmutableHeaders` as interface name?
Also, the returned `Header` interface is technically not immutable
either, because `Header#key()` returns a mutable byte-array... Would we
need a `ReadOnlyHeader`
that we should try to support downgrades without wipes. At least
Nick should state in the KIP why we do not support it.
Best,
Bruno
On 4/23/24 8:13 AM, Matthias J. Sax wrote:
Thanks for splitting out this KIP. The discussion shows, that it is a
complex beast by itself, so worth to discuss by
I like the idea of error codes. Not sure if the name are ideal?
UNKNOWN_PROCESS_ID makes sense, but the other two seems a little bit
difficult to understand?
Should we be very descriptive (and also try to avoid coupling it to the
threading model -- important for the first error code):
-
[
https://issues.apache.org/jira/browse/KAFKA-16644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842514#comment-17842514
]
Matthias J. Sax commented on KAFKA-16644:
-
Sorry. Wrong link. Fixed -> https://issues.apache.
[
https://issues.apache.org/jira/browse/KAFKA-16644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-16644:
Description:
We introduced a regression bug in 3.7.0 release via KAFKA-14748. When
101 - 200 of 11284 matches
Mail list logo