[
https://issues.apache.org/jira/browse/KAFKA-13641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17487750#comment-17487750
]
Matthias J. Sax commented on KAFKA-13641:
-
{quote}Is the plan to have type driven semantics
I am +1 to close stale PRs -- not sure to what extend we want to
automate it, or just leave it up to the committers to do the cleanup
manually. I am happy both ways.
However, I also want to point out, that one reason why we have so many
stale PRs is the committer overload to actually review
[
https://issues.apache.org/jira/browse/KAFKA-13641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17487433#comment-17487433
]
Matthias J. Sax commented on KAFKA-13641:
-
I don't have a good intuition atm what a good way
[
https://issues.apache.org/jira/browse/KAFKA-13641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17486584#comment-17486584
]
Matthias J. Sax commented on KAFKA-13641:
-
The Java API faces the same issue – it's hard from
[
https://issues.apache.org/jira/browse/KAFKA-13641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-13641:
Language: scala needs-kip (was: scala)
> Kafka Streams Scala: Add `Opt
[
https://issues.apache.org/jira/browse/KAFKA-13638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17486177#comment-17486177
]
Matthias J. Sax commented on KAFKA-13638:
-
Seems this does not explain much yet, as 5.18.4 did
[
https://issues.apache.org/jira/browse/KAFKA-13633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17486002#comment-17486002
]
Matthias J. Sax commented on KAFKA-13633:
-
Thanks! Will try to review the KIP soon.
> Merg
[
https://issues.apache.org/jira/browse/KAFKA-13633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-13633:
Labels: kip (was: )
> Merging multiple KStreams in one operat
[
https://issues.apache.org/jira/browse/KAFKA-13638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17486001#comment-17486001
]
Matthias J. Sax commented on KAFKA-13638:
-
We did update the RocksDB version in 3.0.0 release
[
https://issues.apache.org/jira/browse/KAFKA-13152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax reopened KAFKA-13152:
-
The PR broke backward compatibility. Needed to revert the commit. Sorry about
that.
Lets
[
https://issues.apache.org/jira/browse/KAFKA-13152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax reopened KAFKA-13152:
-
The PR broke backward compatibility. Needed to revert the commit. Sorry about
that.
Lets
[
https://issues.apache.org/jira/browse/KAFKA-13633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-13633:
Labels: needs-kip (was: )
> Merging multiple KStreams in one operat
[
https://issues.apache.org/jira/browse/KAFKA-13633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17485067#comment-17485067
]
Matthias J. Sax commented on KAFKA-13633:
-
Seems you close the PR...
Btw: this ticket implies
eSupplier(StoreType storeType, ...)
Let's see what others think about it.
Thank you.
Luke
On Tue, Jan 25, 2022 at 4:01 PM Matthias J. Sax
wrote:
Thanks,
There is already `Stores.persistentSessionStore` and
`Stores.inMemorySessionStore`. From a DSL code POV, I don't see large
benefits to add a ne
with a mismatching number of partitions.
On Sat, 22 Jan 2022 at 03:46, Matthias J. Sax
wrote:
Well, it's unclear what the remote lookup does... As Kafka Streams does
not implement this part, my best guess at the moment is to blame it on a
bug in the remote request implementation.
Are you using some
Done.
On 1/26/22 12:52 PM, Vikas Singh wrote:
Hi,
Sending this mail as per
https://cwiki.apache.org/confluence/display/kafka/kafka+improvement+proposals
to request permission to be able to create KIP and contribute to AK.
confluence wiki id: vikasconfluent
jira id: vikasconfluent
Thanks,
[
https://issues.apache.org/jira/browse/KAFKA-10309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-10309:
Fix Version/s: 2.7.0
> KafkaProducer's sendOffsetsToTransaction should not bl
r it.
Thank you.
Luke
On Tue, Jan 25, 2022 at 2:37 AM Matthias J. Sax wrote:
I don't see the KIP update? Did you hit "save"?
Also, the formatting in your email for the new methods is hard to read.
Not sure atm why we need the API change? Can you elaborate? what does
I found it'd be bet
22 at 2:00 PM Matthias J. Sax wrote:
+1 (binding)
On 1/20/22 10:52 AM, Guozhang Wang wrote:
Thanks Luke! I'm +1 on the KIP.
Guozhang
On Wed, Jan 19, 2022 at 5:58 PM Luke Chen wrote:
Hi devs,
I'd like to start a vote for the KIP-591: Add Kafka Streams config to
set
default state store
-7-6.eu-west-1.compute.internal"}*
This behaviour is not random and is 100% reproducible. I can try to create
a minimal code example that will demonstrate it.
On Fri, 21 Jan 2022 at 18:20, Matthias J. Sax wrote:
but instance A returns
result X for a partition I and instance B returns result Y for t
but instance A returns
result X for a partition I and instance B returns result Y for the same
partition I.
This sound a little off. As you stated, if both instances agree on the
active host, the active host must either be instance A or instance B,
and thus you can query partition I only on
he KIP to make processor-based the preferred
choice, along with the changes to the motivation etc. Only thing to figure
out is that restoring behavior to be sure processors of the readonly
statestore aren't working with stale data.
D.
-----Original Message-
From: Matthias J. Sax
Sent:
+1 (binding)
On 1/20/22 10:52 AM, Guozhang Wang wrote:
Thanks Luke! I'm +1 on the KIP.
Guozhang
On Wed, Jan 19, 2022 at 5:58 PM Luke Chen wrote:
Hi devs,
I'd like to start a vote for the KIP-591: Add Kafka Streams config to set
default state store. The goal is to allow users to set a
Matthias J. Sax created KAFKA-13602:
---
Summary: Allow to broadcast a result record
Key: KAFKA-13602
URL: https://issues.apache.org/jira/browse/KAFKA-13602
Project: Kafka
Issue Type: New
[
https://issues.apache.org/jira/browse/KAFKA-13602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-13602:
Labels: needs-kip newbie++ (was: needs-kip)
> Allow to broadcast a result rec
Matthias J. Sax created KAFKA-13602:
---
Summary: Allow to broadcast a result record
Key: KAFKA-13602
URL: https://issues.apache.org/jira/browse/KAFKA-13602
Project: Kafka
Issue Type: New
Daan,
thanks for the KIP. I personally find the motivation section a little
bit confusing. If I understand the KIP correctly, you want to read a
topic into a state store (ie, materialize it). This is already possible
today.
Of course, today a "second" changelog topic would be created. It
You are all set.
On 1/18/22 11:28 AM, Philip Nee wrote:
Hello,
Would like to gain permission to the AK for contribution.
wikiID: pnee
jiraID: pnee
Thanks,
P
+1 (binding)
On 1/14/22 06:32, John Roesler wrote:
Thanks for the KIP, Nick!
+1 (binding)
-John
On Fri, Jan 14, 2022, at 07:40, Bruno Cadonna wrote:
Hi Nick,
Since the title of the KIP slightly changed after the vote was opened
also the link to the KIP changed as a result. This is should
Thanks for the KIP!
I think it's a good step forward for the DSL and it makes sense to
exclude the PAPI and custom stores for now.
About the config name, it seems to be overly complicated. Guozhang's
argument about "store type" that is used to refer to kv, windowed,
session stores make
Thanks for the KIP. Addresses a long standing gap!
+1 (binding)
On 1/12/22 2:53 AM, Tom Bentley wrote:
Hi Mickael,
Thanks! +1 (binding).
Tom
On Mon, 10 Jan 2022 at 15:31, Chris Egerton
wrote:
Hi Mickael,
Happy new year! +1 non-binding.
Cheers,
Chris
On Wed, Jan 5, 2022 at 3:08 PM
Thanks for the KIP! Very good discussion.
I want to raise one point: I am not a fan of the `min.` prefix of the
config, because all configs like this are _minimums_. We also use
`commit.interval.ms` and not `min.commit.interval.ms` for example. I
would suggest to strip the `min.` prefix.
[
https://issues.apache.org/jira/browse/KAFKA-13549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-13549:
Description:
KIP-811:
[https://cwiki.apache.org/confluence/display/KAFKA/KIP-811%3A+Add
Done.
On 1/12/22 3:05 PM, Yu Kvicii wrote:
Hi,
I’d like to request permissions to contribute to Kafka to propose a KIP
Wiki Id:Kvicii.Yu
Jira Id: Kvicii.Yu
Thx
[
https://issues.apache.org/jira/browse/KAFKA-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17474910#comment-17474910
]
Matthias J. Sax commented on KAFKA-13289:
-
{quote}However it seems the dropping of messages
[
https://issues.apache.org/jira/browse/KAFKA-10173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax reassigned KAFKA-10173:
---
Assignee: John Roesler (was: Matthias J. Sax)
> BufferUnderflowException dur
[
https://issues.apache.org/jira/browse/KAFKA-10173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax reassigned KAFKA-10173:
---
Assignee: Matthias J. Sax (was: John Roesler)
> BufferUnderflowException dur
[
https://issues.apache.org/jira/browse/KAFKA-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17473149#comment-17473149
]
Matthias J. Sax commented on KAFKA-13289:
-
{quote}The app uses a 0ms join window with a 0ms
[
https://issues.apache.org/jira/browse/KAFKA-13476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax resolved KAFKA-13476.
-
Fix Version/s: 3.2.0
Resolution: Fixed
> Streams crashes when non Base64 Off
[
https://issues.apache.org/jira/browse/KAFKA-13476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax resolved KAFKA-13476.
-
Fix Version/s: 3.2.0
Resolution: Fixed
> Streams crashes when non Base64 Off
[
https://issues.apache.org/jira/browse/KAFKA-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17469010#comment-17469010
]
Matthias J. Sax commented on KAFKA-13289:
-
You can reproduce with the code in the github repo
If you observer timestamps based synchronization issues, you might also
consider to switch to 3.0 release, that closes a few more gaps to this end.
Cf
https://cwiki.apache.org/confluence/display/KAFKA/KIP-695%3A+Further+Improve+Kafka+Streams+Timestamp+Synchronization
-Matthias
On 12/29/21
Not 100% sure. From what you describe it should work as expected.
It seems `delete()` does not delete the key from the store (ie, RocksDB)
itself (for unknown reasons)?
Are you closing all your iterators correctly? (More or less a wild guess
at the moment.)
Did you enable caching for the
[
https://issues.apache.org/jira/browse/KAFKA-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468879#comment-17468879
]
Matthias J. Sax commented on KAFKA-13289:
-
{quote}However in the cases mentioned here
you guys know of any article/blog/paper/mail discussion/... that
describes/discusses this?
Niels
On Mon, Dec 20, 2021 at 4:35 PM Matthias J. Sax
wrote:
I think this problem should be tackled inside Kafka, not Flink.
Kafka already has internal control messages to write transaction
markers. Tho
[
https://issues.apache.org/jira/browse/KAFKA-13561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463439#comment-17463439
]
Matthias J. Sax commented on KAFKA-13561:
-
Thanks for the details.
> Consider deprecat
[
https://issues.apache.org/jira/browse/KAFKA-13561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-13561:
Labels: needs-kip (was: )
> Consider deprecating `StreamsBuilder#build(props)` funct
[
https://issues.apache.org/jira/browse/KAFKA-13561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-13561:
Component/s: streams
> Consider deprecating `StreamsBuilder#build(props)` funct
[
https://issues.apache.org/jira/browse/KAFKA-13561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463436#comment-17463436
]
Matthias J. Sax commented on KAFKA-13561:
-
My personal idea was actually to deprecate
[
https://issues.apache.org/jira/browse/KAFKA-13549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-13549:
Labels: kip (was: needs-kip)
> Add "delete interval
[
https://issues.apache.org/jira/browse/KAFKA-13549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax reassigned KAFKA-13549:
---
Assignee: Nicholas Telford
> Add "delete interval
[
https://issues.apache.org/jira/browse/KAFKA-13549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-13549:
Description:
KIP-811:
[https://cwiki.apache.org/confluence/display/KAFKA/KIP-811%3A+Add
I think this problem should be tackled inside Kafka, not Flink.
Kafka already has internal control messages to write transaction
markers. Those could be extended to carry watermark information. It
would be best to generalize those as "user control messages" and
watermarks could just be one
Congrats!
On 12/17/21 15:46, Bill Bejeck wrote:
Congratulations David! Well deserved.
-Bill
On Fri, Dec 17, 2021 at 6:43 PM José Armando García Sancio
wrote:
Congrats David!
On Fri, Dec 17, 2021 at 3:09 PM Gwen Shapira wrote:
Hi everyone,
David Jacot has been an Apache Kafka committer
Congrats!
On 12/17/21 15:46, Bill Bejeck wrote:
Congratulations David! Well deserved.
-Bill
On Fri, Dec 17, 2021 at 6:43 PM José Armando García Sancio
wrote:
Congrats David!
On Fri, Dec 17, 2021 at 3:09 PM Gwen Shapira wrote:
Hi everyone,
David Jacot has been an Apache Kafka committer
[
https://issues.apache.org/jira/browse/KAFKA-13549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17461738#comment-17461738
]
Matthias J. Sax commented on KAFKA-13549:
-
You could also just do the KIP. Should not be too
Matthias J. Sax created KAFKA-13555:
---
Summary: Consider number if input topic partitions for task
assignment
Key: KAFKA-13555
URL: https://issues.apache.org/jira/browse/KAFKA-13555
Project: Kafka
Matthias J. Sax created KAFKA-13555:
---
Summary: Consider number if input topic partitions for task
assignment
Key: KAFKA-13555
URL: https://issues.apache.org/jira/browse/KAFKA-13555
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-13476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17461160#comment-17461160
]
Matthias J. Sax commented on KAFKA-13476:
-
{quote}Tracing data was added to metadata because
Matthias J. Sax created KAFKA-13549:
---
Summary: Add "delete interval" config
Key: KAFKA-13549
URL: https://issues.apache.org/jira/browse/KAFKA-13549
Project: Kafka
Issue Type: I
Matthias J. Sax created KAFKA-13549:
---
Summary: Add "delete interval" config
Key: KAFKA-13549
URL: https://issues.apache.org/jira/browse/KAFKA-13549
Project: Kafka
Issue Type: I
[
https://issues.apache.org/jira/browse/KAFKA-13500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17457487#comment-17457487
]
Matthias J. Sax commented on KAFKA-13500:
-
Right... My bad.
> Consider adding a dedica
[
https://issues.apache.org/jira/browse/KAFKA-8115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17456993#comment-17456993
]
Matthias J. Sax edited comment on KAFKA-8115 at 12/10/21, 9:14 AM:
---
One
[
https://issues.apache.org/jira/browse/KAFKA-8115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17456993#comment-17456993
]
Matthias J. Sax commented on KAFKA-8115:
One more on 3.1.
> Flaky Test CoordinatorT
[
https://issues.apache.org/jira/browse/KAFKA-13530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17456992#comment-17456992
]
Matthias J. Sax commented on KAFKA-13530:
-
Again.
> Flaky test ReplicaManagerT
[
https://issues.apache.org/jira/browse/KAFKA-8115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17456991#comment-17456991
]
Matthias J. Sax commented on KAFKA-8115:
Failed again.
> Flaky Test CoordinatorT
[
https://issues.apache.org/jira/browse/KAFKA-13530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17456990#comment-17456990
]
Matthias J. Sax commented on KAFKA-13530:
-
+1
> Flaky test ReplicaManagerT
[
https://issues.apache.org/jira/browse/KAFKA-12377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17456989#comment-17456989
]
Matthias J. Sax commented on KAFKA-12377:
-
One more.
> Flaky Test SaslAuthenticatorT
Matthias J. Sax created KAFKA-13532:
---
Summary: Flaky test
KafkaStreamsTest.testInitializesAndDestroysMetricsReporters
Key: KAFKA-13532
URL: https://issues.apache.org/jira/browse/KAFKA-13532
Project
Matthias J. Sax created KAFKA-13532:
---
Summary: Flaky test
KafkaStreamsTest.testInitializesAndDestroysMetricsReporters
Key: KAFKA-13532
URL: https://issues.apache.org/jira/browse/KAFKA-13532
Project
[
https://issues.apache.org/jira/browse/KAFKA-12377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17456986#comment-17456986
]
Matthias J. Sax commented on KAFKA-12377:
-
One more on 3.1 branch.
> Flaky T
Matthias J. Sax created KAFKA-13531:
---
Summary: Flaky test NamedTopologyIntegrationTest
Key: KAFKA-13531
URL: https://issues.apache.org/jira/browse/KAFKA-13531
Project: Kafka
Issue Type
Matthias J. Sax created KAFKA-13531:
---
Summary: Flaky test NamedTopologyIntegrationTest
Key: KAFKA-13531
URL: https://issues.apache.org/jira/browse/KAFKA-13531
Project: Kafka
Issue Type
[
https://issues.apache.org/jira/browse/KAFKA-12933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax resolved KAFKA-12933.
-
Resolution: Fixed
> Flaky t
[
https://issues.apache.org/jira/browse/KAFKA-12933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax resolved KAFKA-12933.
-
Resolution: Fixed
> Flaky t
[
https://issues.apache.org/jira/browse/KAFKA-13530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17456981#comment-17456981
]
Matthias J. Sax commented on KAFKA-13530:
-
And again.
> Flaky test ReplicaManagerT
[
https://issues.apache.org/jira/browse/KAFKA-13514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17456982#comment-17456982
]
Matthias J. Sax commented on KAFKA-13514:
-
And one more.
> Flakey test StickyAssignorT
[
https://issues.apache.org/jira/browse/KAFKA-13530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17456978#comment-17456978
]
Matthias J. Sax commented on KAFKA-13530:
-
And one more.
> Flaky test ReplicaManagerT
[
https://issues.apache.org/jira/browse/KAFKA-12377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17456976#comment-17456976
]
Matthias J. Sax commented on KAFKA-12377:
-
And one more.
> Flaky Test SaslAuthenticatorT
[
https://issues.apache.org/jira/browse/KAFKA-12377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17456973#comment-17456973
]
Matthias J. Sax commented on KAFKA-12377:
-
One more.
> Flaky Test SaslAuthenticatorT
[
https://issues.apache.org/jira/browse/KAFKA-13514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17456970#comment-17456970
]
Matthias J. Sax commented on KAFKA-13514:
-
Failed again. [~ableegoldman] Could you help
[
https://issues.apache.org/jira/browse/KAFKA-13530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17456968#comment-17456968
]
Matthias J. Sax commented on KAFKA-13530:
-
Failed a second time.
> Flaky t
[
https://issues.apache.org/jira/browse/KAFKA-12319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17456967#comment-17456967
]
Matthias J. Sax commented on KAFKA-12319:
-
Failed again.
> Flaky t
[
https://issues.apache.org/jira/browse/KAFKA-12377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17456966#comment-17456966
]
Matthias J. Sax commented on KAFKA-12377:
-
Failed again.
> Flaky Test SaslAuthenticatorT
Matthias J. Sax created KAFKA-13530:
---
Summary: Flaky test ReplicaManagerTest
Key: KAFKA-13530
URL: https://issues.apache.org/jira/browse/KAFKA-13530
Project: Kafka
Issue Type: Test
Matthias J. Sax created KAFKA-13530:
---
Summary: Flaky test ReplicaManagerTest
Key: KAFKA-13530
URL: https://issues.apache.org/jira/browse/KAFKA-13530
Project: Kafka
Issue Type: Test
[
https://issues.apache.org/jira/browse/KAFKA-13500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17456955#comment-17456955
]
Matthias J. Sax commented on KAFKA-13500:
-
Not 100% sure: for individual configs, maybe
[
https://issues.apache.org/jira/browse/KAFKA-13500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17456955#comment-17456955
]
Matthias J. Sax edited comment on KAFKA-13500 at 12/10/21, 8:32 AM
Hard to achieve.
I guess a naive approach would be to use a `flatMapTransform()` to
implement a filter that drops all record that are not in the desired
time range.
pause() and resume() are not available in Kafka Streams, but only on the
KafkaConsumer (The Spring docs you cite is also about
Thanks for the KIP.
+1 (binding)
On 12/5/21 7:03 PM, Luke Chen wrote:
Hi Vasiliki,
Thanks for the KIP!
It makes sense to have the range and scan query in IQv2, as in IQv1.
+1 (non-binding)
Thank you.
Luke
On Thu, Dec 2, 2021 at 5:41 AM John Roesler wrote:
Thanks for the KIP, Vicky!
I’m
questions.
Best,
Vicky
On Tue, Dec 7, 2021 at 12:46 AM Matthias J. Sax wrote:
Thanks for the KIP. Overall, make sense.
One question: What is the purpose to `RawRangeQuery`? Seems not very
user friendly.
-Matthias
On 11/30/21 12:48 PM, Vasiliki Papavasileiou wrote:
Thank you John! Yes
[
https://issues.apache.org/jira/browse/KAFKA-13500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17456061#comment-17456061
]
Matthias J. Sax commented on KAFKA-13500:
-
I guess it's related. If the restoration thread
Matthias J. Sax created KAFKA-13514:
---
Summary: Flakey test StickyAssignorTest
Key: KAFKA-13514
URL: https://issues.apache.org/jira/browse/KAFKA-13514
Project: Kafka
Issue Type: Test
Matthias J. Sax created KAFKA-13514:
---
Summary: Flakey test StickyAssignorTest
Key: KAFKA-13514
URL: https://issues.apache.org/jira/browse/KAFKA-13514
Project: Kafka
Issue Type: Test
Matthias J. Sax created KAFKA-13513:
---
Summary: Flaky test AdjustStreamThreadCountTest
Key: KAFKA-13513
URL: https://issues.apache.org/jira/browse/KAFKA-13513
Project: Kafka
Issue Type
Matthias J. Sax created KAFKA-13513:
---
Summary: Flaky test AdjustStreamThreadCountTest
Key: KAFKA-13513
URL: https://issues.apache.org/jira/browse/KAFKA-13513
Project: Kafka
Issue Type
[
https://issues.apache.org/jira/browse/KAFKA-13490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax reassigned KAFKA-13490:
---
Assignee: Colin McCabe (was: Matthias J. Sax)
> Fix some problems with KR
[
https://issues.apache.org/jira/browse/KAFKA-13490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax reassigned KAFKA-13490:
---
Assignee: Matthias J. Sax (was: Colin McCabe)
> Fix some problems with KR
Thanks for the KIP. Overall, make sense.
One question: What is the purpose to `RawRangeQuery`? Seems not very
user friendly.
-Matthias
On 11/30/21 12:48 PM, Vasiliki Papavasileiou wrote:
Thank you John! Yes, that was a typo from copying and I fixed it.
Since there have been no more
I had heard when doing a join, the timestamp of the generated
message is taken from the message triggering the join or the biggest
timestamp of the two.
In older versions it was the timestamp of the record that triggered the
join. Since 2.3, it is the maximum of both (cf
1301 - 1400 of 11152 matches
Mail list logo
