Hi there! To subscribe to the list, you have to email a different address:
users-subscr...@kafka.apache.org. (see https://kafka.apache.org/contact.html).
This also applies to the message you sent to dev (should have been
dev-subscr...@kafka.apache.org).
Thanks for joining the conversation!
-Joh
Hi all,
The KIP is accepted and implemented already, but is blocked on code
review: https://github.com/apache/kafka/pull/7170
A quick note on the lack of recent progress... It's completely our fault,
the reviews fell by the wayside during the 2.5.0 release cycle, and we
haven't gotten back to it.
ose this gap. But we
> > would need to do a KIP to introduce some API to allow user to tell
> > Kafka Streams that repartitioning is not necessary.
> >
> > In Apache Flink, there is an operator called
> > `reinterpretAsKeyedStream`. We could introduce something similar.
Hi Navneeth,
This sounds like an unusual use case. Can you provide more information on why
this is required?
Thanks,
John
On Mon, Mar 9, 2020, at 12:48, Navneeth Krishnan wrote:
> Hi All,
>
> Any suggestions?
>
> Thanks
>
> On Sat, Mar 7, 2020 at 10:13 AM Navneeth Krishnan
> wrote:
>
> > H
KV stores each. Since the code is fairly large per function, I have
> > them split into classes by functionalities. and some method in the call
> > stack would need to access this state. What do you recommend in such
> > scenarios?
> >
> > Thanks
> >
> > On Mon, M
Hi Alex,
It sounds like your theory is plausible. After a rebalance, Streams needs to
restore its stores from the changelog topics. Currently, Streams performs this
restore operation in the same loop that does processing and polls the consumer
for more records. If the restore batches (or the pr
what I’m wondering is, could the
> OVERALL length of time needed to fully restore the state stores (which
> could be multiple topics with multiple partitions) be exceeding some
> timeout or threshold? Thanks again for any ideas,
>
>
>
> Alex C
>
>
> On Thu, Ap
Boom, you got it, Liam! Nice debugging work.
This is a pretty big bummer, but I had to do it that way for compatibility. I
added a log message to try and help reduce the risk, but it’s still kind of a
trap.
I’d like to do a KIP at some point to consider changing the default grace
period, but
Hi Sachin,
Just to build on Boyang’s answer a little, when designing Kafka’s partition
expansion operation, we did consider making it work also for dynamically
repartitioning in a way that would work for Streams as well, but it added too
much complexity, and the contributor had some other use c
ion the kafka completely re-distributes all
> the older messages too among all the partitions.
> And if it does that then does it ensure that in this re-distributions it
> keeps messages of same key in same partition.
>
> Thanks
> Sachin
>
>
>
>
> On Wed, Apr 15, 2020 at
Hi Liam,
I took a quick look. On the output side, it looks like you’re adding the count
to the prior count. Should that just set the outbound vale to the new count?
Maybe I misunderstood the situation.
What I mean is, suppose you get two events for the same window:
Inbound map := 0+1 = 1
Coun
gt;
> Liam Clarke-Hutchinson
>
> On Thu, Apr 16, 2020 at 1:59 AM John Roesler wrote:
>
> > Boom, you got it, Liam! Nice debugging work.
> >
> > This is a pretty big bummer, but I had to do it that way for
> > compatibility. I added a log message to try and hel
e. To prepare for this change, we could start to log a WARN
> > message, if a user does not set the grace period explicitly for now.
> >
> > Just my 2 ct. Thoughts?
> >
> > -Matthias
> >
> > On 4/19/20 7:40 AM, John Roesler wrote:
> > > Oh, man,
t; I'm deploying a fixed
> version of it as we speak. Thanks for the reply though :)
>
> Kind regards,
>
> Liam Clarke
>
>
>
> On Mon, 20 Apr. 2020, 2:08 am John Roesler, wrote:
>
> > Hi Liam,
> >
> > I took a quick look. On the output side, it
wrote:
> > PR submitted :) https://github.com/apache/kafka/pull/8520
> >
> > On Mon, Apr 20, 2020 at 2:34 PM John Roesler wrote:
> >
> >> Hi Liam,
> >>
> >> That sounds like a good idea to me. In fact, I’d go so far as to say we
> >> sh
Hi Carl,
That sounds pretty frustrating; sorry about that.
I think I got a hint, but I'm not totally clear on the situation. It shouldn't
be possible for data to get into the store if it can't be handled by the serde.
There is a specific issue with global stores, but it doesn't sound like that's
Hi Pushkar,
I’ve been wondering if we should add writable tables to the Streams api. Can
you explain more about your use case and how it would integrate with your
application?
Incidentally, this would also help us provide more concrete advice.
Thanks!
John
On Fri, May 1, 2020, at 15:28, Matt
different instance and it tried to read from store cache then it doesn't
> > get the data, so the event passed on without enriched data.
> > That's pretty much about the use case.
> >
> >
> > On Sun, May 3, 2020 at 9:42 PM John Roesler wrote:
> >
>
y
> carefully.
>
> Thanks again!
>
> On Mon, May 4, 2020 at 11:18 PM Pushkar Deole wrote:
>
> > Thanks John... what parameters would affect the latency in case
> > GlobalKTable will be used and is there any configurations that could be
> > tuned to minimize th
Hi Pushkar,
If you’re not too concerned about compactness, I think Jackson json
serialization is the easiest way to serialize complex types.
There’s also a kip in progress to add a list serde. You might take a look at
that proposal for ideas to write your own.
Thanks,
John
On Thu, May 7, 20
way, what is the byteArrayserializer? As the name suggests, it is
> for byte arrays so won't work for java ArrayList, right?
>
> On Thu, May 7, 2020 at 8:44 PM John Roesler wrote:
>
> > Hi Pushkar,
> >
> > If you’re not too concerned about compactness, I think Ja
data in memory or it gets it from the backed topic everytime?
> Secondly, what kind of internal data structure does it use? Is it good for
> constant time performance?
>
> On Thu, May 7, 2020 at 7:27 PM John Roesler wrote:
>
> > Hi Pushkar,
> >
> > To answer your
:47, Pushkar Deole wrote:
> John,
> is there KIP in progress for supporting Java HashMap also?
>
> On Sun, May 10, 2020, 00:47 John Roesler wrote:
>
> > Yes, that’s correct. It’s only for serializing the java type ‘byte[]’.
> >
> > On Thu, May 7, 2020, at 10:37,
Oh, my mistake. I thought this was a different thread :)
You might want to check, but I don’t think there is a kip for a map serde. Of
course, you’re welcome to start one.
Thanks,
John
On Mon, May 11, 2020, at 09:14, John Roesler wrote:
> Hi Pushkar,
>
> I don’t think there i
Hello Baki,
It looks like option 2 is really what you want. The purpose of the time window
stores is to allow deleting old data when you need to group by a time
dimension, which naturally results in an infinite key space.
If you don’t want to wait for the final result, can you just not add the
Woah, that's a nasty bug. I've just pinged the Jira ticket. Please feel free to
do the same.
Thanks,
-John
On Thu, May 28, 2020, at 02:55, Pushkar Deole wrote:
> Thanks for the help Guozhang!
> however i realized that the exception and actual problem is totally
> different. The problem was the cl
Hello,
Thanks for the question. It looks like the ticket is still open,
so I think it's safe to say it's not fixed.
If you're affected by the issue, it would be helpful to leave
a comment on the ticket to that effect.
Thanks,
-John
On Fri, May 29, 2020, at 00:05, Debraj Manna wrote:
> Anyone an
That’s great news! Congratulations, Boyang. It’s well deserved.
-John
On Mon, Jun 22, 2020, at 18:26, Guozhang Wang wrote:
> The PMC for Apache Kafka has invited Boyang Chen as a committer and we are
> pleased to announce that he has accepted!
>
> Boyang has been active in the Kafka community mor
Hello Nag,
Yes, your conclusion sounds right.
“Sum the values per key” is a statement that doesn’t really make sense in a
KTable context, since there is always just one value per key (the latest
update).
I think the docs are just trying to drive the point home that in a KTable,
there is just
Hello Kafka users, developers and client-developers,
This is the first candidate for release of Apache Kafka 2.5.1.
Apache Kafka 2.5.1 is a bugfix release and fixes 72 issues since the 2.5.0
release. Please see the release notes for more information.
Release notes for the 2.5.1 release:
https:/
Hello again all,
Just a reminder that the 2.5.1 RC0 is available for verification.
Thanks,
John
On Thu, Jul 23, 2020, at 21:39, John Roesler wrote:
> Hello Kafka users, developers and client-developers,
>
> This is the first candidate for release of Apache Kafka 2.5.1.
>
> Apa
Hello all,
This vote passes with four +1 votes (3 binding) and no 0 or -1 votes.
+1 votes
PMC Members (in voting order):
* Ismael Juma
* Manikumar Reddy
* Mickael Maison
Committers (in voting order):
* John Roesler
Community:
* No votes
0 votes
* No votes
-1 votes
* No votes
Vote thread
Hi Mathieu,
That sounds frustrating. I’m sorry for the trouble.
>From what you described, it does sound like something wacky is going on with
>the partitioning. In particular, the fact that both joins work when you set
>everything to 1 partition.
You mentioned that you’re using the default pa
Bummer.
> (aaand I spent entire days on it)
>
> Problem solved
> Thanks
>
> Mathieu
>
> Le mar. 11 août 2020 à 07:18, John Roesler a écrit :
>
> > Hi Mathieu,
> >
> > That sounds frustrating. I’m sorry for the trouble.
> >
> > From wha
“Andy” Fang, Dima Reznik, Ego,
Evelyn Bayes, Ewen Cheslack-Postava, Greg Harris, Guozhang
Wang, Ismael Juma, Jason Gustafson, Jeff Widman, Jeremy
Custenborder, jiameixie, John Roesler, Jorge Esteban
Quilcate Otoya, Konstantine Karantasis, Lucent-Wong, Mario
Molina, Matthias J. Sax, Navinder Pal
Hello Ahmed,
Thanks for this feedback. I can see what you mean.
I know that there is a redesign currently in progress for
the site, but I'm not sure if the API/Config documentation
is planned as part of that effort. Here's the PR to re-
design the home page:
https://github.com/apache/kafka-site/
Hello Sanjay,
I've just added you to the contributor list in Jira, so you
should be able to assign tickets now.
Thanks for your interest in the project!
-John
On Sun, 2020-08-16 at 21:27 -0500, Sanjay Y R wrote:
> Hello,
>
> I am Sanjay. I am a Kafka user intending to contribute to Kafka Open
Hi Steve,
Which version of Streams is this? I vaguely recall that we updated to a version
of Rocks that’s compiled for ARM, and I think some people have used it on ARM,
but I might be misremembering.
I’m afraid I can’t be much help in debugging this, but maybe some others on the
list have mor
rms to rocksdb and we updated the dependency
> > to
> > get this fix in 2.6. See KAFKA-9225
> > <https://issues.apache.org/jira/browse/KAFKA-9225>
> >
> > If you already were running 2.6, then, that's unfortunate. You might have
> > some luck
> > asking t
Hi Deepak,
It sounds like you're saying that the exception handler is
correctly indicating that Streams should "Continue", and
that if you stop the app after handling an exceptional
record but before the next commit, Streams re-processes the
record?
If that's what you're seeing, then it's how the
Hi Pushkar,
I'd recommend always keeping Streams and the Clients at the
same version, since we build, test, and release them
together. FWIW, I think there were some bugfixes for the
clients in 2.5.1 anyway.
Thanks,
-John
On Mon, 2020-09-14 at 20:08 +0530, Pushkar Deole wrote:
> Sophie, one more
Hi Pushkar,
Sorry for the trouble. Can you share your config and
topology description?
If I read your error message correctly, it says that your
app is configured with no source topics and no threads. Is
that accurate?
Thanks,
-John
On Mon, 2020-10-05 at 15:04 +0530, Pushkar Deole wrote:
> Hi A
Hi Uirco,
The method that doesn’t take Consumed will fall back to the configured “default
serdes”. If you don’t have that confit set, it will just keep them as byte
arrays, which will probably give you an exception at runtime. You’ll probably
want to use the Consumed argument to set your serdes
Hi Eric,
Ah, that’s a bummer. The correct serde is the session windowed serde, as I can
see you know. I’m afraid I’m a bit rusty on implicit resolution rules, so I
can’t be much help there.
But my general recommendation for implicits is that when things get weird, just
don’t use them at all.
se. If yes, can you please
> show me how?
>
> def to(topic: String)(implicit produced: Produced[K, V]): Unit =
> inner.to(topic, produced)
>
>
> Also not sure how to use a self documenting format like JSON. Any
> examples to share?
>
>
> On Wed, Nov 18, 2020
))
> .count()
> .toStream
> .to("streams-pipe-output")
>
> builder.build()
> }
> }
>
>
>
>
> On Thu, Nov 19, 2020 at 7:24 AM John Roesler wrote:
>
> > Hi Eric,
> >
> > Sure thing. Assuming the
Hi Mathieu,
Ah, that is unfortunate. I believe your analysis is correct. In general, we
have no good solution to the problem of upstream tasks moving ahead of each
other and causing disorder in the repartition topics. Guozhang has done a
substantial amount of thinking on this subject, though, a
Hello Jeffrey,
I’m sorry for the trouble. I appreciate your diligence in tracking this down.
In reading your description, nothing jumps out to me as problematic. I’m a bit
at a loss as to what may have been the problem.
>- Is there a realistic scenario (e.g. crash, rebalance) which you ca
Thanks for this release, Bill,
I ran though the quickstart (just the zk, broker, and
console clients part), verified the signatures, and also
built and ran the tests.
I'm +1 (binding).
Thanks,
-John
On Mon, 2020-12-14 at 14:58 -0800, Guozhang Wang wrote:
> I checked the docs and ran unit tests,
Hi Antoine,
Thanks for your message!
I couldn't see the logo; I think the mailing list software
doesn't transmit attachments.
Perhaps you could just send a pull request to add La Redoute
to
https://github.com/apache/kafka-site/edit/asf-site/powered-by.html
?
Feel free to reply here if you have
Hi Navneeth,
I'm sorry for the trouble.
Which version of Streams are you using? Also, this doesn't
look like the full stacktrace, since we can't see the NPE
itself. Can you share the whole thing?
Thanks,
-John
On Tue, 2020-12-15 at 00:30 -0800, Navneeth Krishnan wrote:
> Hi All,
>
> I have a
Hi Navneeth,
Yes, you are correct. I think there are some opportunities for improvement
there, but there are also reasons for it to be serialized in the in-memory
store.
Off the top of my head, we need to serialize stored data anyway to send it to
the changelog. Also, even though the store is
Hi Mathieu,
I don’t think there would be any problem. Note that window expiry is computed
against an internal clock called “stream time”, which is the max timestamp yet
observed. This time is advanced per each record when that record is processed.
There is a separate clock for each partition, s
Hi David,
Thank you for the question.
If I can confirm, it looks like the "operations" topic is
the only input to the topology, and the topology reads the
"operations" topic joined with the "account" table and
generates a "movements" stream. It reads (and aggregates)
the "movements" stream to cre
Hello Upesh,
I’m sorry for the trouble. This was my feature, and my oversight. I will update
the docs on Monday.
The quick answer is that there is also a new api.MockProcessorContext, which is
compatible with the new interface. That class also provides
getStateStoreContext to use with the sta
Hi Ross,
Thanks for the feedback!
For some "context," the change you mention was:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-478+-+Strongly+typed+Processor+API
In addition to the spec on that page, there are links to the
discussion and voting mailing list threads.
The primary motivat
Hello Kafka users, developers and client-developers,
This is the first candidate for release of Apache Kafka
2.8.0. This is a major release that includes many new
features, including:
* Early-access release of replacing Zookeeper with a self-
managed quorum
* Add Describe Cluster API
* Support mu
2.8.0 release, but wanted to get RC0 out asap for
testing.
Thank you,
John
On Tue, 2021-03-30 at 16:37 -0500, John Roesler wrote:
> Hello Kafka users, developers and client-developers,
>
> This is the first candidate for release of Apache Kafka
> 2.8.0. This is a major release that
Hi Mazen,
This sounds like a good use case. If you’d like, you can start a KIP to add an
enforceRebalance() method to the admin client interface. Feel free to ask here
for any guidance on the KIP process itself.
Regarding your usage, you will actually have to call poll(). That is the point
at
Hello Kafka users, developers and client-developers,
This is the second candidate for release of Apache Kafka
2.8.0. This is a major release that includes many new
features, including:
* Early-access release of replacing Zookeeper with a self-
managed quorum
* Add Describe Cluster API
* Support m
> On Fri, Apr 9, 2021 at 4:52 PM Bill Bejeck wrote:
>
> > Hi John,
> >
> > Thanks for running the 2.8.0 release!
> >
> > I've started to validate it and noticed the site-docs haven't been
> > installed to https://kafka.apache.org/28/documentation.html
Hello Kafka users, developers and client-developers,
This is the third candidate for release of Apache Kafka
2.8.0.This is a major release that includes many new
features, including:
* Early-access release of replacing Zookeeper with a
self-managed quorum
* Add Describe Cluster API
* Suppor
n, Apr 12, 2021 at 8:47 PM John Roesler
> wrote:
> > Good catch, Israel!
> >
> > I’ll make sure that gets fixed.
> >
> > Thanks,
> > John
> >
> > On Mon, Apr 12, 2021, at 19:30, Israel Ekpo wrote:
> > > I just noticed that with the la
, Ismael Juma, Ivan
Ponomarev, Ivan Yurchenko, jackyoh, James Cheng, James
Yuzawa, Jason Gustafson, Jesse Gorzinski, Jim Galasyn, John
Roesler, Jorge Esteban Quilcate Otoya, José Armando García
Sancio, Julien Chanaud, Julien Jean Paul Sirocchi, Justine
Olshan, Kengo Seki, Kowshik Prakasam, leah, Lee
Yes, thank you, Mickael!
-John
On Mon, 2022-03-14 at 12:19 +0100, Bruno Cadonna wrote:
> Thanks Mickael for driving this release!
>
> Best,
> Bruno
>
> On 14.03.22 11:42, Mickael Maison wrote:
> > The Apache Kafka community is pleased to announce the release for
> > Apache Kafka 3.0.1
> >
> > A
Hi Lorcan,
Thanks for your interest!
The instructions for subscribing are available here:
https://kafka.apache.org/contact
Thanks,
John
On Fri, Apr 15, 2022, at 11:28, Lorcan Cooke wrote:
> Hi,
>
>
> I would like to subscribe to users@kafka.apache.org please.
>
>
> Regards,
>
> —
> Lorcan
Hi Neeraj,
Thanks for all that detail! Your expectation is correct. You should see the
checkpoint files after a _clean_ shutdown, and then you should not see it
bootstrap from the beginning of the changelog on the next startup.
How are you shutting down the application? You'll want to call
Kaf
Congratulations, Chris!!
-John
On Mon, Jul 25, 2022, at 20:22, Luke Chen wrote:
> Congratulations Chris! Well deserved!
>
> Luke
>
> On Tue, Jul 26, 2022 at 5:39 AM Anna McDonald
> wrote:
>
>> Congratulations Chris! Time to Cellobrate!
>>
>> anna
>>
>> On Mon, Jul 25, 2022 at 4:23 PM Martin Gain
Hello,
Yes, this is correct. There is a difference between what we call “stream time”
and regular “wall-clock time”.
All the windowing operations need to be deterministic, otherwise your results
would depend on when you run your program. For that reason, we have “stream
time”, which takes its
Congratulations, Sophie!
-John
On Tue, Aug 2, 2022, at 06:40, Chris Egerton wrote:
> Congrats, Sophie!
>
> On Mon, Aug 1, 2022 at 9:21 PM Luke Chen wrote:
>
>> Congrats Sophie! :)
>>
>> Luke
>>
>> On Tue, Aug 2, 2022 at 7:56 AM Adam Bellemare
>> wrote:
>>
>> > Congratulations Sophie! I’m glad t
Hi Suresh,
Sorry for the trouble!
Are you able to provide the rest of the stack trace?
It shouldn’t be possible to call put() on a store in a standby task, so we need
to see the stack frames that show what is calling it.
Thanks,
John
On Tue, Aug 23, 2022, at 05:08, Suresh Rukmangathan wrote:
Thanks for running this, David!
I've verified the signatures, looked at the docs, and run the quickstart (ZK
and KRaft). I also ran the unit tests, as well as all the tests for Streams
locally.
The docs look a little malformed (the "collapse/expand" button floats over the
text, the collapsed d
Hi Tomasz,
Thanks for asking. This sounds like the situation that we fixed in Apache Kafka
3.0, with KIP-695
(https://cwiki.apache.org/confluence/display/KAFKA/KIP-695%3A+Further+Improve+Kafka+Streams+Timestamp+Synchronization).
Can you try upgrading and let us know if this fixes the problem?
ith positive task.max.idle.ms and it did
> not help.
> When lag is large, the application still consumes data batches without
> interleaving.
>
>
>
> wt., 27 wrz 2022 o 05:51 John Roesler napisał(a):
>
>> Hi Tomasz,
>>
>> Thanks for asking. This soun
eck it out and try adjusting the test setup until you're
able to reproduce the behavior you're seeing? If you can do that, I think we
will get to the bottom of it.
Thanks,
-John
On Fri, Sep 30, 2022, at 09:51, John Roesler wrote:
> Hi Tomasz,
>
> Thanks for trying that out. It’s
Hi José,
I verified the signatures and ran all the unit tests, as well as the Streams
integration tests with:
> ./gradlew -version
>
>
> Gradle 7.4.2
>
>
> Build time: 20
Hello Tomasz,
Thanks for the question!
Streams should always call init() before passing any records to transform(...).
When we talk about "reprocessing", we just mean that some record was processed,
but then there was a failure before its offset was committed, and therefore we
have to process
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 wrote:
>>
>> Congrats!
>>
>> On Tue, Nov 1, 2022, 15:44 Bill Bejeck wrote:
>>
>> > Congrats Bruno! Well deserved.
>> >
>> > -Bill
>> >
>> > On T
Hi Pushkar,
Thanks for the question. I think that what’s happening is that, even though
both branches use the same grouping logic, Streams can’t detect that they are
the same. It just sees two group-bys and therefore introduces two repartitions,
with a separate downstream task for each.
You mi
Hi Alexander,
I’m sorry to hear that. It certainly sounds like a hard one to debug.
To clarify, do you mean that when you observe this problem, the sink node is
not in the topology at all, or that it is in the topology, but does not
function properly?
Also, are you using Spring to construct t
Hi Rakesh,
I'm sorry for your trouble. The mailing list doesn't transmit embedded images,
so we can't see the information you provided. Maybe you can create a Github
Gist or open a Jira ticket at
https://issues.apache.org/jira/projects/KAFKA/issues ?
Thanks,
-John
On Sun, Dec 4, 2022, at 23:5
ored in 'totals'. State maintained on local state store on same pod
>>
>> 3rd event with CLOSED status, with key xyz came in and processed. The
>> state is stored in 'record' state store, it is expected to be stored in
>> state store on same pod.
>&
Hi Pushkar,
In 2.5, Kafka Streams used an assignor that tried to strike a compromise
between stickiness and workload balance, so you would observe some stickiness,
but not all the time.
In 2.6, we introduced the "high availability task assignor" (see KIP-441
https://cwiki-test.apache.org/confl
101 - 183 of 183 matches
Mail list logo