[
https://issues.apache.org/jira/browse/KAFKA-14415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-14415:
Component/s: streams
> ThreadCache is getting slower with every additional state st
Thanks for the KIP.
Couple of clarification questions (I am not a broker expert do maybe
some question are obvious for others, but not for me with my lack of
broker knowledge).
(10)
The delayed message case can also violate EOS if the delayed message comes in
after the next
Thanks for the KIP Victoria. Very well written!
Couple of questions (many might just require to add some more details to
the KIP):
(1) Why does the new store not extend KeyValueStore, but StateStore?
In the end, it's a KeyValueStore?
(2) Should we have a ReadOnlyVersionedKeyValueStore?
[
https://issues.apache.org/jira/browse/KAFKA-14400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17636907#comment-17636907
]
Matthias J. Sax edited comment on KAFKA-14400 at 11/21/22 10:40 PM
[
https://issues.apache.org/jira/browse/KAFKA-14400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17636907#comment-17636907
]
Matthias J. Sax edited comment on KAFKA-14400 at 11/21/22 10:40 PM
[
https://issues.apache.org/jira/browse/KAFKA-14400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17636907#comment-17636907
]
Matthias J. Sax commented on KAFKA-14400:
-
The old and new API have different semantics. The old
+1 (binding)
On 11/21/22 7:39 AM, John Roesler wrote:
I'm +1 (binding)
Thanks for the KIP!
-John
On 2022/11/17 21:06:29 Hao Li wrote:
Hi all,
I would like start a vote on KIP-884:
[
https://issues.apache.org/jira/browse/KAFKA-14184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17635680#comment-17635680
]
Matthias J. Sax commented on KAFKA-14184:
-
The stack trace is highly suspicious. Based
[
https://issues.apache.org/jira/browse/KAFKA-14374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17635667#comment-17635667
]
Matthias J. Sax commented on KAFKA-14374:
-
Thanks for creating a ticket. I am not sure right now
it the
`DefaultKafkaClientSupplier`
Thanks,
Hao
On Tue, Nov 15, 2022 at 4:11 PM Matthias J. Sax wrote:
Thanks for the KIP Hao.
What is the behavior if users set the config and also pass in a client
supplier into the constructor?
Following other config/API patterns we use, it seems the best thing
Thanks for the KIP Hao.
What is the behavior if users set the config and also pass in a client
supplier into the constructor?
Following other config/API patterns we use, it seems the best thing
would be if the code would overwrite the config?
If we do this, should we change the config name
[
https://issues.apache.org/jira/browse/KAFKA-14360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax resolved KAFKA-14360.
-
Resolution: Fixed
> Documentation: Streams Security page has broken li
[
https://issues.apache.org/jira/browse/KAFKA-14360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax resolved KAFKA-14360.
-
Resolution: Fixed
> Documentation: Streams Security page has broken li
don't think that there is any guarantee that you might "see"
concurrent modification (IIRC, RocksDB uses snapshot isolation for
iterators). But maybe that's good enough for you?
-Matthias
On 11/7/22 11:13 AM, Joshua Suskalo wrote:
"Matthias J. Sax" writes:
In ge
Thanks for the KIP Sophie. Seems there is a lively discussion going on.
I tried to read up on the history and I hope I don't repeat what was
already discussed.
And sorry for the quite long email...
(1) Stateless vs Stateful
I agree that stateless apps should be supported, even if I am not
[
https://issues.apache.org/jira/browse/KAFKA-14294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17630098#comment-17630098
]
Matthias J. Sax commented on KAFKA-14294:
-
Why do you think we don't commit? Based on the code
used iterator is
concurrent, there is no API contract about it.
-Matthias
On 11/7/22 7:41 AM, Joshua Suskalo wrote:
Hello Matthias, thanks for the response!
"Matthias J. Sax" writes:
Spanning your own thread and calling context.forward() is _not_ safe, and there
is currently no w
Your observation is correct. The Processor#process() and punctuation
callback are executed on a single thread. It's by design to avoid the
issue of concurrency (writing thread safe code is hard and we want to
avoid putting this burden onto the user). There is currently no plans to
make
[
https://issues.apache.org/jira/browse/KAFKA-13813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17629223#comment-17629223
]
Matthias J. Sax commented on KAFKA-13813:
-
Sorry for late reply – I was on leave.
{quote
Congrats!
On 11/1/22 7:08 PM, Luke Chen wrote:
Congrats Bruno!
Well deserved!
Luke
On Wed, Nov 2, 2022 at 10:07 AM John Roesler wrote:
Congratulations, Bruno!!!
On Tue, Nov 1, 2022, at 15:16, Lucas Brutschy wrote:
Wow, congratulations!
On Tue, Nov 1, 2022 at 8:55 PM Chris Egerton
Congrats!
On 11/1/22 7:08 PM, Luke Chen wrote:
Congrats Bruno!
Well deserved!
Luke
On Wed, Nov 2, 2022 at 10:07 AM John Roesler wrote:
Congratulations, Bruno!!!
On Tue, Nov 1, 2022, at 15:16, Lucas Brutschy wrote:
Wow, congratulations!
On Tue, Nov 1, 2022 at 8:55 PM Chris Egerton
[
https://issues.apache.org/jira/browse/KAFKA-14090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-14090:
Component/s: streams
(was: clients)
> Allow Kafka Stre
Congrats! Well deserved!
-Matthias
On 7/25/22 1:08 PM, Bill Bejeck wrote:
Congrats Chris!
-Bill
On Mon, Jul 25, 2022 at 3:58 PM Jorge Esteban Quilcate Otoya <
quilcate.jo...@gmail.com> wrote:
Congratulations Chris!
On Mon, 25 Jul 2022 at 20:27, Robin Moffatt
wrote:
Congrats Chris!
--
[
https://issues.apache.org/jira/browse/KAFKA-14076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-14076:
Affects Version/s: 3.3.0
> Fix issues with KafkaStreams.CloseOpti
[
https://issues.apache.org/jira/browse/KAFKA-13217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-13217:
Labels: kip newbie newbie++ (was: needs-kip newbie newbie++)
> Reconsider skipp
[
https://issues.apache.org/jira/browse/KAFKA-13217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-13217:
Description:
In Kafka Streams, when an instance is shut down via the close() API, we
[
https://issues.apache.org/jira/browse/KAFKA-13217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17569283#comment-17569283
]
Matthias J. Sax commented on KAFKA-13217:
-
Just reviewed the PR and linked the tickets. PR LGTM
[
https://issues.apache.org/jira/browse/KAFKA-14076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17569282#comment-17569282
]
Matthias J. Sax commented on KAFKA-14076:
-
Marking this as blocker for 3.3, because this fixes
[
https://issues.apache.org/jira/browse/KAFKA-14076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-14076:
Priority: Blocker (was: Major)
> Fix issues with KafkaStreams.CloseOpti
[
https://issues.apache.org/jira/browse/KAFKA-14076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-14076:
Fix Version/s: 3.3.0
> Fix issues with KafkaStreams.CloseOpti
[
https://issues.apache.org/jira/browse/KAFKA-14076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax reassigned KAFKA-14076:
---
Assignee: Jim Hughes
> Fix issues with KafkaStreams.CloseOpti
[
https://issues.apache.org/jira/browse/KAFKA-12887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17568659#comment-17568659
]
Matthias J. Sax commented on KAFKA-12887:
-
This feature broke some stuff, and we revert
[
https://issues.apache.org/jira/browse/KAFKA-13152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-13152:
Labels: kip (was: needs-kip)
> Replace "buffered.records.per.p
[
https://issues.apache.org/jira/browse/KAFKA-13152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax reopened KAFKA-13152:
-
> Replace "buffered.records.per.partition" with "inpu
[
https://issues.apache.org/jira/browse/KAFKA-13152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-13152:
Fix Version/s: (was: 3.3.0)
> Replace "buffered.records.per.p
[
https://issues.apache.org/jira/browse/KAFKA-13152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax reopened KAFKA-13152:
-
> Replace "buffered.records.per.partition" with "inpu
class devoid of any StreamPartitioner. I just
thought it's cleaner to keep it this way as StreamPartitioner already
dpes the partitioning. Let me know what you think.
Thanks!
Sagar.
On Wed, Jun 29, 2022 at 5:34 AM Matthias J. Sax wrote:
Thanks for the KIP. Overall a good addition.
I am actually
Thanks for the KIP.
I read it and I am also worried by the complexity of the new
configurations. They are not easy to grasp. I need to digest it a bit more,
I think.
Best,
David
Le mer. 29 juin 2022 à 02:25, Matthias J. Sax a écrit :
Thanks for the KIP.
I don't think I fully digested the proposa
[
https://issues.apache.org/jira/browse/KAFKA-14049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17563510#comment-17563510
]
Matthias J. Sax commented on KAFKA-14049:
-
{quote}Null Values in the Stream for a Left Join
[ https://issues.apache.org/jira/browse/KAFKA-14049 ]
Matthias J. Sax deleted comment on KAFKA-14049:
-
was (Author: mjsax):
Sounds like a duplicate to https://issues.apache.org/jira/browse/KAFKA-12317 ?
> Relax Non Null Requirem
[
https://issues.apache.org/jira/browse/KAFKA-14049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17563509#comment-17563509
]
Matthias J. Sax commented on KAFKA-14049:
-
Sounds like a duplicate to https://issues.apache.org
[
https://issues.apache.org/jira/browse/KAFKA-13936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-13936:
Fix Version/s: 3.3.0
> Invalid consumer lag when monitoring from a kafka stre
[
https://issues.apache.org/jira/browse/KAFKA-13936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax reassigned KAFKA-13936:
---
Assignee: Prashanth Joseph Babu
> Invalid consumer lag when monitoring f
[
https://issues.apache.org/jira/browse/KAFKA-13936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax resolved KAFKA-13936.
-
Resolution: Fixed
> Invalid consumer lag when monitoring from a kafka stre
[
https://issues.apache.org/jira/browse/KAFKA-13936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax resolved KAFKA-13936.
-
Resolution: Fixed
> Invalid consumer lag when monitoring from a kafka stre
On Thu, Mar 24, 2022 at 5:13 PM Matthias J. Sax wrote:
+1 (binding)
On 3/24/22 1:52 PM, Hao Li wrote:
I hit reply on my phone in the mail app and changed the title and text
hoping it will start a new thread. Apparently it doesn't work...
On Thu, Mar 24, 2022 at 12:36 PM Bruno Cadonna
wro
[
https://issues.apache.org/jira/browse/KAFKA-10493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17560622#comment-17560622
]
Matthias J. Sax commented on KAFKA-10493:
-
There is nothing official yet, but we started to work
Thanks for the KIP.
I don't think I fully digested the proposal yet, but my first reaction
is: this is quite complicated. Frankly, I am worried about complexity
and usability.
Especially the option `safe_latest` is a "weird" one IMHO, and `nearest`
is even more complex.
The problem at
Thanks for the KIP. Overall a good addition.
I am actually not sure if we need to add a new class? From my
understanding, if there is exactly one abstract method, the interface is
still functional? Thus, we could add a new method to
`StreamsPartitioner` with a default implementation (that
[
https://issues.apache.org/jira/browse/KAFKA-13531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17555781#comment-17555781
]
Matthias J. Sax commented on KAFKA-13531:
-
Could be. We usually also report if we say more
[
https://issues.apache.org/jira/browse/KAFKA-13531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax resolved KAFKA-13531.
-
Resolution: Cannot Reproduce
> Flaky test NamedTopologyIntegrationT
[
https://issues.apache.org/jira/browse/KAFKA-13531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax resolved KAFKA-13531.
-
Resolution: Cannot Reproduce
> Flaky test NamedTopologyIntegrationT
[
https://issues.apache.org/jira/browse/KAFKA-13939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17554742#comment-17554742
]
Matthias J. Sax commented on KAFKA-13939:
-
Thanks for the PR. I added you to list
[
https://issues.apache.org/jira/browse/KAFKA-13939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax reassigned KAFKA-13939:
---
Assignee: Jackson Newhouse
> Memory Leak When Logging Is Disab
es include a message being written to topic
A, could messages from batch with sn X+1 end up being persisted with an
offset lesser than the ones from the batch with sn X?
Does this question make sense?
El mar, 7 jun 2022 a las 16:13, Matthias J. Sax ()
escribió:
Yes, the broker de-dupes using
[
https://issues.apache.org/jira/browse/SUREFIRE-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17554376#comment-17554376
]
Matthias J. Sax commented on SUREFIRE-2076:
---
Thanks for the update! – I opened a PR for our
[
https://issues.apache.org/jira/browse/KAFKA-13963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17551333#comment-17551333
]
Matthias J. Sax commented on KAFKA-13963:
-
{quote}Is it worth updating the java doc to mention
[
https://issues.apache.org/jira/browse/KAFKA-13963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17551271#comment-17551271
]
Matthias J. Sax commented on KAFKA-13963:
-
TopologyDescription only describes the structure
Yes, the broker de-dupes using the sequence number.
But for example, if a sequence number is skipped, you could get this
exception: the current batch of messages cannot be appended to the log,
as one batch is missing, and the producer would need to re-send the
previous/missing batch with
`enable.auto.commit` is a Consumer config and does not apply to Kafka
Stream.
In Kafka Streams, you basically always have auto commit enabled, and you
can control how frequently commits happen via `commit.interval.ms`.
Also on `close()` Kafka Streams would commit offsets.
-Matthias
On
[
https://issues.apache.org/jira/browse/KAFKA-13936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17546407#comment-17546407
]
Matthias J. Sax commented on KAFKA-13936:
-
The docs are in the same repository as the code
[
https://issues.apache.org/jira/browse/KAFKA-13936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17545686#comment-17545686
]
Matthias J. Sax commented on KAFKA-13936:
-
Might be worth to document for this case :) – Would
[
https://issues.apache.org/jira/browse/KAFKA-13945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-13945:
Description: KIP-846:
[https://cwiki.apache.org/confluence/pages/viewpage.action?pageId
[
https://issues.apache.org/jira/browse/KAFKA-13936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17544647#comment-17544647
]
Matthias J. Sax commented on KAFKA-13936:
-
As mentioned above, offsets are by default committed
[
https://issues.apache.org/jira/browse/KAFKA-13939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17544645#comment-17544645
]
Matthias J. Sax commented on KAFKA-13939:
-
Thanks for reporting this issue – sound rather severs
[
https://issues.apache.org/jira/browse/KAFKA-13939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-13939:
Component/s: streams
> Memory Leak When Logging Is Disab
[
https://issues.apache.org/jira/browse/KAFKA-13939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-13939:
Priority: Blocker (was: Major)
> Memory Leak When Logging Is Disab
[
https://issues.apache.org/jira/browse/KAFKA-13936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17542359#comment-17542359
]
Matthias J. Sax commented on KAFKA-13936:
-
> we see in the kafka UI
There is no "
ane wrote:
@Matthias J. Sax / All
Have added below line :
.suppress(Suppressed.untilWindowCloses(Suppressed.BufferConfig.unbounded()))
Here is the output : (for uuid (*2cbef750-325b-4a2f-ac39-b2c23fa0313f)*,
expecting single output but that is not the case here. Which 1 is the final
output from tho
Added. Feel free to update wiki pages with smaller details like this
directly.
-Matthias
On 5/19/22 2:27 PM, James Cheng wrote:
Thanks Guozhang! Based on your comment, I searched through the repo and found
the associated pull requests and JIRAs.
It looks like most of the support was added
[
https://issues.apache.org/jira/browse/KAFKA-13817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17540294#comment-17540294
]
Matthias J. Sax commented on KAFKA-13817:
-
Thanks for the PR! I put it into my review backlog
[
https://issues.apache.org/jira/browse/KAFKA-13913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17539718#comment-17539718
]
Matthias J. Sax commented on KAFKA-13913:
-
There was some discussion about this in the past (cf
[
https://issues.apache.org/jira/browse/KAFKA-13913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-13913:
Labels: kip (was: )
> Provide builders for KafkaProducer/KafkaConsumer and KafkaStre
[
https://issues.apache.org/jira/browse/KAFKA-13913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-13913:
Component/s: streams
> Provide builders for KafkaProducer/KafkaConsumer and KafkaStre
Emitting intermediate result is by-design.
If you don't want to get intermediate result, you can add `suppress()`
after the aggregation and configure it to only "emit on window close".
-Matthias
On 5/17/22 3:20 AM, Shankar Mane wrote:
Hi All,
Our use case is to use sliding window. (for
[
https://issues.apache.org/jira/browse/KAFKA-6520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17537860#comment-17537860
]
Matthias J. Sax commented on KAFKA-6520:
It's still an open item – and it's complex (for details
[
https://issues.apache.org/jira/browse/KAFKA-13817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17536926#comment-17536926
]
Matthias J. Sax commented on KAFKA-13817:
-
> as it will eventually self-correct and conti
[
https://issues.apache.org/jira/browse/SUREFIRE-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17535072#comment-17535072
]
Matthias J. Sax commented on SUREFIRE-2076:
---
[~tibordigana] [~zoltan.meze] – Did you see my
[
https://issues.apache.org/jira/browse/KAFKA-7527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax resolved KAFKA-7527.
Resolution: Fixed
> Enable Dependency Injection for Kafka Streams handlers (KIP-
[
https://issues.apache.org/jira/browse/KAFKA-7527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax resolved KAFKA-7527.
Resolution: Fixed
> Enable Dependency Injection for Kafka Streams handlers (KIP-
I had one minor question on the discuss thread. It's mainly about
clarifying and document the user contract. I am fine either way.
+1 (binding)
-Matthias
On 5/10/22 12:32 PM, Sophie Blee-Goldman wrote:
Thanks for the KIP! +1 (binding)
On Tue, May 10, 2022, 12:24 PM Bruno Cadonna wrote:
d point about getting the paused state to new members; it
is
seeming
like the "building block" approach is a good one to keep
things
simple
at
first.
Cheers,
Jim
On Fri, May 6, 2022 at 8:31 PM Matthias J. Sax <
mj...@apache.org
wrote:
I think it's tricky to propagate a pa
I think it's tricky to propagate a pauseAll() via the rebalance
protocol. New members joining the group would need to get paused, too?
Could there be weird race conditions with overlapping pauseAll() and
resumeAll() calls on different instanced while there could be a errors /
network
[
https://issues.apache.org/jira/browse/KAFKA-8769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17532427#comment-17532427
]
Matthias J. Sax commented on KAFKA-8769:
Just a "random" comment, based on some other
[
https://issues.apache.org/jira/browse/KAFKA-13873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-13873:
Description:
In order to reduce resources used or modify data pipelines, users may want
[
https://issues.apache.org/jira/browse/KAFKA-13873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-13873:
Component/s: streams
> Add ability to Pause / Resume KafkaStreams Topolog
[
https://issues.apache.org/jira/browse/KAFKA-13873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-13873:
Labels: kip (was: )
> Add ability to Pause / Resume KafkaStreams Topolog
[
https://issues.apache.org/jira/browse/KAFKA-13870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-13870:
Labels: needs-kip (was: )
> support both Suppressed untilTimeLimit and maxBytes with
[
https://issues.apache.org/jira/browse/KAFKA-13870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531836#comment-17531836
]
Matthias J. Sax commented on KAFKA-13870:
-
I think you mix up two concepts: windowing is about
[
https://issues.apache.org/jira/browse/KAFKA-13813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-13813:
Summary: left/outer joins can wait indefinitely for emitted record with
spurious record
Matthias J. Sax created KAFKA-13866:
---
Summary: Support more advanced time retention policies
Key: KAFKA-13866
URL: https://issues.apache.org/jira/browse/KAFKA-13866
Project: Kafka
Issue
Matthias J. Sax created KAFKA-13866:
---
Summary: Support more advanced time retention policies
Key: KAFKA-13866
URL: https://issues.apache.org/jira/browse/KAFKA-13866
Project: Kafka
Issue
[
https://issues.apache.org/jira/browse/SUREFIRE-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17529670#comment-17529670
]
Matthias J. Sax commented on SUREFIRE-2076:
---
Seems we are hitting this issue trying
.
Levani
On 23. Apr 2022, at 02:43, Matthias J. Sax wrote:
Ivan,
are you still interested in this KIP? I think it would be a good addition.
-Matthias
On 8/16/21 5:30 PM, Matthias J. Sax wrote:
Your point about the IQ problem is an interesting one. I missed the
point that the "new key&q
[
https://issues.apache.org/jira/browse/KAFKA-13647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17528288#comment-17528288
]
Matthias J. Sax commented on KAFKA-13647:
-
Should we close this ticket? \cc [~guozhang
Ivan,
are you still interested in this KIP? I think it would be a good addition.
-Matthias
On 8/16/21 5:30 PM, Matthias J. Sax wrote:
Your point about the IQ problem is an interesting one. I missed the
point that the "new key" would be a "superkey", and thus, it shoul
/javase/8/docs/api/java/util/Collection.html#toArray-T:A-
Cheers,
Chris
On Tue, Mar 29, 2022 at 11:14 PM Matthias J. Sax wrote:
My understand was, that the original proposal was to have:
merge(KStream stream);
merge(KStream... streams);
Maybe I misunderstood.
I am not really a fan
[
https://issues.apache.org/jira/browse/KAFKA-12909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17522502#comment-17522502
]
Matthias J. Sax edited comment on KAFKA-12909 at 4/21/22 9:13 PM
[
https://issues.apache.org/jira/browse/KAFKA-12909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17526086#comment-17526086
]
Matthias J. Sax commented on KAFKA-12909:
-
Ah sorry. That was my bad... Fixed.
> Allow us
[
https://issues.apache.org/jira/browse/KAFKA-13842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-13842:
Description:
Kafka Streams follows a continuous refinement model for aggregation
1101 - 1200 of 11152 matches
Mail list logo
