Hello,
Thanks for pinging the community. I've taken a look at your code at
KAFKA-10465 and replied in the ticket.
Guozhang
On Mon, Sep 7, 2020 at 8:46 AM M. Manna wrote:
> Hello,
>
> We do appreciate that release 2.7 is keeping us occupied, but this bug (or
> not) is holding us back from
Hello folks,
The Bay Area Kafka meetup will continue to be hosted online this month,
tomorrow (Sep 2nd) at 5:00pm. This time we will have guest speakers from
Twitter to talk about their journey to adopt Apache Kafka.
*RSVP*:
https://www.meetup.com/KafkaBayArea/events/272643868/
*Date*
5:00pm,
Hi Ming,
Maybe this ticket could be useful to you:
https://issues.apache.org/jira/browse/KAFKA-7504
Guozhang
On Fri, Aug 28, 2020 at 8:21 AM Ming Liu wrote:
> Hi
> One major reason that Kafka is fast is because it is using sendfile()
> for zero copy, as what it described at
>
Thanks for the update Steve! This is very helpful and I find the blog is a
good read too! Appreciate your contribution to the community.
Guozhang
On Thu, Aug 27, 2020 at 11:06 AM Steve Jones wrote:
> Ok so an update here, it's just a learning thing alongside the day job so
> it took a little
al with regard to the Kafka logo.
> > > Would it be possible to change Design B accordingly?
> > >
> > > I am not a font expert, but the fonts in both design are different and
> I
> > > am wondering if there is an official Apache Kafka font that we should
Bejeck, Boyang
> Chen, Bruno Cadonna, Chia-Ping Tsai, Chris Egerton, David
> Arthur, David Jacot, Dezhi “Andy” Fang, Dima Reznik, Ego,
> Evelyn Bayes, Ewen Cheslack-Postava, Greg Harris, Guozhang
> Wang, Ismael Juma, Jason Gustafson, Jeff Widman, Jeremy
> Custenborder, jiameixie, John Roe
Thanks Randall,
I made a pass over the gdoc and it looks great.
Guozhang
On Wed, Aug 5, 2020 at 9:48 AM Randall Hauch wrote:
> Thanks, Jason. We haven't done that for a few releases, but I think it's a
> great idea. I've updated the blog post draft and the Google doc to mention
> the 127
The PMC for Apache Kafka has invited Xi Hu as a committer and we are
pleased to announce that he has accepted!
Xi Hu has been actively contributing to Kafka since 2016, and is well
recognized especially for his non-code contributions: he maintains a tech
blog post evangelizing Kafka in the
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 more than two years ago.
Since then he has presented his experience operating with Kafka Streams at
Pinterest as well as several
ers, I think the problem is very misleading and should be
> > fixed as soon as possible, or a proper exception should be thrown.
> >
> > On Thu, May 28, 2020 at 9:46 AM Guozhang Wang
> wrote:
> >
> > > Hello Pushkar,
> > >
> > > I think the
Apr 28, 2020 at 1:34 AM Benoit Delbosc wrote:
> Hi Guozhang,
> thanks for your reply
>
> On 27.04.20 19:17, Guozhang Wang wrote:
> > Hello Ben,
> >
> > First of all, just to clarify your versioning should be (4.5.0 -> 2.5.0)
> > and (4.3.1 -> 2.3.1) etc, rig
Hello Ben,
First of all, just to clarify your versioning should be (4.5.0 -> 2.5.0)
and (4.3.1 -> 2.3.1) etc, right? Currently Apache Kafka's latest release is
2.5.0.
The RebalanceInProgressException is only introduced in the most recent
releases (2.5.0+), previously it is only used internally
Hello folks,
The Bay Area Kafka meetup will continue to be hosted online this month,
next Tuesday (April 21st) 4:00pm. We will be presenting the current on
going work for a Kafkaesque Raft Protocol:
I think it is an appropriate to support multi-way joins of KTables
(including outer, left), but it is not necessarily an extension of the
"co-group" syntax. We can start this discussion as a separate KIP.
Guozhang
Hi Federico,
I'd think you could re-post this question here:
https://github.com/confluentinc/ksql/issues.
Cheers,
Guozhang
On Fri, Apr 17, 2020 at 8:57 AM Federico D'Ambrosio
wrote:
> So, I tried with another query which hangs and I get this, after its
> corresponding TERMINATE command:
>
>
Hello Murilo,
Thanks for your interests in KIP-150.
As we discussed in the KIP, the scope of this co-group is for stream
co-aggregation. For your case, the first joining table is not from the
aggregation but is a source table itself, in this case it cannot be
included in the co-group of KIP-150.
Hello Nicolae,
If your output topic is configured as log compacted, then sending a record
with null-bytes effectively serves as a tombstone. Note that you'd need to
make sure in your sink node's serializer that the serialized bytes are null
when the unserialized object typed value indicates to be
Thanks for the reported issue.
For guava I think we should just upgrade version to 24.1.1 or newer to
resolve 10237.
For rocksdbjni, I saw that at the moment even current master is still using
bzip version 1.0.6 so 3189 and 12900 would be existed in newest rocksDB
version. I'd suggest you post
Hello Tim,
The following link should be the source of truth for EOL policy:
https://cwiki.apache.org/confluence/display/KAFKA/Time+Based+Release+Plan#TimeBasedReleasePlan-WhatIsOurEOLPolicy?
Guozhang
On Tue, Apr 7, 2020 at 5:54 AM Gaudet, Timothy
wrote:
> Hello,
>
> I am trying to find the
I think it is a regression, since it was introduced in KAFKA-9437: KIP-559,
which is in 2.5.0, so it means for the same scenario described in Boyang's
PR, 2.5 would fail while 2.4 would not.
Guozhang
On Fri, Mar 20, 2020 at 6:59 PM Ismael Juma wrote:
> Hi Boyang,
>
> Is this a regression?
>
>
Hi Stephen,
We've deprecated the partition-grouper API due to its drawbacks in
upgrading compatibility (consider if you want to change the num.partitions
while evolving your application), and instead we're working on KIP-221 for
the same purpose of your use case:
wrote:
> Guozhang
> The ticket definitely describes what I’m trying to achieve.
> And should I be hopeful with the fact it’s in progress? :)
> Thanks for pointing that out.
> Murilo
>
> On Fri, Feb 28, 2020 at 2:57 PM Guozhang Wang wrote:
>
> > Hi Murilo,
> >
Hi Murilo,
Would this be helping your case?
https://issues.apache.org/jira/browse/KAFKA-4835
Guozhang
On Fri, Feb 28, 2020 at 7:01 AM Murilo Tavares wrote:
> Hi
> I am currently doing a simple KTable groupby().aggregate() in KafkaStreams.
> In the groupBy I do need to select a new key, but I
Congrats Konstantine!
Guozhang
On Wed, Feb 26, 2020 at 3:09 PM John Roesler wrote:
> Congrats, Konstantine! Awesome news.
> -John
>
> On Wed, Feb 26, 2020, at 16:39, Bill Bejeck wrote:
> > Congratulations Konstantine! Well deserved.
> >
> > -Bill
> >
> > On Wed, Feb 26, 2020 at 5:37 PM Jason
.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17044602
> > > .
> > >
> > > With the current behavior, the commands should be:
> > >
> > > `stream.transformValues(...).filter((k,v) -> return v !=
> > > null).groupByK
Hello Adam,
It seems your intention is to not "avoid emitting if the new aggregation
result is the same as the old aggregation" but to "avoid processing the
aggregation at all if it state is already some certain value", right?
In this case I think you can try sth. like this:
gt; KStream otherStream2,
> ...
> (va, vb, vc, ...) -> ...
> )
> This way we can join multiple streams and whose resultant stream if of type
> (K, VA+VB+VC...)
>
> Let me know if something like this can be useful.
>
> Thanks
> Sachin
>
&g
ms and order may not hold, then
> what may be a good way to ensure streamB records are enriched with the
> joined data of streamAA and streamAB.
>
> Thanks
> Sachin
>
>
>
> On Sat, Feb 22, 2020 at 2:33 AM Guozhang Wang wrote:
>
> > From the description it seems there
Hello,
As far as I know Kafka connect's Rest server depends on Glassfish for
web-app configuration; the Kafka brokers do not.
Guozhang
On Sat, Feb 22, 2020 at 5:29 AM ashish sood wrote:
> Hello,
>
> This is more of a query rather than an issue. I am working with java based
> application &
that since streamAA and streamAB types of records are before
> streamB type of record in the input topic the join will also happen before.
> If this assumption is not safe then is there any other way of ensuring.
>
> For now lets assume there is single partition of the input topic.
>
> Thanks
Hi Sachin,
The javadoc has a good explanation that you can refer to:
https://kafka.apache.org/24/javadoc/index.html?org/apache/kafka/streams/state/ReadOnlyWindowStore.html
As in our example, both these two would be returned.
Guozhang
On Tue, Feb 18, 2020 at 6:56 AM Sachin Mittal wrote:
>
Hello Sachin,
1) It seems from your source code, that in the stream2.transform you are
generating a new value and return a new key-value pair:
mutate value = enrich(value, result)
return new KeyValue(key, value);
---
Anyways, if you do not want to generate a new value object, and
Hello folks,
This is a kind reminder of the Bay Area Kafka® meetup this Thursday (Feb.
20th) 5:30pm, at Confluent's Mountain View HQ office.
*RSVP and Register* (if you intend to attend in person):
https://www.meetup.com/KafkaBayArea/events/268427599/
*Date*
5:30pm, Thursday, February 20th,
I've added francis lee (francislee) to the contribution list.
On Wed, Feb 12, 2020 at 1:41 AM 萨尔卡 <1026203...@qq.com> wrote:
> hiGuozhang Wang,
> info in cwiki:
>
>
> full name: francis lee
> mail: francislee...@outlook.com
>
>
> Have a nice dayFrancis Lee
>
>
> QQ : 1026203200
>
>
>
--
--
Hi Francis,
What's your apache id?
Guozhang
On Sun, Feb 9, 2020 at 5:50 AM 萨尔卡 <1026203...@qq.com> wrote:
> hi ,
> i want to make a KIP for kafka-exporter by java. how can i do it ?
>
>
>
>
> Have a nice dayFrancis Lee
>
>
> QQ : 1026203200
>
>
>
--
-- Guozhang
Hello Fares,
I remember there's a JIRA ticket for this part, is that what you saw as
well? https://issues.apache.org/jira/browse/KAFKA-9304
Guozhang
On Thu, Feb 6, 2020 at 8:25 AM Fares Oueslati
wrote:
> Thanks for your quick feedback.
>
> Here is a link to the hosted screenshot
a:340)
> >> at
> >>
> org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.poll(ConsumerCoordinator.java:471)
> >> at
> >>
> org.apache.kafka.clients.consumer.KafkaConsumer.updateAssignmentMetadataIfNeeded(KafkaConsumer.java:1267)
>
Hello Aurel,
Maybe this helps:
https://kafka.apache.org/24/documentation/streams/developer-guide/dsl-api.html
Guozhang
On Fri, Dec 27, 2019 at 8:50 AM Aurel Sandu wrote:
> Hi all of you,
>
> I am reading the following code :
> ..
> KTable wordCounts = textLines
>
Guozhang Wang wrote:
> Hello Nitay,
>
> Could you share the topology description on both 2.4 and 2.3.1, and also
> could you elaborate on the feature flag you turned on / off?
>
>
> Guozhang
>
> On Mon, Dec 23, 2019 at 9:32 AM Nitay Kufert wrote:
>
>> Hel
Hello Nitay,
Could you share the topology description on both 2.4 and 2.3.1, and also
could you elaborate on the feature flag you turned on / off?
Guozhang
On Mon, Dec 23, 2019 at 9:32 AM Nitay Kufert wrote:
> Hello,
>
> So as the title says, I am trying to upgrade our streams client to the
hanks,
> > Tomoyuki
> >
> > On Mon, Dec 9, 2019 at 1:52 PM Tomoyuki Saito
> wrote:
> > >
> > > Hi Guozhang,
> > >
> > > Thank you for your suggestion!
> > > I'll create a JIRA within a few days and consider submitting a PR.
> > >
ou are launching a Kafka Streams instance
> of your application. You can run multiple instances of your application.
> >A common scenario is that there are multiple instances of your application
> running in parallel. For more information, see Parallelism Model.
>
> On Mon, Dec 16, 20
Hello Yu,
Could you point to me which page has the reference to this link?
Guozhang
On Sun, Dec 15, 2019 at 2:24 AM Yu Watanabe wrote:
> Hello.
>
> I was walking through kafka streams document and below link seems to be
> invalid. It returns below page.
>
> > Not Found
> > The requested URL
Hello David,
The host information of the group membership is inferred from the socket
channel's ip address, I'm not certain how EC2 spot instance's
application.server config is used, but if it is not dynamically reflected
on the socket channel's inet address then it would be the case you
Hello Tomoyuki,
It seems that issue in 6494 is indeed valid, and I'd personally suggest we
do option 3) to fix the flush() behavior. Please feel free to create a JIRA
(and also submit your PR if you are interested in contributing :).
Guozhang
On Sat, Dec 7, 2019 at 7:59 AM Tomoyuki Saito
Hello Sachin,
Thanks for the detailed description.
Your find is right that for stream-table join the table-side updates would
not trigger a join since stream records are not "materialized" or buffered
during the processing. The community has requested similar semantics to
improve as table-table
Hello Avshalom,
I think the first question to answer is where are the new consumers coming
from. From your description they seem to be not expected (i.e. you did not
intentionally start up new instances), so looking at those VMs that
suddenly start new consumers would be my first shot.
Guozhang
Hi Sachin,
As Patrik mentioned, KIP-150 is being actively worked on and is likely to
be included in the next release.
Guozhang
On Fri, Dec 6, 2019 at 12:09 AM Patrik Kleindl wrote:
> Hi
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-150+-+Kafka-Streams+Cogroup
> might
> be worth a
the starting
time is *earlier
at 5:30*.
*Agenda*
5:30pm - 6:00pm: Networking, Pizza and drinks!
6:00pm - 6:40pm: The Silver Bullet for Endless Rebalances (Guozhang Wang
and Sophie Blee-Goldman, Confluent)
6:40pm - 7:20pm: Kafka as a service at Dropbox (Peng Kang and Richi Gupta,
Dropbox)
7:20pm
Hi Everyone,
The PMC of Apache Kafka is pleased to announce a new Kafka committer, John
Roesler.
John has been contributing to Apache Kafka since early 2018. His main
contributions are primarily around Kafka Streams, but have also included
improving our test coverage beyond Streams as well.
Hello Javier,
When a rebalance happened and the new tasks (hence input partitions) are
assigned that need to be restored, the state of the instance would also
transit to REBALANCING, and would only be transit back to RUNNING after all
tasks have been completed restoring and all are being
Congrats Mickael!
Guozhang
On Thu, Nov 7, 2019 at 1:53 PM Bill Bejeck wrote:
> Congratulations Mickael! Well deserved!
>
> -Bill
>
> On Thu, Nov 7, 2019 at 4:38 PM Jun Rao wrote:
>
> > Hi, Everyone,
> >
> > The PMC of Apache Kafka is pleased to announce a new Kafka committer
> > Mickael
> >
+1. I've ran the quick start and unit tests.
Guozhang
On Tue, Oct 22, 2019 at 12:57 PM David Arthur wrote:
> Thanks, Jonathon and Jason. I've updated the release notes along with the
> signature and checksums. KAFKA-9053 was also missing.
>
> On Tue, Oct 22, 2019 at 3:47 PM Jason Gustafson
>
Hello Sean,
Yes atm we have one producer per task when EOS is turned on compared to one
producer per thread without EOS. There's an ongoing KIP-447 aiming to bring
this back to one producer per thread with EOS as well which involves
broker-side changes.
To answer your question:
1. Assuming each
Hello folks,
This is a kind reminder of the Bay Area Kafka® meetup next Tuesday 6:30pm,
at Confluent's San Francisco office.
*RSVP and Register* (if you intend to attend in person):
https://www.meetup.com/KafkaBayArea/events/264562779/
*Date*
6:30pm, Tuesday, October 1st, 2019
*Location*
Hello Ning,
I've added you to the contributors list.
Cheers,
Guozhang
On Tue, Sep 10, 2019 at 10:27 AM Ning Liu wrote:
> Sorry, I forget to add my profile here
>
> Account signup
>
> You have signed up for a Jira account at:
> https://issues.apache.org/jira
> If you forget your password, you
ogy works fine on 0.10.2.1 with kafka-streams 2.2.0,
> > but fails with the error above if I use 2.2.1.
> >
> > I haven't changed any part of the code, simply updated my gradle file
> > updating the dependency.
> >
> > Thanks again
> >
> > On Tue,
Hello Alisson,
The root cause you've seen is the message header support, which is added in
brokers as in 0.11.0 (KIP-82) and in streams client as in 2.0 (KIP-244). If
your code does not add any more headers then it would only inherit the
headers from source topics when trying to write to
t; > trying to spawn up multiple worker and wire up the instance with some
> > static data which will be used in the per message business logic.
> >
> > Thanks
> >
> > On Thu, Aug 1, 2019 at 9:51 AM Guozhang Wang wrote:
> >
> >> Hello Navneeth,
> >
Hello Navneeth,
I may be misunderstanding your intent from the previous emails here, so
just a quick summary:
1) if you just want to "know" which partitions are assigned to which
instance, this can be retrieved in multiple ways (e.g. the one mentioned by
Matthias, and also one can get this info
browse/KAFKA-8715. I don't see any
> workarounds for this, so hopefully this can get resolved sooner rather
> than later.
>
> Regards,
> Raman
>
>
>
> On Mon, Jul 22, 2019 at 9:25 PM Guozhang Wang wrote:
> >
> > Hello Raman, since you are using Cons
ging rate to the rate at which records
> are produced?
>
> Best,
>
> Pieter
>
> -Oorspronkelijk bericht-
> Van: Guozhang Wang
> Verzonden: Monday, 17 June 2019 22:14
> Aan: users@kafka.apache.org
> Onderwerp: Re: Repeating UNKNOWN_PRODUCER_ID errors for Kafka
Hi Jamie,
The most relevant materials I can think of would be in KIP-101:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-101+-+Alter+Replication+Protocol+to+use+Leader+Epoch+rather+than+High+Watermark+for+Truncation
Although it is a bit out-dated it still contains most significant design
Hello Raman, since you are using Consumer and you are concerning about the
member-failure triggered rebalance, I think KIP-429 is most relevant to
your scenario. As Matthias mentioned we are working on getting it in to the
next release 2.4.
Guozhang
On Sat, Jul 20, 2019 at 6:36 PM Matthias J.
Hello Shurong,
What you bumped into seems to be the same issue as is reported tracked
by Luying
Liu here: https://issues.apache.org/jira/browse/KAFKA-8676.
Guozhang
On Thu, Jun 27, 2019 at 10:48 AM srlin wrote:
> Hi, team,
>
> We are using Kafka Connect at present and have encountered a
Hello Muhammed,
The community is working on KIP-444 that expose rocksDB metrics. There's an
on-going PR that you may find helpful for your own implementation:
https://github.com/apache/kafka/pull/6884
Guozhang
On Wed, Jul 17, 2019 at 6:26 AM Muhammed Ashik wrote:
> Hi I'm trying to log the
Hello folks,
This is just a kind reminder of the Bay Area Kafka® meetup tomorrow,
Tuesday 6:30pm, at Confluent's Palo Alto HQ.
*RSVP and Register* (if you intend to attend in person):
https://www.meetup.com/KafkaBayArea/events/262715611/
please read instructions within the link to register for
en, Colin Hicks, Colin Patrick
> McCabe, commandini, cwildman, Cyrus Vafadari, Dan Norwood, David Arthur,
> Dejan Stojadinović, Dhruvil Shah, Doroszlai, Attila, Ewen Cheslack-Postava,
> Fangbin Sun, Filipe Agapito, Florian Hussonnois, Gardner Vickers, Guozhang
> Wang, Gwen Shapira, Hai
ry retries that follow from it. If there will be a fix for
> this eventually that would make us very happy :-)
>
> Thanks for your efforts so far, and let me know if I can do anything to
> assist. We could continue this work via Slack if you prefer.
>
> Best,
>
> Pieter
>
> -Oors
a volume large enough to
> > produce a record on each partition between every offset commit.
> >
> > Our only options seem to be to move from exactly once to at least
> > once, or to wait for
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-360%3A+Im
min client based on committed input topic offsets. This would explain
> producer id's not being known if the logs get cleaned up almost instantly
> via this process.
>
> Best,
>
> Pieter
>
> -Oorspronkelijk bericht-
> Van: Guozhang Wang
> Verzonden: Thurs
ymore.
>
> Regards
>
> --
> Alessandro Tagliapietra
>
>
> On Thu, Jun 6, 2019 at 10:50 AM Guozhang Wang wrote:
>
> > That's right, but local state is used as a "materialized view" of your
> > changelog topics: if you have nothing locally, then it has to boot
>
> Thank you
>
> --
> Alessandro Tagliapietra
>
>
> On Thu, Jun 6, 2019 at 10:13 AM Guozhang Wang wrote:
>
> > If you deploy your streams app into a docker container, you'd need to
> make
> > sure local state directories are preserved, since otherwise when
I'm trying to upgrade to kafka 2.2.1 to see if I get any
> improvement.
>
> --
> Alessandro Tagliapietra
>
>
> On Wed, Jun 5, 2019 at 4:45 PM Guozhang Wang wrote:
>
> > Hello Alessandro,
> >
> > What did you do for `restarting the app online`? I'm no
build up the set of
> known producers from the log. If a message was produced on a partition 5
> seconds before by the same producer (confirmed via kafkacat), how can it be
> the broker throws an UNKNOWN_PRODUCER_ID exception?
>
> Best,
>
> Pieter
>
> -Oorspronk
Hello Alessandro,
What did you do for `restarting the app online`? I'm not sure I follow the
difference between "restart the streams app" and "restart the app online"
from your description.
Guozhang
On Wed, Jun 5, 2019 at 10:42 AM Alessandro Tagliapietra <
tagliapietra.alessan...@gmail.com>
Especially
> because the cause seems different than the 'low traffic' cause in JIRA
> issue KAFKA-7190 as the partitions for which errors are thrown are
> receiving data.
>
> Best,
>
> Pieter
>
> -Oorspronkelijk bericht-
> Van: Guozhang Wang
> Verzonden: Wedn
Hello Pieter,
If you only have one record every few seconds that may be too small given
you have at least 25 partitions (as I saw you have a xxx--repartition-24
partition), which means that for a single partition, it may not see any
records for a long time, and in this case you may need to
Hello Mohan,
That is right, note though that it is transiting to RUNNING after all
assigned tasks to its threads has completed restoration and starting
running. This means even under REBALANCING state some tasks that finished
restoration early may still be executed as well.
Guozhang
On Tue,
Hello,
Transactional messaging is actually designed to solve this scenario exactly
(pun intended :). Although in your app you may not have stateful logic, it
is still necessary to enable transactional messaging if you are using
consumer/producer, or just enable EOS if you are using streams.
Hello Wenxuan,
One KIP that we are considering so far is KIP-447:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-447%3A+Producer+scalability+for+exactly+once+semantics
It does not directly address your scenarios, but I'm wondering if you can
adjust your code to group the producers if they
memory buffer in mind first and not
> > spilling to disk. I have read the KIP document,
> >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-328%3A+Ability+to+suppress+updates+for+KTables
> > ,
> > but this doesn't mention any specifics as to why the in-memo
Hi Raman,
Since you are using `transformation` already which is a lower-level API in
DSL, you can basically do arbitrary logic like threading pool to process
the records within your `process()` or `transform()` function. Note that,
like consumer docs mentioned `Typically, you must disable
Hello Nayanjyoti,
Did you find anything else from the streams log entries (is it enabled on
DEBUG or TRACE?), and what version of Kafka are you using?
Guozhang
On Sun, May 19, 2019 at 1:04 PM Nayanjyoti Deka
wrote:
> Forgot to add that there is no transition to RUNNING state.
>
> On Mon, May
For who interested in this thread, there's a ticket created for it and we
believe it is a lurking bug and are trying to fix it before the 2.3
release: https://issues.apache.org/jira/browse/KAFKA-8335
Guozhang
On Fri, May 10, 2019 at 10:39 AM Michael Jaschob
wrote:
> Weichu,
>
> while I don't
Hello Emmanuel,
Yes I think it is do-able technically. Note that it means the offsets of
cluster A would be stored on cluster B and hence upon restarting one need
to talk to cluster B in order to get the committed position in cluster A.
Guozhang
On Thu, May 9, 2019 at 11:58 AM Emmanuel
Hello Ishita,
Is it consistently reproducing? And which Kafka version are you using?
Guozhang
On Thu, May 2, 2019 at 5:24 PM Ishita Rakshit wrote:
> Hi,
> I have a Kafka Streams application where I am joining a KStream that reads
> from "topic1" with a GlobalKTable that reads from "topic2"
Hello Everyone,
I'm glad to announce that Matthias J. Sax is now a member of Kafka PMC.
Matthias has been a committer since Jan. 2018, and since then he continued
to be active in the community and made significant contributions the
project.
Congratulations to Matthias!
-- Guozhang
Congrats Harsh!
Guozhang
On Thu, Apr 18, 2019 at 11:46 AM Jun Rao wrote:
> Hi, Everyone,
>
> Sriharsh Chintalapan has been active in the Kafka community since he became
> a Kafka committer in 2015. I am glad to announce that Harsh is now a member
> of Kafka PMC.
>
> Congratulations, Harsh!
>
Hello folks,
The Confluent engineering team would like to invite you all to attend the
first-ever Confluent hosted Bay Area Kafka® meetup on Monday 6pm, at
Confluent's Palo Alto HQ.
*RSVP and Register* (if you intend to attend in person):
https://www.meetup.com/KafkaBayArea/events/260657485/
f a lot of hoops to jump through, and in any case,
> even if I did this, I'm still unclear on how this actually solves the
> race condition (question #3 in my previous message)?
>
> Regards,
> Raman
>
> On Fri, Apr 12, 2019 at 1:57 PM Guozhang Wang wrote:
> >
> >
lve the race condition?
>
> Regards,
> Raman
>
>
>
> On Fri, Apr 5, 2019 at 12:00 PM Guozhang Wang wrote:
> >
> > I see.
> >
> > So back to your original question, yes there will be a race condition
> since
> > the global ktable is updated with a separ
in topic-1 though, using some other information in the
> payload of topic-2.
>
> Regards,
> Raman
>
> On Thu, Apr 4, 2019 at 12:57 AM Guozhang Wang wrote:
> >
> > Hi Raman,
> >
> > What I'm not clear is that since topic-2 is a transformed topic of
> top
e keys. The
> global-ktable allows me to easily look up the values I need from
> topic-1 using an attribute from the payload of topic-2, and combine
> those to write to topic-3.
>
> Regards,
> Raman
>
> On Tue, Apr 2, 2019 at 6:56 PM Guozhang Wang wrote:
> >
> > H
Hello Raman,
It seems from your case that `topic-1` is used for both the global ktable
as well as another stream, which then be transformed to a new stream that
will be "joined" somehow with the global ktable. Could you elaborate your
case a bit more on why do you want to use the same source
Hello Mark,
That's a very general question, and the answer depends on your hardware,
your computational logic etc. Could you elaborate a bit more on your use
case?
Guozhang
On Mon, Apr 1, 2019 at 11:16 AM Mark Fursht
wrote:
> Hello,
>
> I would like to know, how many opened windows Kafka
Hello Anirudh,
The config `upgrade.from` is recommended for safe and smooth upgrade. In
your case it is possible that when rolling bounce the instances the first
upgraded instance happen to be the leader of the group and hence even
without the config it can recognize other instances; but if you
ams?
> The Topology should know all topics and the existence of the topics could
> be verified with the AdminClient.
> This would allow to fail fast similar to when the state directory is not
> available.
> Or am I missing something?
> best regards
> Patrik
>
> On M
Hello Murilo,
Just to give some more background to John's message and KAFKA-7970 here.
The main reason of trickiness is around the scenario of "topics being
partially available", e.g. say your application is joining to topics A and
B, while topicA exists but topicB does not (it is surprisingly
Hello Adrian,
What you described did sounds wired to me. I'm not aware of any regressions
on rocksDB disk usage from 1.1 to 2.1.
Could you file a JIRA ticket with more details like state dir snapshots,
your code snippet and configs etc so we can find a way to reproduce it?
Guozhang
On Fri,
101 - 200 of 1544 matches
Mail list logo
