Re: [ANNOUNCE] New committer: Igor Soarez

2024-04-24 Thread Bill Bejeck
Congrats Igor!

-Bill

On Wed, Apr 24, 2024 at 2:37 PM Tom Bentley  wrote:

> Congratulations Igor!
>
> On Thu, 25 Apr 2024 at 6:27 AM, Chia-Ping Tsai  wrote:
>
> > Congratulations, Igor! you are one of the best Kafka developers!!!
> >
> > Mickael Maison  於 2024年4月25日 週四 上午2:16寫道:
> >
> > > Congratulations Igor!
> > >
> > > On Wed, Apr 24, 2024 at 8:06 PM Colin McCabe 
> wrote:
> > > >
> > > > Hi all,
> > > >
> > > > The PMC of Apache Kafka is pleased to announce a new Kafka committer,
> > > Igor Soarez.
> > > >
> > > > Igor has been a Kafka contributor since 2019. In addition to being a
> > > regular contributor and reviewer, he has made significant contributions
> > to
> > > improving Kafka's JBOD support in KRaft mode. He has also contributed
> to
> > > discussing and reviewing many KIPs such as KIP-690, KIP-554, KIP-866,
> and
> > > KIP-938.
> > > >
> > > > Congratulations, Igor!
> > > >
> > > > Thanks,
> > > >
> > > > Colin (on behalf of the Apache Kafka PMC)
> > >
> >
>


Re: [ANNOUNCE] New Kafka PMC Member: Greg Harris

2024-04-13 Thread Bill Bejeck
Congrats Greg!

-Bill

On Sat, Apr 13, 2024 at 4:25 PM Boudjelda Mohamed Said 
wrote:

> Congratulations Greg
>
> On Sat 13 Apr 2024 at 20:42, Chris Egerton  wrote:
>
> > Hi all,
> >
> > Greg Harris has been a Kafka committer since July 2023. He has remained
> > very active and instructive in the community since becoming a committer.
> > It's my pleasure to announce that Greg is now a member of Kafka PMC.
> >
> > Congratulations, Greg!
> >
> > Chris, on behalf of the Apache Kafka PMC
> >
>


Re: [EXT] Re: [DISCUSS] KIP-1033: Add Kafka Streams exception handler for exceptions occuring during processing

2024-04-09 Thread Bill Bejeck
Hi Damien, Sebastien and Loic,

Thanks for the KIP, this is a much-needed addition.
I like the approach of getting the plumbing in for handling processor
errors, allowing users to implement more complex solutions as needed.

Overall how where the KIP Is now LGTM, modulo outstanding comments.  I
think adding the example you included in this thread to the KIP is a great
idea.

Regarding the metrics, I'm thinking along the same lines as Bruno.  I'm
wondering if we can make do with a task-level metric at the INFO level and
the processor metric at DEBUG.  IMHO, when it comes to tracking exceptions
in processing, these two areas are where users will want to focus, higher
level metrics wouldn't be as useful in this case.

Thanks,
Bill

On Tue, Apr 9, 2024 at 6:54 AM Bruno Cadonna  wrote:

> Hi again,
>
> I have additional questions/comments.
>
> 6.
> What record is exactly passed to the handler?
> Is it the input record to the task? Is it the input record to the
> processor node? Is it the input record to the processor?
>
>
> 7.
> Could you please add the packages of the Java classes/interfaces/enums
> you want to add?
>
>
> Best,
> Bruno
>
>
> On 4/9/24 10:17 AM, Bruno Cadonna wrote:
> > Hi Loïc, Damien, and Sébastien,
> >
> > Thanks for the KIP!
> > I find it really great that you contribute back to Kafka Streams
> > concepts you developed for kstreamplify so that everybody can take
> > advantage from your improvements.
> >
> > I have a couple of questions/comments:
> >
> > 1. and 2.
> > I am wondering whether we should expose the processor node ID -- which
> > basically is the processor node name -- in the ProcessingContext
> > interface. I think the processor node ID fits well in the
> > ProcessingContext interface since it already contains application ID and
> > task ID and it would make the API for the handler cleaner.
> >
> >
> > 3.
> > Could you elaborate -- maybe with an example -- when a record is in a
> > state in which it cannot be serialized? This is not completely clear to
> me.
> >
> >
> > 4.
> > Regarding the metrics, it is not entirely clear to me what the metric
> > measures. Is it the number of calls to the process handler or is it the
> > number of calls to process handler that returned FAIL?
> > If it is the former, I was also wondering whether it would be better to
> > put the task-level metrics to INFO reporting level and remove the
> > thread-level metric, similar to the dropped-records metric. You can
> > always roll-up the metrics to the thread level in your preferred
> > monitoring system. Or do you think we end up with to many metrics?
> >
> >
> > 5.
> > What do you think about naming the handler ProcessingExceptionHandler
> > instead of ProcessExceptionHandler?
> > The DeserializationExceptionHanlder and the ProductionExceptionHandler
> > also use the noun of the action in their name and not the verb.
> >
> >
> > Best,
> > Bruno
> >
> >
> > On 4/8/24 3:48 PM, Sebastien Viale wrote:
> >> Thanks for your review!
> >>
> >>   All the points make sense for us!
> >>
> >>
> >>
> >> We updated the KIP for points 1 and 4.
> >>
> >>
> >>
> >> 2/ We followed the DeserializationExceptionHandler interface
> >> signature, it was not on our mind that the record be forwarded with
> >> the ProcessorContext.
> >>
> >> The ProcessingContext is sufficient, we do expect that most people
> >> would need to access the RecordMetadata.
> >>
> >>
> >>
> >> 3/ The use of Record is required, as the error could
> >> occurred in the middle of a processor where records could be non
> >> serializable objects
> >>
> >>   As it is a global error catching, the user may need little
> >> information about the faulty record.
> >>
> >>   Assuming that users want to make some specific treatments to the
> >> record, they can add a try / catch block in the topology.
> >>
> >>   It is up to users to cast record value and key in the implementation
> >> of the ProcessorExceptionHandler.
> >>
> >>
> >>
> >> Cheers
> >>
> >> Loïc, Damien and Sébastien
> >>
> >> 
> >> De : Sophie Blee-Goldman 
> >> Envoyé : samedi 6 avril 2024 01:08
> >> À : dev@kafka.apache.org 
> >> Objet : [EXT] Re: [DISCUSS] KIP-1033: Add Kafka Streams exception
> >> handler for exceptions occuring during processing
> >>
> >> Warning External sender Do not click on any links or open any
> >> attachments unless you trust the sender and know the content is safe.
> >>
> >> Hi Damien,
> >>
> >> First off thanks for the KIP, this is definitely a much needed
> >> feature. On
> >> the
> >> whole it seems pretty straightforward and I am in favor of the proposal.
> >> Just
> >> a few questions and suggestions here and there:
> >>
> >> 1. One of the #handle method's parameters is "ProcessorNode node", but
> >> ProcessorNode is an internal class (and would expose a lot of internals
> >> that we probably don't want to pass in to an exception handler). Would
> it
> >> be sufficient to just make this a String and pass in the processor 

Re: [ANNOUNCE] New committer: Christo Lolov

2024-04-03 Thread Bill Bejeck
Congrats Christo!

-Bill

On Wed, Mar 27, 2024 at 4:03 AM Matthias J. Sax  wrote:

> Congrats!
>
> On 3/26/24 9:39 PM, Christo Lolov wrote:
> > Thank you everyone!
> >
> > It wouldn't have been possible without quite a lot of reviews and
> extremely
> > helpful inputs from you and the rest of the community! I am looking
> forward
> > to working more closely with you going forward :)
> >
> > On Tue, 26 Mar 2024 at 14:31, Kirk True  wrote:
> >
> >> Congratulations Christo!
> >>
> >>> On Mar 26, 2024, at 7:27 AM, Satish Duggana 
> >> wrote:
> >>>
> >>> Congratulations Christo!
> >>>
> >>> On Tue, 26 Mar 2024 at 19:20, Ivan Yurchenko  wrote:
> 
>  Congrats!
> 
>  On Tue, Mar 26, 2024, at 14:48, Lucas Brutschy wrote:
> > Congrats!
> >
> > On Tue, Mar 26, 2024 at 2:44 PM Federico Valeri <
> fedeval...@gmail.com>
> >> wrote:
> >>
> >> Congrats!
> >>
> >> On Tue, Mar 26, 2024 at 2:27 PM Mickael Maison <
> >> mickael.mai...@gmail.com> wrote:
> >>>
> >>> Congratulations Christo!
> >>>
> >>> On Tue, Mar 26, 2024 at 2:26 PM Chia-Ping Tsai  >
> >> wrote:
> 
>  Congrats Christo!
> 
>  Chia-Ping
> >
> >>
> >>
> >
>


Re: [DISCUSS] Personal branches under apache/kafka

2024-03-14 Thread Bill Bejeck
+1

Sounds like a good idea to me.

-Bill

On Wed, Mar 13, 2024 at 2:55 PM Matthias J. Sax  wrote:

> +1
>
> Should be fine to just delete all of them (as long as nobody raised
> objections).
>
> Not sure if we could enable some protection GitHub side that disallow to
> push into non-existing branches and thus avoids accidental branch creation?
>
>
> -Matthias
>
> On 3/13/24 11:39 AM, Josep Prat wrote:
> > Hi Michael,
> >
> > I think it's a good idea. Only "official" branches should exist in the
> > upstream repo.
> > I guess the only exception would be if a massive feature would be done by
> > different individuals collaborating and they would need a "neutral" place
> > for the branch to be. But This didn't happen yet and I doubt it will in
> the
> > near future.
> >
> > Best,
> >
> > ---
> > Josep Prat
> > Open Source Engineering Director, aivenjosep.p...@aiven.io   |
> > +491715557497 | aiven.io
> > Aiven Deutschland GmbH
> > Alexanderufer 3-7, 10117 Berlin
> > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > Amtsgericht Charlottenburg, HRB 209739 B
> >
> > On Wed, Mar 13, 2024, 19:27 José Armando García Sancio
> >  wrote:
> >
> >> On Wed, Mar 13, 2024 at 11:02 AM Mickael Maison
> >>  wrote:
> >>> What do you think?
> >>
> >> I agree. I wouldn't be surprised if these branches (not trunk or
> >> release branches) were created by mistake by the committer.
> >>
> >> Thanks,
> >> --
> >> -José
> >>
> >
>


Re: [VOTE] 3.6.1 RC0

2023-12-01 Thread Bill Bejeck
Hi Mickael,

I did the following:

   1. Validated all checksums, signatures, and hashes
   2. Built from source
   3. Ran all the unit tests
   4. Spot checked the documentation and Javadoc
   5. Ran the ZK, Kraft, and Kafka Streams quickstart guides

I did notice that the `fillDotVersion` in `js/templateData.js` needs
updating to `3.6.1`, but this is minor and should not block the release.

It's a +1(binding) for me, pending the successful system test run

Thanks,
Bill

On Fri, Dec 1, 2023 at 1:49 PM Justine Olshan 
wrote:

> I've started a system test run on my end.
>
> Justine
>
> On Wed, Nov 29, 2023 at 1:55 PM Justine Olshan 
> wrote:
>
> > I built from source and ran a simple transactional produce bench. I ran a
> > handful of unit tests as well.
> > I scanned the docs and everything looked reasonable.
> >
> > I was wondering if we got the system test results mentioned > System
> > tests: Still running I'll post an update once they complete.
> >
> > Justine
> >
> > On Wed, Nov 29, 2023 at 6:33 AM Mickael Maison  >
> > wrote:
> >
> >> Hi Josep,
> >>
> >> Good catch!
> >> If it's the only issue we find, I don't think we should block the
> >> release just to fix that.
> >>
> >> If we find another issue, I'll backport it before running another RC,
> >> otherwise I'll backport it once 3.6.1 is released.
> >>
> >> Thanks,
> >> Mickael
> >>
> >> On Wed, Nov 29, 2023 at 11:55 AM Josep Prat  >
> >> wrote:
> >> >
> >> > Hi Mickael,
> >> > This PR[1] made me realize NOTICE-binary is missing the notice for
> >> > commons-io. I don't know if it's a blocker or not. I can cherry pick
> the
> >> > commit to the 3.6 branch if you want.
> >> >
> >> > Best,
> >> >
> >> >
> >> > [1]: https://github.com/apache/kafka/pull/14865
> >> >
> >> > On Tue, Nov 28, 2023 at 10:25 AM Josep Prat 
> >> wrote:
> >> >
> >> > > Hi Mickael,
> >> > > Thanks for running the release. It's a +1 for me (non-binding).
> >> > > I did the following:
> >> > > - Verified artifact's signatures and hashes
> >> > > - Checked JavaDoc (with navigation to Oracle JavaDoc)
> >> > > - Compiled source code
> >> > > - Run unit tests and integration tests
> >> > > - Run getting started with ZK and KRaft
> >> > >
> >> > > Best,
> >> > >
> >> > > On Tue, Nov 28, 2023 at 8:51 AM Kamal Chandraprakash <
> >> > > kamal.chandraprak...@gmail.com> wrote:
> >> > >
> >> > >> +1 (non-binding)
> >> > >>
> >> > >> 1. Built the source from 3.6.1-rc0 tag in scala 2.12 and 2.13
> >> > >> 2. Ran all the unit and integration tests.
> >> > >> 3. Ran quickstart and verified the produce-consume on a 3 node
> >> cluster.
> >> > >> 4. Verified the tiered storage functionality with local-tiered
> >> storage.
> >> > >>
> >> > >> On Tue, Nov 28, 2023 at 12:55 AM Federico Valeri <
> >> fedeval...@gmail.com>
> >> > >> wrote:
> >> > >>
> >> > >> > Hi Mickael,
> >> > >> >
> >> > >> > - Build from source (Java 17, Scala 2.13)
> >> > >> > - Run unit and integration tests
> >> > >> > - Run custom client apps using staging artifacts
> >> > >> >
> >> > >> > +1 (non binding)
> >> > >> >
> >> > >> > Thanks
> >> > >> > Fede
> >> > >> >
> >> > >> >
> >> > >> >
> >> > >> > On Sun, Nov 26, 2023 at 11:34 AM Jakub Scholz 
> >> wrote:
> >> > >> > >
> >> > >> > > +1 non-binding. I used the staged Scala 2.13 artifacts and the
> >> staged
> >> > >> > Maven
> >> > >> > > repo for my tests. All seems to work fine.
> >> > >> > >
> >> > >> > > Thanks
> >> > >> > > Jakub
> >> > >> > >
> >> > >> > > On Fri, Nov 24, 2023 at 4:37 PM Mickael Maison <
> >> mimai...@apache.org>
> >> > >> > wrote:
> >> > >> > >
> >> > >> > > > Hello Kafka users, developers and client-developers,
> >> > >> > > >
> >> > >> > > > This is the first candidate for release of Apache Kafka
> 3.6.1.
> >> > >> > > >
> >> > >> > > > This is a bugfix release with several fixes, including
> >> dependency
> >> > >> > > > version bumps for CVEs.
> >> > >> > > >
> >> > >> > > > Release notes for the 3.6.1 release:
> >> > >> > > >
> >> > >>
> https://home.apache.org/~mimaison/kafka-3.6.1-rc0/RELEASE_NOTES.html
> >> > >> > > >
> >> > >> > > > *** Please download, test and vote by Friday, December 1
> >> > >> > > >
> >> > >> > > > Kafka's KEYS file containing PGP keys we use to sign the
> >> release:
> >> > >> > > > https://kafka.apache.org/KEYS
> >> > >> > > >
> >> > >> > > > * Release artifacts to be voted upon (source and binary):
> >> > >> > > > https://home.apache.org/~mimaison/kafka-3.6.1-rc0/
> >> > >> > > >
> >> > >> > > > * Maven artifacts to be voted upon:
> >> > >> > > >
> >> > >>
> >> https://repository.apache.org/content/groups/staging/org/apache/kafka/
> >> > >> > > >
> >> > >> > > > * Javadoc:
> >> > >> > > > https://home.apache.org/~mimaison/kafka-3.6.1-rc0/javadoc/
> >> > >> > > >
> >> > >> > > > * Tag to be voted upon (off 3.6 branch) is the 3.6.1 tag:
> >> > >> > > > https://github.com/apache/kafka/releases/tag/3.6.1-rc0
> >> > >> > > >
> >> > >> > > > PR for updating docs:
> >> > >> > > > 

Re: [DISCUSS] KIP-992 Proposal to introduce IQv2 Query Types: TimestampedKeyQuery and TimestampedRangeQuery

2023-11-02 Thread Bill Bejeck
Hi Hanyu,

One minor comment.  Can you update the KIP to add the behavior when
developer uses a TimestampedXQuery against a non-timestamped store?

Thanks!
Bill

On Mon, Oct 30, 2023 at 4:46 PM Hanyu (Peter) Zheng
 wrote:

> Hi, Hao,
>
> For TimestampedKeyQuery, it only returns the value of the key, and the
> value should be ValueAndTimestamp.
> If you want to get an  iterator of `ValueAndTimestamp`, you can use
> TimestampedRangeQuery.
>
> Sincerely,
> Hanyu
>
> On Mon, Oct 30, 2023 at 1:42 PM Hanyu (Peter) Zheng 
> wrote:
>
> > Hi, Matthias,
> > Now, if we use TimestampedKeyQuery to query kv-store, it will throw a
> > exception,
> > the exception like this:
> > java.lang.IllegalArgumentException: Cannot get result for failed query.
> >
> > Sincerely,
> > Hanyu
> >
> > On Thu, Oct 26, 2023 at 3:45 PM Hao Li  wrote:
> >
> >> Thanks for the KIP Hanyu! One question: why not return an iterator of
> >> `ValueAndTimestamp` for `TimestampedKeyQuery`? I suppose for a
> >> ts-kv-store, there could be multiple timestamps associated with the same
> >> key?
> >>
> >> Hao
> >>
> >> On Thu, Oct 26, 2023 at 10:23 AM Matthias J. Sax 
> >> wrote:
> >>
> >> > Would we really get a ClassCastException?
> >> >
> >> >  From my understanding, the store would reject the query as
> unsupported
> >> > and thus the returned `QueryResult` object would have it's internal
> flag
> >> > set to indicate the failure, but no exception would be thrown
> directly?
> >> >
> >> > (Of course, there might be an exception thrown to the user if they
> don't
> >> > check `isSuccess()` flag but call `getResult()` directly.)
> >> >
> >> >
> >> > -Matthias
> >> >
> >> > On 10/25/23 8:55 AM, Hanyu (Peter) Zheng wrote:
> >> > > Hi, Bill,
> >> > > Thank you for your reply. Yes, now, if a user executes a timestamped
> >> > query
> >> > > against a non-timestamped store, It will throw ClassCastException.
> >> > > If a user uses KeyQuery to query kv-store or ts-kv-store, it always
> >> > return
> >> > > V.  If a user uses TimestampedKeyQuery to query kv-store, it will
> >> throw a
> >> > > exception, so TimestampedKeyQuery query can only query ts-kv-store
> and
> >> > > return ValueAndTimestamp object in the end.
> >> > >
> >> > > Sincerely,
> >> > > Hanyu
> >> > >
> >> > > On Wed, Oct 25, 2023 at 8:51 AM Hanyu (Peter) Zheng <
> >> pzh...@confluent.io
> >> > >
> >> > > wrote:
> >> > >
> >> > >> Thank you Lucas,
> >> > >>
> >> > >> I will fix the capitalization.
> >> > >> When a user executes a timestamped query against a non-timestamped
> >> > store,
> >> > >> It will throw ClassCastException.
> >> > >>
> >> > >> Sincerely,
> >> > >> Hanyu
> >> > >>
> >> > >> On Tue, Oct 24, 2023 at 1:36 AM Lucas Brutschy
> >> > >>  wrote:
> >> > >>
> >> > >>> Hi Hanyu,
> >> > >>>
> >> > >>> reading the KIP, I was wondering the same thing as Bill.
> >> > >>>
> >> > >>> Other than that, this looks good to me. Thanks for KIP.
> >> > >>>
> >> > >>> nit: you have method names `LowerBound` and `UpperBound`, where
> you
> >> > >>> probably want to fix the capitalization.
> >> > >>>
> >> > >>> Cheers,
> >> > >>> Lucas
> >> > >>>
> >> > >>> On Mon, Oct 23, 2023 at 5:46 PM Bill Bejeck 
> >> wrote:
> >> > >>>>
> >> > >>>> Hey Hanyu,
> >> > >>>>
> >> > >>>> Thanks for the KIP, it's a welcomed addition.
> >> > >>>> Overall, the KIP looks good to me, I just have one comment.
> >> > >>>>
> >> > >>>> Can you discuss the expected behavior when a user executes a
> >> > timestamped
> >> > >>>> query against a non-timestamped store?  I think it should throw
> an
> >> > >>>> exception vs. using some default value.
> >> > &g

Re: [VOTE] KIP-992 Proposal to introduce IQv2 Query Types: TimestampedKeyQuery and TimestampedRangeQuery

2023-11-02 Thread Bill Bejeck
Hi Hanyu,

Thanks for the KIP this LGTM.
+1 (binding)

Thanks,
Bill



On Wed, Nov 1, 2023 at 1:07 PM Hanyu (Peter) Zheng
 wrote:

> Hello everyone,
>
> I would like to start a vote for KIP-992: Proposal to introduce IQv2 Query
> Types: TimestampedKeyQuery and TimestampedRangeQuery.
>
> Sincerely,
> Hanyu
>
> On Wed, Nov 1, 2023 at 10:00 AM Hanyu (Peter) Zheng 
> wrote:
>
> >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-992%3A+Proposal+to+introduce+IQv2+Query+Types%3A+TimestampedKeyQuery+and+TimestampedRangeQuery
> >
> > --
> >
> > [image: Confluent] 
> > Hanyu (Peter) Zheng he/him/his
> > Software Engineer Intern
> > +1 (213) 431-7193 <+1+(213)+431-7193>
> > Follow us: [image: Blog]
> > <
> https://www.confluent.io/blog?utm_source=footer_medium=email_campaign=ch.email-signature_type.community_content.blog
> >[image:
> > Twitter] [image: LinkedIn]
> > [image: Slack]
> > [image: YouTube]
> > 
> >
> > [image: Try Confluent Cloud for Free]
> > <
> https://www.confluent.io/get-started?utm_campaign=tm.fm-apac_cd.inbound_source=gmail_medium=organic
> >
> >
>
>
> --
>
> [image: Confluent] 
> Hanyu (Peter) Zheng he/him/his
> Software Engineer Intern
> +1 (213) 431-7193 <+1+(213)+431-7193>
> Follow us: [image: Blog]
> <
> https://www.confluent.io/blog?utm_source=footer_medium=email_campaign=ch.email-signature_type.community_content.blog
> >[image:
> Twitter] [image: LinkedIn]
> [image: Slack]
> [image: YouTube]
> 
>
> [image: Try Confluent Cloud for Free]
> <
> https://www.confluent.io/get-started?utm_campaign=tm.fm-apac_cd.inbound_source=gmail_medium=organic
> >
>


Re: [ANNOUNCE] New Kafka PMC Member: Satish Duggana

2023-10-27 Thread Bill Bejeck
Congratulations Satish!

On Fri, Oct 27, 2023 at 1:12 PM Matthias J. Sax  wrote:

> Congrats!
>
> On 10/27/23 10:01 AM, Viktor Somogyi-Vass wrote:
> > Congrats Satish!
> >
> > On Fri, Oct 27, 2023, 18:48 Ivan Yurchenko  wrote:
> >
> >> Congrats Satish!
> >>
> >> Ivan
> >>
> >> On Fri, Oct 27, 2023, at 19:02, Kamal Chandraprakash wrote:
> >>> Congratulations Satish!
> >>>
> >>> On Fri, Oct 27, 2023, 21:10 Jorge Esteban Quilcate Otoya <
> >>> quilcate.jo...@gmail.com> wrote:
> >>>
>  Congratulations Satish!!
> 
>  On Fri, 27 Oct 2023 at 18:38, Mickael Maison <
> mickael.mai...@gmail.com
> >>>
>  wrote:
> 
> > Congratulations Satish!
> >
> > On Fri, Oct 27, 2023 at 5:18 PM Lucas Brutschy
> >  wrote:
> >>
> >> Congrats!
> >>
> >> On Fri, Oct 27, 2023 at 5:06 PM Manikumar <
> >> manikumar.re...@gmail.com>
> > wrote:
> >>>
> >>> Congrats!
> >>>
> >>> On Fri, Oct 27, 2023 at 8:35 PM Jun Rao  >>>
> > wrote:
> >>>
>  Hi, Everyone,
> 
>  Satish Duggana has been a Kafka committer since 2022. He has
> >> been
> > very
>  instrumental to the community since becoming a committer. It's
> >> my
> > pleasure
>  to announce that Satish is now a member of Kafka PMC.
> 
>  Congratulations Satish!
> 
>  Jun
>  on behalf of Apache Kafka PMC
> 
> >
> 
> >>>
> >>
> >
>


Re: [DISCUSS] KIP-992 Proposal to introduce IQv2 Query Types: TimestampedKeyQuery and TimestampedRangeQuery

2023-10-23 Thread Bill Bejeck
Hey Hanyu,

Thanks for the KIP, it's a welcomed addition.
Overall, the KIP looks good to me, I just have one comment.

Can you discuss the expected behavior when a user executes a timestamped
query against a non-timestamped store?  I think it should throw an
exception vs. using some default value.
If it's the case that Kafka Stream wraps all stores in a
`TimestampAndValue` store and returning a plain `V` or a
`TimestampAndValue` object depends on the query type, then it would be
good to add those details to the KIP.

Thanks,
Bill



On Fri, Oct 20, 2023 at 5:07 PM Hanyu (Peter) Zheng
 wrote:

> Thank you Matthias,
>
> I will modify the KIP to eliminate this restriction.
>
> Sincerely,
> Hanyu
>
> On Fri, Oct 20, 2023 at 2:04 PM Hanyu (Peter) Zheng 
> wrote:
>
> > Thank you Alieh,
> >
> > In these two new query types, I will remove 'get' from all getter method
> > names.
> >
> > Sincerely,
> > Hanyu
> >
> > On Fri, Oct 20, 2023 at 10:40 AM Matthias J. Sax 
> wrote:
> >
> >> Thanks for the KIP Hanyu,
> >>
> >> One questions:
> >>
> >> > To address this inconsistency, we propose that KeyQuery  should be
> >> restricted to querying kv-stores  only, ensuring that it always returns
> a
> >> plain V  type, making the behavior of the aforementioned code more
> >> predictable. Similarly, RangeQuery  should be dedicated to querying
> >> kv-stores , consistently returning only the plain V .
> >>
> >> Why do you want to restrict `KeyQuery` and `RangeQuery` to kv-stores? I
> >> think it would be possible to still allow both queries for ts-kv-stores,
> >> but change the implementation to return "plain V" instead of
> >> `ValueAndTimestamp`, ie, the implementation would automatically
> >> unwrap the value.
> >>
> >>
> >>
> >> -Matthias
> >>
> >> On 10/20/23 2:32 AM, Alieh Saeedi wrote:
> >> > Hey Hanyu,
> >> >
> >> > Thanks for the KIP. It seems good to me.
> >> > Just one point: AFAIK, we are going to remove "get" from the name of
> all
> >> > getter methods.
> >> >
> >> > Cheers,
> >> > Alieh
> >> >
> >> > On Thu, Oct 19, 2023 at 5:44 PM Hanyu (Peter) Zheng
> >> >  wrote:
> >> >
> >> >> Hello everyone,
> >> >>
> >> >> I would like to start the discussion for KIP-992: Proposal to
> introduce
> >> >> IQv2 Query Types: TimestampedKeyQuery and TimestampedRangeQuery
> >> >>
> >> >> The KIP can be found here:
> >> >>
> >> >>
> >>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-992%3A+Proposal+to+introduce+IQv2+Query+Types%3A+TimestampedKeyQuery+and+TimestampedRangeQuery
> >> >>
> >> >> Any suggestions are more than welcome.
> >> >>
> >> >> Many thanks,
> >> >> Hanyu
> >> >>
> >> >> On Thu, Oct 19, 2023 at 8:17 AM Hanyu (Peter) Zheng <
> >> pzh...@confluent.io>
> >> >> wrote:
> >> >>
> >> >>>
> >> >>>
> >> >>
> >>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-992%3A+Proposal+to+introduce+IQv2+Query+Types%3A+TimestampedKeyQuery+and+TimestampedRangeQuery
> >> >>>
> >> >>> --
> >> >>>
> >> >>> [image: Confluent] 
> >> >>> Hanyu (Peter) Zheng he/him/his
> >> >>> Software Engineer Intern
> >> >>> +1 (213) 431-7193 <+1+(213)+431-7193>
> >> >>> Follow us: [image: Blog]
> >> >>> <
> >> >>
> >>
> https://www.confluent.io/blog?utm_source=footer_medium=email_campaign=ch.email-signature_type.community_content.blog
> >> >>> [image:
> >> >>> Twitter] [image: LinkedIn]
> >> >>> [image: Slack]
> >> >>> [image: YouTube]
> >> >>> 
> >> >>>
> >> >>> [image: Try Confluent Cloud for Free]
> >> >>> <
> >> >>
> >>
> https://www.confluent.io/get-started?utm_campaign=tm.fm-apac_cd.inbound_source=gmail_medium=organic
> >> >>>
> >> >>>
> >> >>
> >> >>
> >> >> --
> >> >>
> >> >> [image: Confluent] 
> >> >> Hanyu (Peter) Zheng he/him/his
> >> >> Software Engineer Intern
> >> >> +1 (213) 431-7193 <+1+(213)+431-7193>
> >> >> Follow us: [image: Blog]
> >> >> <
> >> >>
> >>
> https://www.confluent.io/blog?utm_source=footer_medium=email_campaign=ch.email-signature_type.community_content.blog
> >> >>> [image:
> >> >> Twitter] [image: LinkedIn]
> >> >> [image: Slack]
> >> >> [image: YouTube]
> >> >> 
> >> >>
> >> >> [image: Try Confluent Cloud for Free]
> >> >> <
> >> >>
> >>
> https://www.confluent.io/get-started?utm_campaign=tm.fm-apac_cd.inbound_source=gmail_medium=organic
> >> >>>
> >> >>
> >> >
> >>
> >
> >
> > --
> >
> > [image: Confluent] 
> > Hanyu (Peter) Zheng he/him/his
> > Software Engineer Intern
> > +1 (213) 431-7193 <+1+(213)+431-7193>
> > Follow us: [image: Blog]
> > <
> https://www.confluent.io/blog?utm_source=footer_medium=email_campaign=ch.email-signature_type.community_content.blog
> >[image:
> > Twitter] 

Re: [VOTE] KIP-988 Streams StandbyUpdateListener

2023-10-23 Thread Bill Bejeck
This is a great addition

+1(binding)

-Bill

On Fri, Oct 20, 2023 at 2:29 PM Almog Gavra  wrote:

> +1 (non-binding) - great improvement, thanks Colt & Eduwer!
>
> On Tue, Oct 17, 2023 at 11:25 AM Guozhang Wang  >
> wrote:
>
> > +1 from me.
> >
> > On Mon, Oct 16, 2023 at 1:56 AM Lucas Brutschy
> >  wrote:
> > >
> > > Hi,
> > >
> > > thanks again for the KIP!
> > >
> > > +1 (binding)
> > >
> > > Cheers,
> > > Lucas
> > >
> > >
> > >
> > > On Sun, Oct 15, 2023 at 9:13 AM Colt McNealy 
> > wrote:
> > > >
> > > > Hello there,
> > > >
> > > > I'd like to call a vote on KIP-988 (co-authored by my friend and
> > colleague
> > > > Eduwer Camacaro). We are hoping to get it in before the 3.7.0
> release.
> > > >
> > > >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-988%3A+Streams+Standby+Task+Update+Listener
> > > >
> > > > Cheers,
> > > > Colt McNealy
> > > >
> > > > *Founder, LittleHorse.dev*
> >
>


Re: [DISCUSS] Apache Kafka 3.5.2 release

2023-10-17 Thread Bill Bejeck
Thanks for driving the release, Luke.

+1
-Bill

On Tue, Oct 17, 2023 at 5:05 AM Satish Duggana 
wrote:

> Thanks Luke for volunteering for 3.5.2 release.
>
> On Tue, 17 Oct 2023 at 11:58, Josep Prat 
> wrote:
> >
> > Hi Luke,
> >
> > Thanks for taking this one!
> >
> > Best,
> >
> > On Tue, Oct 17, 2023 at 8:12 AM Luke Chen  wrote:
> >
> > > Hi all,
> > >
> > > I'd like to volunteer as release manager for the Apache Kafka 3.5.2, to
> > > have an important bug/vulnerability fix release for 3.5.1.
> > >
> > > If there are no objections, I'll start building a release plan in
> thewiki
> > > in the next couple of weeks.
> > >
> > > Thanks,
> > > Luke
> > >
> >
> >
> > --
> > [image: Aiven] 
> >
> > *Josep Prat*
> > Open Source Engineering Director, *Aiven*
> > josep.p...@aiven.io   |   +491715557497
> > aiven.io    |   <
> https://www.facebook.com/aivencloud>
> >      <
> https://twitter.com/aiven_io>
> > *Aiven Deutschland GmbH*
> > Alexanderufer 3-7, 10117 Berlin
> > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > Amtsgericht Charlottenburg, HRB 209739 B
>


Re: Apache Kafka 3.7.0 Release

2023-10-09 Thread Bill Bejeck
+1

Thanks, Stanislav!

-Bill

On Mon, Oct 9, 2023 at 1:59 PM Ismael Juma  wrote:

> Thanks for volunteering Stanislav!
>
> Ismael
>
> On Mon, Oct 9, 2023 at 10:51 AM Stanislav Kozlovski
>  wrote:
>
> > Hey all!
> >
> > I would like to volunteer to be the release manager driving the next
> > release - Apache Kafka *3.7.0*.
> >
> > If there are no objections, I will start and share a release plan soon
> > enough!
> >
> > Cheers,
> > Stanislav
> >
>


Re: [DISCUSS] KIP-985 Add reverseRange and reverseAll query over kv-store in IQv2

2023-10-03 Thread Bill Bejeck
Hi Hanyu,

Thanks for the KIP, overall it's looking good, but I have a couple of
comments

   - In the “Proposed Changes” section there's a reference to
   `setReverse()` but the code example has “withDescendingOrder()” so I think
   the text needs an update to reflect the code example.
   - I prefer “withDescendingKeys()”  to “withDescendingOrder()”
   - I also agree that we should include a section on ordering, but it
   should be fairly straightforward.  The “StateQueryRequest” of IQv2 allows
   users to specify a partition or partitions, so if ordering is important
   they can elect to provide a single partition in the query.


Thanks,
Bill

On Tue, Oct 3, 2023 at 5:27 PM Walker Carlson 
wrote:

> Hello Hanyu,
>
> Looking over your kip things mostly make sense but I have a couple of
> comments.
>
>
>1. You have "withDescandingOrder()". I think you mean "descending" :)
>Also there are still a few places in the do where its called
> "setReverse"
>2. Also I like "WithDescendingKeys()" better
>3. I'm not sure of what ordering guarantees we are offering. Perhaps we
>can add a section to the motivation clearly spelling out the current
>ordering and the new offering?
>4. When you say "use unbounded reverseQuery to achieve reverseAll" do
>you mean "use unbounded RangeQuery to achieve reverseAll"? as far as I
> can
>tell we don't have a reverseQuery as a named object?
>
>
> Looking good so far
>
> best,
> Walker
>
> On Tue, Oct 3, 2023 at 2:13 PM Colt McNealy  wrote:
>
> > Hello Hanyu,
> >
> > Thank you for the KIP. I agree with Matthias' proposal to keep the naming
> > convention consistent with KIP-969. I favor the `.withDescendingKeys()`
> > name.
> >
> > I am curious about one thing. RocksDB guarantees that records returned
> > during a range scan are lexicographically ordered by the bytes of the
> keys
> > (either ascending or descending order, as specified in the query). This
> > means that results within a single partition are indeed ordered.** My
> > reading of KIP-805 suggests to me that you don't need to specify the
> > partition number you are querying in IQv2, which means that you can have
> a
> > valid reversed RangeQuery over a store with "multiple partitions" in it.
> >
> > Currently, IQv1 does not guarantee order of keys in this scenario. Does
> > IQv2 support ordering across partitions? Such an implementation would
> > require opening a rocksdb range scan** on multiple rocksdb instances (one
> > per partition), and polling the first key of each. Whether or not this is
> > ordered, could we please add that to the documentation?
> >
> > **(How is this implemented/guaranteed in an `inMemoryKeyValueStore`? I
> > don't know about that implementation).
> >
> > Colt McNealy
> >
> > *Founder, LittleHorse.dev*
> >
> >
> > On Tue, Oct 3, 2023 at 1:35 PM Hanyu (Peter) Zheng
> >  wrote:
> >
> > > ok, I will update it. Thank you  Matthias
> > >
> > > Sincerely,
> > > Hanyu
> > >
> > > On Tue, Oct 3, 2023 at 11:23 AM Matthias J. Sax 
> > wrote:
> > >
> > > > Thanks for the KIP Hanyu!
> > > >
> > > >
> > > > I took a quick look and it think the proposal makes sense overall.
> > > >
> > > > A few comments about how to structure the KIP.
> > > >
> > > > As you propose to not add `ReverseRangQuery` class, the code example
> > > > should go into "Rejected Alternatives" section, not in the "Proposed
> > > > Changes" section.
> > > >
> > > > For the `RangeQuery` code example, please omit all existing methods
> > etc,
> > > > and only include what will be added/changed. This make it simpler to
> > > > read the KIP.
> > > >
> > > >
> > > > nit: typo
> > > >
> > > > >  the fault value is false
> > > >
> > > > Should be "the default value is false".
> > > >
> > > >
> > > > Not sure if `setReverse()` is the best name. Maybe
> > `withDescandingOrder`
> > > > (or similar, I guess `withReverseOrder` would also work) might be
> > > > better? Would be good to align to KIP-969 proposal that suggest do
> use
> > > > `withDescendingKeys` methods for "reverse key-range"; if we go with
> > > > `withReverseOrder` we should change KIP-969 accordingly.
> > > >
> > > > Curious to hear what others think about naming this consistently
> across
> > > > both KIPs.
> > > >
> > > >
> > > > -Matthias
> > > >
> > > >
> > > > On 10/3/23 9:17 AM, Hanyu (Peter) Zheng wrote:
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-985%3A+Add+reverseRange+and+reverseAll+query+over+kv-store+in+IQv2
> > > > >
> > > >
> > >
> > >
> > > --
> > >
> > > [image: Confluent] 
> > > Hanyu (Peter) Zheng he/him/his
> > > Software Engineer Intern
> > > +1 (213) 431-7193 <+1+(213)+431-7193>
> > > Follow us: [image: Blog]
> > > <
> > >
> >
> https://www.confluent.io/blog?utm_source=footer_medium=email_campaign=ch.email-signature_type.community_content.blog
> > > >[image:
> > > Twitter] [image: LinkedIn]
> > > 

Re: [VOTE] 3.6.0 RC2

2023-10-02 Thread Bill Bejeck
Hi Satish,

Thanks for running the release.
I performed the following steps:

   - Validated all the checksums, signatures, and keys
   - Built the release from source
   - Ran all unit tests
   - Quick start validations
  - ZK and Kraft
  - Connect
  - Kafka Streams
   - Spot checked java docs and documentation

+1 (binding)

- Bill

On Mon, Oct 2, 2023 at 10:23 AM Proven Provenzano
 wrote:

> Hi,
>
> To verify the release of release 3.6.0 RC2 I did the following:
>
>- Downloaded the source, built and ran the tests.
>- Validated SCRAM with KRaft including creating credentials with
>kafka-storage.
>- Validated Delegation Tokens with KRaft
>
> +1 (non-binding)
>
> --Proven
>
>
>
> On Mon, Oct 2, 2023 at 8:37 AM Divij Vaidya 
> wrote:
>
> > + 1 (non-binding)
> >
> > Verifications:
> > 1. I ran a produce-consume workload with plaintext auth, JDK17, zstd
> > compression using an open messaging benchmark and found 3.6 to be better
> > than or equal to 3.5.1 across all dimensions. Notably, 3.6 had
> consistently
> > 6-7% lower CPU utilization, lesser spikes on P99 produce latencies and
> > overall lower P99.8 latencies.
> >
> > 2. I have verified that detached signature is correct using
> > https://www.apache.org/info/verification.html and the release manager
> > public keys are available at
> > https://keys.openpgp.org/search?q=F65DC3423D4CD7B9
> >
> > 3. I have verified that all metrics emitted in 3.5.1 (with Zk) are also
> > being emitted in 3.6.0 (with Zk).
> >
> > Problems (but not blockers):
> > 1. Metrics added in
> >
> >
> https://github.com/apache/kafka/commit/2f71708955b293658cec3b27e9a5588d39c38d7e
> > aren't available in the documentation (cc: Justine). I don't consider
> this
> > as a release blocker but we should add it as a fast follow-up.
> >
> > 2. Metric added in
> >
> >
> https://github.com/apache/kafka/commit/a900794ace4dcf1f9dadee27fbd8b63979532a18
> > isn't available in documentation (cc: David). I don't consider this as a
> > release blocker but we should add it as a fast follow-up.
> >
> > --
> > Divij Vaidya
> >
> >
> >
> > On Mon, Oct 2, 2023 at 9:50 AM Federico Valeri 
> > wrote:
> >
> > > Hi Satish, I did the following to verify the release:
> > >
> > > - Built from source with Java 17 and Scala 2.13
> > > - Ran all unit and integration tests
> > > - Spot checked documentation
> > > - Ran custom client applications using staging artifacts on a 3-nodes
> > > cluster
> > > - Tested tiered storage with one of the available RSM implementations
> > >
> > > +1 (non binding)
> > >
> > > Thanks
> > > Fede
> > >
> > > On Mon, Oct 2, 2023 at 8:50 AM Luke Chen  wrote:
> > > >
> > > > Hi Satish,
> > > >
> > > > I verified with:
> > > > 1. Ran quick start in KRaft for scala 2.12 artifact
> > > > 2. Making sure the checksum are correct
> > > > 3. Browsing release notes, documents, javadocs, protocols.
> > > > 4. Verified the tiered storage feature works well.
> > > >
> > > > +1 (binding).
> > > >
> > > > Thanks.
> > > > Luke
> > > >
> > > >
> > > >
> > > > On Mon, Oct 2, 2023 at 5:23 AM Jakub Scholz  wrote:
> > > >
> > > > > +1 (non-binding). I used the Scala 2.13 binaries and the staged
> Maven
> > > > > artifacts and run my tests. Everything seems to work fine for me.
> > > > >
> > > > > Thanks
> > > > > Jakub
> > > > >
> > > > > On Fri, Sep 29, 2023 at 8:17 PM Satish Duggana <
> > > satish.dugg...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Hello Kafka users, developers and client-developers,
> > > > > >
> > > > > > This is the third candidate for the release of Apache Kafka
> 3.6.0.
> > > > > > Some of the major features include:
> > > > > >
> > > > > > * KIP-405 : Kafka Tiered Storage
> > > > > > * KIP-868 : KRaft Metadata Transactions
> > > > > > * KIP-875: First-class offsets support in Kafka Connect
> > > > > > * KIP-898: Modernize Connect plugin discovery
> > > > > > * KIP-938: Add more metrics for measuring KRaft performance
> > > > > > * KIP-902: Upgrade Zookeeper to 3.8.1
> > > > > > * KIP-917: Additional custom metadata for remote log segment
> > > > > >
> > > > > > Release notes for the 3.6.0 release:
> > > > > >
> > https://home.apache.org/~satishd/kafka-3.6.0-rc2/RELEASE_NOTES.html
> > > > > >
> > > > > > *** Please download, test and vote by Tuesday, October 3, 12pm PT
> > > > > >
> > > > > > Kafka's KEYS file containing PGP keys we use to sign the release:
> > > > > > https://kafka.apache.org/KEYS
> > > > > >
> > > > > > * Release artifacts to be voted upon (source and binary):
> > > > > > https://home.apache.org/~satishd/kafka-3.6.0-rc2/
> > > > > >
> > > > > > * Maven artifacts to be voted upon:
> > > > > >
> > > https://repository.apache.org/content/groups/staging/org/apache/kafka/
> > > > > >
> > > > > > * Javadoc:
> > > > > > https://home.apache.org/~satishd/kafka-3.6.0-rc2/javadoc/
> > > > > >
> > > > > > * Tag to be voted upon (off 3.6 branch) is the 3.6.0-rc2 tag:
> > > > > > https://github.com/apache/kafka/releases/tag/3.6.0-rc2
> > > > 

Re: [ANNOUNCE] New Kafka PMC Member: Justine Olshan

2023-09-23 Thread Bill Bejeck
Congrats Justine!

-Bill

On Sat, Sep 23, 2023 at 6:23 PM Greg Harris 
wrote:

> Congratulations Justine!
>
> On Sat, Sep 23, 2023 at 5:49 AM Boudjelda Mohamed Said
>  wrote:
> >
> > Congrats Justin !
> >
> > On Sat 23 Sep 2023 at 14:44, Randall Hauch  wrote:
> >
> > > Congratulations, Justine!
> > >
> > > On Sat, Sep 23, 2023 at 4:25 AM Kamal Chandraprakash <
> > > kamal.chandraprak...@gmail.com> wrote:
> > >
> > > > Congrats Justine!
> > > >
> > > > On Sat, Sep 23, 2023, 13:28 Divij Vaidya 
> > > wrote:
> > > >
> > > > > Congratulations Justine!
> > > > >
> > > > > On Sat 23. Sep 2023 at 07:06, Chris Egerton <
> fearthecel...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Congrats Justine!
> > > > > > On Fri, Sep 22, 2023, 20:47 Guozhang Wang <
> > > guozhang.wang...@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Congratulations!
> > > > > > >
> > > > > > > On Fri, Sep 22, 2023 at 8:44 PM Tzu-Li (Gordon) Tai <
> > > > > tzuli...@apache.org
> > > > > > >
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > Congratulations Justine!
> > > > > > > >
> > > > > > > > On Fri, Sep 22, 2023, 19:25 Philip Nee 
> > > > wrote:
> > > > > > > >
> > > > > > > > > Congrats Justine!
> > > > > > > > >
> > > > > > > > > On Fri, Sep 22, 2023 at 7:07 PM Luke Chen <
> show...@gmail.com>
> > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Hi, Everyone,
> > > > > > > > > >
> > > > > > > > > > Justine Olshan has been a Kafka committer since Dec.
> 2022.
> > > She
> > > > > has
> > > > > > > been
> > > > > > > > > > very active and instrumental to the community since
> becoming
> > > a
> > > > > > > committer.
> > > > > > > > > > It's my pleasure to announce that Justine is now a
> member of
> > > > > Kafka
> > > > > > > PMC.
> > > > > > > > > >
> > > > > > > > > > Congratulations Justine!
> > > > > > > > > >
> > > > > > > > > > Luke
> > > > > > > > > > on behalf of Apache Kafka PMC
> > > > > > > > > >
> > > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
>


Re: [ANNOUNCE] New committer: Yash Mayya

2023-09-21 Thread Bill Bejeck
Congrats Yash!

On Thu, Sep 21, 2023 at 12:26 PM Divij Vaidya 
wrote:

> Congratulations Yash!
>
> Divij Vaidya
>
>
> On Thu, Sep 21, 2023 at 6:18 PM Sagar  wrote:
> >
> > Congrats Yash !
> > On Thu, 21 Sep 2023 at 9:38 PM, Ashwin 
> wrote:
> >
> > > Awesome ! Congratulations Yash !!
> > >
> > > On Thu, Sep 21, 2023 at 9:25 PM Edoardo Comar 
> > > wrote:
> > >
> > > > Congratulations Yash
> > > >
> > > > On Thu, 21 Sept 2023 at 16:28, Bruno Cadonna 
> wrote:
> > > > >
> > > > > Hi all,
> > > > >
> > > > > The PMC of Apache Kafka is pleased to announce a new Kafka
> committer
> > > > > Yash Mayya.
> > > > >
> > > > > Yash's major contributions are around Connect.
> > > > >
> > > > > Yash authored the following KIPs:
> > > > >
> > > > > KIP-793: Allow sink connectors to be used with topic-mutating SMTs
> > > > > KIP-882: Kafka Connect REST API configuration validation timeout
> > > > > improvements
> > > > > KIP-970: Deprecate and remove Connect's redundant task
> configurations
> > > > > endpoint
> > > > > KIP-980: Allow creating connectors in a stopped state
> > > > >
> > > > > Overall, Yash is known for insightful and friendly input to
> discussions
> > > > > and his high quality contributions.
> > > > >
> > > > > Congratulations, Yash!
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Bruno (on behalf of the Apache Kafka PMC)
> > > >
> > >
>


Re: [ANNOUNCE] New committer: Lucas Brutschy

2023-09-21 Thread Bill Bejeck
Congrats Lucas! Well deserved.

— Bill

On Thu, Sep 21, 2023 at 12:21 PM Kirk True  wrote:

> Congratulations, Lucas!
>
> > On Sep 21, 2023, at 9:16 AM, Sagar  wrote:
> >
> > Congrats Lucas !
> >
> > On Thu, 21 Sep 2023 at 9:15 PM, Bruno Cadonna 
> wrote:
> >
> >> Hi all,
> >>
> >> The PMC of Apache Kafka is pleased to announce a new Kafka committer
> >> Lucas Brutschy.
> >>
> >> Lucas' major contributions are around Kafka Streams.
> >>
> >> Lucas' significantly contributed to the state updater
> >> (https://issues.apache.org/jira/browse/KAFKA-10199) and he drives the
> >> implementation of the new threading model for Kafka Streams
> >> (https://issues.apache.org/jira/browse/KAFKA-15326).
> >>
> >> Lucas' contributions to KIP discussions and PR reviews are very
> thoughtful.
> >>
> >> Congratulations, Lucas!
> >>
> >> Thanks,
> >>
> >> Bruno (on behalf of the Apache Kafka PMC)
> >>
>
>


Re: [VOTE] KIP-962 Relax non-null key requirement in Kafka Streams

2023-08-11 Thread Bill Bejeck
+1(binding)

On Fri, Aug 11, 2023 at 7:33 AM Lucas Brutschy
 wrote:

> +1 (non-binding)
>
> On Fri, Aug 11, 2023 at 1:08 AM Matthias J. Sax  wrote:
> >
> > +1 (binding)
> >
> > On 8/10/23 12:31 PM, Florin Akermann wrote:
> > >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-962%3A+Relax+non-null+key+requirement+in+Kafka+Streams
> > >
>


[jira] [Resolved] (KAFKA-15126) Change range queries to accept null lower and upper bounds

2023-08-08 Thread Bill Bejeck (Jira)


 [ 
https://issues.apache.org/jira/browse/KAFKA-15126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bill Bejeck resolved KAFKA-15126.
-
Resolution: Fixed

[Merged to trunk|https://github.com/apache/kafka/pull/14137]

> Change range queries to accept null lower and upper bounds
> --
>
> Key: KAFKA-15126
> URL: https://issues.apache.org/jira/browse/KAFKA-15126
> Project: Kafka
>  Issue Type: Improvement
>  Components: streams
>Reporter: Lucia Cerchie
>Assignee: Lucia Cerchie
>Priority: Minor
> Fix For: 3.6.0
>
>   Original Estimate: 672h
>  Remaining Estimate: 672h
>
> {color:#1d1c1d}When web client requests come in with query params, it's 
> common for those params to be null. We want developers to just be able to 
> pass in the upper/lower bounds if they want instead of implementing their own 
> logic to avoid getting the whole range (which will happen if they leave the 
> params null). {color}
> {color:#1d1c1d}An example of the logic they can avoid using after this KIP is 
> implemented is below:{color}
> {code:java}
> private RangeQuery> 
> createRangeQuery(String lower, String upper) {
> if (isBlank(lower) && isBlank(upper)) {
> return RangeQuery.withNoBounds();
> } else if (!isBlank(lower) && isBlank(upper)) {
> return RangeQuery.withLowerBound(lower);
> } else if (isBlank(lower) && !isBlank(upper)) {
> return RangeQuery.withUpperBound(upper);
> } else {
> return RangeQuery.withRange(lower, upper);
> }
> } {code}
>  
> | |



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


Re: [VOTE] KIP-759: Unneeded repartition canceling

2023-08-01 Thread Bill Bejeck
I caught up on the discussion thread and the KIP LGTM.

+1(binding)

On Tue, Aug 1, 2023 at 3:07 PM Walker Carlson 
wrote:

> +1 (binding)
>
> On Mon, Jul 31, 2023 at 10:43 PM Matthias J. Sax  wrote:
>
> > +1 (binding)
> >
> > On 7/11/23 11:16 AM, Shay Lin wrote:
> > > Hi all,
> > >
> > > I'd like to call a vote on KIP-759: Unneeded repartition canceling
> > > The KIP has been under discussion for quite some time(two years). This
> > is a
> > > valuable optimization for advanced users. I hope we can push this
> toward
> > > the finish line this time.
> > >
> > > Link to the KIP:
> > >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-759%3A+Unneeded+repartition+canceling
> > >
> > > Best,
> > > Shay
> > >
> >
>


Re: [VOTE] KIP-941 Range queries to accept null lower and upper bounds

2023-07-10 Thread Bill Bejeck
Hi Lucia,

Thanks for the KIP! It will be a welcomed improvement.

+1(binding)

-Bill

On Mon, Jul 10, 2023 at 2:40 PM Lucia Cerchie 
wrote:

> Hello everyone,
>
> I'd like to call a vote on KIP-941
> <
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-941%3A+Range+queries+to+accept+null+lower+and+upper+bounds
> >.
> It has been under discussion since June 26, and has received edits to the
> KIP and approval by discussion participants.
>
> Best,
> Lucia
>
> --
>
> [image: Confluent] 
> Lucia Cerchie
> Developer Advocate
> Follow us: [image: Blog]
> <
> https://www.confluent.io/blog?utm_source=footer_medium=email_campaign=ch.email-signature_type.community_content.blog
> >[image:
> Twitter] [image: Slack]
> [image: YouTube]
> 
>
> [image: Try Confluent Cloud for Free]
> <
> https://www.confluent.io/get-started?utm_campaign=tm.fm-apac_cd.inbound_source=gmail_medium=organic
> >
>


Re: [ANNOUNCE] New committer: Greg Harris

2023-07-10 Thread Bill Bejeck
Congrats Greg!

-Bill

On Mon, Jul 10, 2023 at 11:53 AM Divij Vaidya 
wrote:

> Congratulations Greg! I am going through a new committer teething process
> right now and would be happy to get you up to speed. Looking forward to
> working with you in your new role.
>
> --
> Divij Vaidya
>
>
>
> On Mon, Jul 10, 2023 at 5:51 PM Josep Prat 
> wrote:
>
> > Congrats Greg!
> >
> >
> > ———
> > Josep Prat
> >
> > Aiven Deutschland GmbH
> >
> > Alexanderufer 3-7, 10117 Berlin
> >
> > Amtsgericht Charlottenburg, HRB 209739 B
> >
> > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> >
> > m: +491715557497
> >
> > w: aiven.io
> >
> > e: josep.p...@aiven.io
> >
> > On Mon, Jul 10, 2023, 17:47 Matthias J. Sax  wrote:
> >
> > > Congrats!
> > >
> > > On 7/10/23 8:45 AM, Chris Egerton wrote:
> > > > Hi all,
> > > >
> > > > The PMC for Apache Kafka has invited Greg Harris to become a
> committer,
> > > and
> > > > we are happy to announce that he has accepted!
> > > >
> > > > Greg has been contributing to Kafka since 2019. He has made over 50
> > > commits
> > > > mostly around Kafka Connect and Mirror Maker 2. His most notable
> > > > contributions include KIP-898: "Modernize Connect plugin discovery"
> > and a
> > > > deep overhaul of the offset syncing logic in MM2 that addressed
> several
> > > > technically-difficult, long-standing, high-impact issues.
> > > >
> > > > He has also been an active participant in discussions and reviews on
> > the
> > > > mailing lists and on GitHub.
> > > >
> > > > Thanks for all of your contributions, Greg. Congratulations!
> > > >
> > >
> >
>


Re: [ANNOUNCE] New committer: Divij Vaidya

2023-06-15 Thread Bill Bejeck
Congratulations!!

On Tue, Jun 13, 2023 at 7:14 PM ziming deng 
wrote:

> Congratulations, Divij!
> Well deserved!
>
> --
> Ziming
>
> > On Jun 14, 2023, at 09:41, Luke Chen  wrote:
> >
> > Congratulations, Divij!
> > Well deserved!
> >
> > Luke
> >
> > On Wed, Jun 14, 2023 at 7:01 AM Viktor Somogyi-Vass
> >  wrote:
> >
> >> Congrats Divij!
> >>
> >> On Tue, Jun 13, 2023, 20:27 Philip Nee  wrote:
> >>
> >>> Congrats!
> >>>
> >>> On Tue, Jun 13, 2023 at 8:17 PM Randall Hauch 
> wrote:
> >>>
>  Congratulations!
> 
>  On Tue, Jun 13, 2023 at 12:48 PM Matthias J. Sax 
> >>> wrote:
> 
> > Congrats!
> >
> > On 6/13/23 10:24 AM, Satish Duggana wrote:
> >> Congratulations Divij!!
> >>
> >> On Tue, 13 Jun 2023 at 22:41, Manyanda Chitimbo
> >>  wrote:
> >>>
> >>> Congratulations Divij.
> >>>
> >>> On Tue 13 Jun 2023 at 17:50, Bruno Cadonna 
>  wrote:
> >>>
>  Hi all,
> 
>  The PMC of Apache Kafka is pleased to announce a new Kafka
> >>> committer
>  Divij Vaidya.
> 
>  Divij's major contributions are:
> 
>  GDPR compliance enforcement of kafka-site -
>  https://issues.apache.org/jira/browse/KAFKA-13868
> 
>  Performance improvements:
> 
>  Improve performance of VarInt encoding and decoding -
>  https://github.com/apache/kafka/pull/13312
> 
>  Reduce data copy & buffer allocation during decompression -
>  https://github.com/apache/kafka/pull/13135
> 
>  He also was heavily involved in the migration to Mockito.
> 
>  Furthermore, Divij is very active on the mailing lists as well as
> >>> in
>  maintaining and reviewing pull requests.
> 
>  Congratulations, Divij!
> 
>  Thanks,
> 
>  Bruno (on behalf of the Apache Kafka PMC)
> 
> 
>  --
> >>> Manyanda Chitimbo.
> >
> 
> >>>
> >>
>
>


Re: [VOTE] 3.5.0 RC1

2023-06-12 Thread Bill Bejeck
Hi Mickael,

I verified the following:

   1. All signatures and checksums
   2. Built from source
   3. Ran all the unit tests
   4. Ran the Kafka-Zookeeper, Kafka-KRaft, and the Kafka Streams
   quickstarts
   5. Spot-checked the docs
   6. Spot-checked the JavaDocs

It's a +1(binding) for me.
Thanks for running the release!

Regards,
Bill

On Sun, Jun 11, 2023 at 5:38 AM Mickael Maison 
wrote:

> Hi,
>
> We've passed the deadline but we are still missing votes.
> So far we have have 2 binding votes (Luke and John) and 2 non-binding
> votes (Federico and Jakub).
>
> Please take time to test this release candidate and vote.
>
> Thanks,
> Mickael
>
> On Wed, Jun 7, 2023 at 6:26 PM John Roesler  wrote:
> >
> > Thanks for running this release, Mickael!
> >
> > I've verified:
> > * the signature
> > * that I can compile the project
> > * that I can run the tests. I saw one flaky test failure, but I don't
> think it should block us. Reported as
> https://issues.apache.org/jira/browse/KAFKA-13531?focusedCommentId=17730190
> > * the Kafka, Consumer, and Streams quickstarts with ZK and KRaft
> >
> > I'm +1 (binding)
> >
> > Thanks,
> > -John
> >
> > On Wed, Jun 7, 2023, at 06:16, Josep Prat wrote:
> > > Hi MIckael,
> > >
> > > Apparently you did it in this PR already :) :
> > > https://github.com/apache/kafka/pull/13749 (this PR among other things
> > > removes classgraph.
> > >
> > > Without being a lawyer, I think I agree with you as stating we depend
> on
> > > something we don't would be less problematic than the other way around.
> > >
> > > Best,
> > >
> > > On Wed, Jun 7, 2023 at 12:14 PM Mickael Maison <
> mickael.mai...@gmail.com>
> > > wrote:
> > >
> > >> Hi Josep,
> > >>
> > >> Thanks for spotting this. If not already done, can you open a
> > >> ticket/PR to fix this on trunk? It looks like the last couple of
> > >> releases already had that issue. Since we're including a license for a
> > >> dependency we don't ship, I think we can consider this non blocking.
> > >> The other way around (shipping a dependency without its license) would
> > >> be blocking.
> > >>
> > >> Thanks,
> > >> Mickael
> > >>
> > >> On Tue, Jun 6, 2023 at 10:10 PM Jakub Scholz  wrote:
> > >> >
> > >> > +1 (non-binding) ... I used the staged binaries with Scala 2.13 and
> > >> staged
> > >> > artifacts to run my tests. All seems to work fine.
> > >> >
> > >> > Thanks for running the release Mickael!
> > >> >
> > >> > Jakub
> > >> >
> > >> > On Mon, Jun 5, 2023 at 3:39 PM Mickael Maison 
> > >> wrote:
> > >> >
> > >> > > Hello Kafka users, developers and client-developers,
> > >> > >
> > >> > > This is the second candidate for release of Apache Kafka 3.5.0.
> Some
> > >> > > of the major features include:
> > >> > > - KIP-710: Full support for distributed mode in dedicated
> MirrorMaker
> > >> > > 2.0 clusters
> > >> > > - KIP-881: Rack-aware Partition Assignment for Kafka Consumers
> > >> > > - KIP-887: Add ConfigProvider to make use of environment variables
> > >> > > - KIP-889: Versioned State Stores
> > >> > > - KIP-894: Use incrementalAlterConfig for syncing topic
> configurations
> > >> > > - KIP-900: KRaft kafka-storage.sh API additions to support SCRAM
> for
> > >> > > Kafka Brokers
> > >> > >
> > >> > > Release notes for the 3.5.0 release:
> > >> > >
> https://home.apache.org/~mimaison/kafka-3.5.0-rc1/RELEASE_NOTES.html
> > >> > >
> > >> > > *** Please download, test and vote by Friday June 9, 5pm PT
> > >> > >
> > >> > > Kafka's KEYS file containing PGP keys we use to sign the release:
> > >> > > https://kafka.apache.org/KEYS
> > >> > >
> > >> > > * Release artifacts to be voted upon (source and binary):
> > >> > > https://home.apache.org/~mimaison/kafka-3.5.0-rc1/
> > >> > >
> > >> > > * Maven artifacts to be voted upon:
> > >> > >
> https://repository.apache.org/content/groups/staging/org/apache/kafka/
> > >> > >
> > >> > > * Javadoc:
> > >> > > https://home.apache.org/~mimaison/kafka-3.5.0-rc1/javadoc/
> > >> > >
> > >> > > * Tag to be voted upon (off 3.5 branch) is the 3.5.0 tag:
> > >> > > https://github.com/apache/kafka/releases/tag/3.5.0-rc1
> > >> > >
> > >> > > * Documentation:
> > >> > > https://kafka.apache.org/35/documentation.html
> > >> > >
> > >> > > * Protocol:
> > >> > > https://kafka.apache.org/35/protocol.html
> > >> > >
> > >> > > * Successful Jenkins builds for the 3.5 branch:
> > >> > > Unit/integration tests: I'm struggling to get all tests to pass
> in the
> > >> > > same build. I'll run a few more builds to ensure each test pass at
> > >> > > least once in the CI. All tests passed locally.
> > >> > > System tests: The build is still running, I'll send an update
> once I
> > >> > > have the results.
> > >> > >
> > >> > > Thanks,
> > >> > > Mickael
> > >> > >
> > >>
> > >
> > >
> > > --
> > > [image: Aiven] 
> > >
> > > *Josep Prat*
> > > Open Source Engineering Director, *Aiven*
> > > josep.p...@aiven.io   |   +491715557497
> > > aiven.io    |   <
> 

[jira] [Resolved] (KAFKA-14539) Simplify StreamsMetadataState by replacing the Cluster metadata with partition info map

2023-06-07 Thread Bill Bejeck (Jira)


 [ 
https://issues.apache.org/jira/browse/KAFKA-14539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bill Bejeck resolved KAFKA-14539.
-
Resolution: Fixed

> Simplify StreamsMetadataState by replacing the Cluster metadata with 
> partition info map
> ---
>
> Key: KAFKA-14539
> URL: https://issues.apache.org/jira/browse/KAFKA-14539
> Project: Kafka
>  Issue Type: Improvement
>  Components: streams
>Reporter: A. Sophie Blee-Goldman
>Assignee: Danica Fine
>Priority: Major
>
> We can clean up the StreamsMetadataState class a bit by removing the 
> #onChange invocation that currently occurs within 
> StreamsPartitionAssignor#assign, which then lets us remove the `Cluster` 
> parameter in that callback. Instead of building a fake Cluster object from 
> the map of partition info when we invoke #onChange inside the 
> StreamsPartitionAssignor#onAssignment method, we can just directly pass in 
> the  `Map` and replace the usage of `Cluster` 
> everywhere in StreamsMetadataState
> (I believe the current system is a historical artifact from when we used to 
> require passing in a {{Cluster}} for the default partitioning strategy, which 
> the StreamMetadataState needs to compute the partition for a key. At some 
> point in the past we provided a better way to get the default partition, so 
> we no longer need a {{Cluster}} parameter/field at all)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


Re: [ANNOUNCE] Apache Kafka 3.4.1

2023-06-07 Thread Bill Bejeck
Thanks for running the release Luke!

On Wed, Jun 7, 2023 at 4:29 AM Tom Bentley  wrote:

> Thanks Luke!
>
> On Wed, 7 Jun 2023 at 09:11, Mickael Maison 
> wrote:
>
> > Thanks for running the release!
> >
> > On Wed, Jun 7, 2023 at 9:11 AM Bruno Cadonna  wrote:
> > >
> > > Thanks Luke!
> > >
> > > On 07.06.23 07:55, Federico Valeri wrote:
> > > > Thanks Luke!
> > > >
> > > > On Wed, Jun 7, 2023 at 5:56 AM Kamal Chandraprakash
> > > >  wrote:
> > > >>
> > > >> Thanks Luke for running this release!
> > > >>
> > > >> On Wed, Jun 7, 2023 at 8:08 AM Chia-Ping Tsai 
> > wrote:
> > > >>
> > > >>> Thank Luke for this hard work!!!
> > > >>>
> > >  Chris Egerton  於 2023年6月7日 上午10:35 寫道:
> > > 
> > >  Thanks for running this release, Luke!
> > > 
> > >  On Tue, Jun 6, 2023, 22:31 Luke Chen  wrote:
> > > 
> > > > The Apache Kafka community is pleased to announce the release for
> > > > Apache Kafka 3.4.1.
> > > >
> > > > This is a bug fix release and it includes fixes and improvements
> > from
> > > > 58 JIRAs, including a few critical bugs:
> > > > - core
> > > > KAFKA-14644 Process should stop after failure in raft IO thread
> > > > KAFKA-14946 KRaft controller node shutting down while renouncing
> > > >>> leadership
> > > > KAFKA-14887 ZK session timeout can cause broker to shutdown
> > > > - client
> > > > KAFKA-14639 Kafka CooperativeStickyAssignor revokes/assigns
> > partition
> > > > in one rebalance cycle
> > > > - connect
> > > > KAFKA-12558 MM2 may not sync partition offsets correctly
> > > > KAFKA-14666 MM2 should translate consumer group offsets behind
> > > >>> replication
> > > > flow
> > > > - stream
> > > > KAFKA-14172 bug: State stores lose state when tasks are
> reassigned
> > under
> > > > EOS
> > > >
> > > > All of the changes in this release can be found in the release
> > notes:
> > > >
> > > > https://www.apache.org/dist/kafka/3.4.1/RELEASE_NOTES.html
> > > >
> > > > You can download the source and binary release (Scala 2.12 and
> > Scala
> > > >>> 2.13)
> > > > from:
> > > >
> > > > https://kafka.apache.org/downloads#3.4.1
> > > >
> > > >
> > > >
> > > >>>
> >
> ---
> > > >
> > > > Apache Kafka is a distributed streaming platform with four core
> > APIs:
> > > >
> > > > ** The Producer API allows an application to publish a stream
> > records
> > > > to one or more Kafka topics.
> > > >
> > > > ** The Consumer API allows an application to subscribe to one or
> > more
> > > > topics and process the stream of records produced to them.
> > > >
> > > > ** The Streams API allows an application to act as a stream
> > processor,
> > > > consuming an input stream from one or more topics and producing
> an
> > > > output stream to one or more output topics, effectively
> > transforming
> > > > the input streams to output streams.
> > > >
> > > > ** The Connector API allows building and running reusable
> > producers or
> > > > consumers that connect Kafka topics to existing applications or
> > data
> > > > systems. For example, a connector to a relational database might
> > > > capture every change to a table.
> > > >
> > > >
> > > > With these APIs, Kafka can be used for two broad classes of
> > application:
> > > >
> > > > ** Building real-time streaming data pipelines that reliably get
> > data
> > > > between systems or applications.
> > > >
> > > > ** Building real-time streaming applications that transform or
> > react
> > > > to the streams of data.
> > > >
> > > > Apache Kafka is in use at large and small companies worldwide,
> > > > including Capital One, Goldman Sachs, ING, LinkedIn, Netflix,
> > > > Pinterest, Rabobank, Target, The New York Times, Uber, Yelp, and
> > > > Zalando, among others.
> > > >
> > > > A big thank you for the following 32 contributors to this
> release!
> > > >
> > > > atu-sharm, Chia-Ping Tsai, Chris Egerton, Colin Patrick McCabe,
> > > > csolidum, David Arthur, David Jacot, Divij Vaidya, egyedt,
> > > > emilnkrastev, Eric Haag, Greg Harris, Guozhang Wang, Hector
> > Geraldino,
> > > > hudeqi, Jason Gustafson, Jeff Kim, Jorge Esteban Quilcate Otoya,
> > José
> > > > Armando García Sancio, Lucia Cerchie, Luke Chen, Manikumar Reddy,
> > > > Matthias J. Sax, Mickael Maison, Philip Nee, Purshotam Chauhan,
> > Rajini
> > > > Sivaram, Ron Dagostino, Terry, Victoria Xia, Viktor Somogyi-Vass,
> > Yash
> > > > Mayya
> > > >
> > > > We welcome your help and feedback. For more information on how to
> > > > report problems, and to get involved, visit the project website
> at
> > > > https://kafka.apache.org/
> > > >
> > > >
> > > > Thank you!

Re: [VOTE] KIP-923: Add A Grace Period to Stream Table Join

2023-06-05 Thread Bill Bejeck
Hi Walker,

Thanks for the KIP.

I've caught up on the discussion thread and I'm satisfied with all
responses.

+1(binding)

-Bill

On Mon, Jun 5, 2023 at 10:20 AM Bruno Cadonna  wrote:

> Hi Walker,
>
> Thank you for the KIP!
>
> +1 (binding)
>
> Best,
> Bruno
>
> On 24.05.23 23:00, Walker Carlson wrote:
> > Hello everybody,
> >
> > I'm opening the vote on KIP-923 here
> > .
> >
> > If we have more to discus please continue the discussion on the existing
> > thread https://www.mail-archive.com/dev@kafka.apache.org/msg130657.html
> >
> > best,
> > Walker
> >
>


Re: [DISCUSS] Apache Kafka 3.4.1 release

2023-04-26 Thread Bill Bejeck
Thanks for volunteering!

+1

On Wed, Apr 26, 2023 at 8:33 AM Mickael Maison 
wrote:

> Thanks Luke
> +1
>
> On Wed, Apr 26, 2023 at 2:12 PM Chia-Ping Tsai  wrote:
> >
> > +1 to Luke!
> >
> > > David Jacot  於 2023年4月26日 下午6:44 寫道:
> > >
> > > +1 Thanks, Luke!
> > >
> > >> Le mer. 26 avr. 2023 à 12:37, Luke Chen  a écrit :
> > >>
> > >> Hi all,
> > >>
> > >> I'd like to volunteer as release manager for the Apache
> > >> Kafka 3.4.1 release.
> > >> If there are no objections, I'll start building a release plan in the
> > >> wiki in the next couple of days.
> > >>
> > >> Thank you.
> > >> Luke
> > >>
>


Re: [Permission for thachle jira account]

2023-03-17 Thread Bill Bejeck
Peter,

You're all set now.
Thanks for your interest in Apache Kafka.

Regards,
Bill

On Fri, Mar 17, 2023 at 10:13 AM Thach Le  wrote:

> Hello team,
> I just created an account for apache Kafka Jira.
> Please grant my account so I can assign myself to the Jira ticket.
> My account: thachle
>
> Regards,
> Peter
>
> *Skype: thachlp*
> *Phone: (+84) 35 5381 053*
>


Re: [ANNOUNCE] New Kafka PMC Member: David Arthur

2023-03-09 Thread Bill Bejeck
Congratulations David!

On Thu, Mar 9, 2023 at 1:12 PM Jun Rao  wrote:

> Hi, Everyone,
>
> David Arthur has been a Kafka committer since 2013. He has been very
> instrumental to the community since becoming a committer. It's my pleasure
> to announce that David is now a member of Kafka PMC.
>
> Congratulations David!
>
> Jun
> on behalf of Apache Kafka PMC
>


Re: [ANNOUNCE] New Kafka PMC Member: Chris Egerton

2023-03-09 Thread Bill Bejeck
Congratulations Chris!

On Thu, Mar 9, 2023 at 1:12 PM Jun Rao  wrote:

> Hi, Everyone,
>
> Chris Egerton has been a Kafka committer since July 2022. He has been very
> instrumental to the community since becoming a committer. It's my pleasure
> to announce that Chris is now a member of Kafka PMC.
>
> Congratulations Chris!
>
> Jun
> on behalf of Apache Kafka PMC
>


Re: Hosting Kafka Videos on ASF YouTube channel

2023-03-09 Thread Bill Bejeck
Hi Divij,

Thanks for your comments.

I understand what you're saying, and I agree with you to a point.
However,  IHMO, it's necessary right now as we've only created 5 videos in
the past few years.
I'd say leave things as is for now, and if we see an increase in interest
in making videos then we can address a separate youtube channel at that
point.

Regards,
Bill


On Thu, Mar 9, 2023 at 8:51 AM Divij Vaidya  wrote:

> I know that it is a diversion here but perhaps, we might want to consider
> creating an Apache Kafka YouTube channel in itself where we can host these
> videos. It would remove the dependency of reaching out to ASF folks
> everytime we want to upload a new video for Kafka.
>
> We have done something similar for Apache TinkerPop after conferring with
> j...@apache.org. Reference email thread
> https://lists.apache.org/thread/kmdfdf65jvcdpzftwmpvbwbyjrmpfhol and
> YouTube channel https://www.youtube.com/@apachetinkerpop
>
> --
> Divij Vaidya
>
>
>
> On Mon, Mar 6, 2023 at 9:26 PM Brian Proffitt  wrote:
>
> > Yes, I was waiting for you. Just send the links directly to me, along
> > with any other information that may be pertinent, like title,
> description,
> > and speakers for each video.
> >
> > BKP
> >
> > On Mon, Mar 6, 2023 at 3:07 PM Bill Bejeck  wrote:
> >
> > > Hi Brian,
> > >
> > > I'm bumping this thread.  I have download links for all the videos (5)
> > > now, but I'd prefer to share them directly with you or whoever will get
> > > them hosted on the ASF youtube channel.
> > >
> > > Thanks!
> > > Bill
> > >
> > > On Thu, Feb 23, 2023 at 12:13 PM Joe Brockmeier 
> wrote:
> > >
> > >> Actually adding Brian to CC now...
> > >>
> > >> On Thu, Feb 23, 2023 at 12:12 PM Joe Brockmeier 
> wrote:
> > >>
> > >>> Hi Bill,
> > >>>
> > >>> On Thu, Feb 23, 2023 at 10:48 AM Bill Bejeck 
> > wrote:
> > >>>
> > >>>> It took a little time, but I have download links to share with you
> for
> > >>>> the 4 Kafka Streams videos we want to host on the ASF Youtube
> > channel, as
> > >>>> discussed on this thread
> > >>>> <https://lists.apache.org/thread/v4m41pr1kl5fyhkxd5dx32th4kb14hpr>.
> > >>>> The "What is Apache Kafka <https://kafka.apache.org/quickstart>"
> > video
> > >>>> has been edited to remove any vendor reference.  I'll also have a
> > download
> > >>>> link to share for that video soon.
> > >>>>
> > >>>> Where is the best place to share the links with you?  I'd prefer not
> > to
> > >>>> share them with you directly vs. the public.
> > >>>>
> > >>>
> > >>> I've stepped aside from the VP marketing role, Brian Proffitt is now
> > >>> heading up M, so he can help guide you on the uploads. (Brian,
> lemme
> > know
> > >>> if you have questions or whatnot.)
> > >>>
> > >>> Did you mean you'd prefer *to* share them directly vs. publicly?
> Either
> > >>> way, you can work out with Brian/press@ how to share and upload
> them.
> > >>>
> > >>> Thanks,
> > >>>
> > >>> Joe
> > >>>
> > >>
> >
>


Re: Hosting Kafka Videos on ASF YouTube channel

2023-03-06 Thread Bill Bejeck
Hi Brian,

I'm bumping this thread.  I have download links for all the videos (5) now,
but I'd prefer to share them directly with you or whoever will get them
hosted on the ASF youtube channel.

Thanks!
Bill

On Thu, Feb 23, 2023 at 12:13 PM Joe Brockmeier  wrote:

> Actually adding Brian to CC now...
>
> On Thu, Feb 23, 2023 at 12:12 PM Joe Brockmeier  wrote:
>
>> Hi Bill,
>>
>> On Thu, Feb 23, 2023 at 10:48 AM Bill Bejeck  wrote:
>>
>>> It took a little time, but I have download links to share with you for
>>> the 4 Kafka Streams videos we want to host on the ASF Youtube channel, as
>>> discussed on this thread
>>> <https://lists.apache.org/thread/v4m41pr1kl5fyhkxd5dx32th4kb14hpr>.
>>> The "What is Apache Kafka <https://kafka.apache.org/quickstart>" video
>>> has been edited to remove any vendor reference.  I'll also have a download
>>> link to share for that video soon.
>>>
>>> Where is the best place to share the links with you?  I'd prefer not to
>>> share them with you directly vs. the public.
>>>
>>
>> I've stepped aside from the VP marketing role, Brian Proffitt is now
>> heading up M, so he can help guide you on the uploads. (Brian, lemme know
>> if you have questions or whatnot.)
>>
>> Did you mean you'd prefer *to* share them directly vs. publicly? Either
>> way, you can work out with Brian/press@ how to share and upload them.
>>
>> Thanks,
>>
>> Joe
>>
>


Re: [VOTE] KIP-898: Modernize Connect plugin discovery

2023-02-28 Thread Bill Bejeck
Thanks for the well-detailed KIP, Greg. It'll be a needed improvement.

+1(binding)

Thanks,
Bill

On Tue, Feb 28, 2023 at 9:51 AM John Roesler  wrote:

> Thanks for the KIP, Greg!
>
> I’m +1 (binding)
>
> I really appreciate all the care you took in the migration and test
> design.
>
> Thanks,
> John
>
> On Tue, Feb 28, 2023, at 04:33, Federico Valeri wrote:
> > +1 (non binding)
> >
> > Thanks
> > Fede
> >
> > On Tue, Feb 28, 2023 at 10:10 AM Mickael Maison
> >  wrote:
> >>
> >> +1 (binding)
> >>
> >> Thanks,
> >> Mickael
> >>
> >> On Mon, Feb 27, 2023 at 7:42 PM Chris Egerton 
> wrote:
> >> >
> >> > +1 (binding). Thanks for the KIP!
> >> >
> >> > On Mon, Feb 27, 2023 at 12:51 PM Greg Harris
> 
> >> > wrote:
> >> >
> >> > > Hi,
> >> > >
> >> > > I'd like to call a vote for KIP-898 which aims to improve the
> performance
> >> > > of Connect startup by allowing discovery of plugins via the
> ServiceLoader.
> >> > >
> >> > > KIP:
> >> > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-898
> >> > > %3A+Modernize+Connect+plugin+discovery
> >> > >
> >> > > Discussion thread:
> >> > > https://lists.apache.org/thread/wxh0r343w86s91py0876njzbyn5qxd8s
> >> > >
> >> > > Thanks!
> >> > >
>


Re: Hosting Kafka Videos on ASF YouTube channel

2023-02-23 Thread Bill Bejeck
Joe,

It took a little time, but I have download links to share with you for the
4 Kafka Streams videos we want to host on the ASF Youtube channel, as
discussed on this thread
.  The "What
is Apache Kafka " video has been
edited to remove any vendor reference.  I'll also have a download link to
share for that video soon.

Where is the best place to share the links with you?  I'd prefer not to
share them with you directly vs. the public.

Thanks,
Bill


Re: Please help to create an JIRA account for me, thanks

2023-02-22 Thread Bill Bejeck
Hi Koma,

You're all set now.  Note that JIRA only allows lowercase letters for the
user name, so I needed to use "kma" (koma was taken).

Thanks for your interest in Apache Kafka!

-Bill

On Wed, Feb 22, 2023 at 10:06 AM koma zhang  wrote:

> my email: komazhang0...@gmail.com
> preferred username: Koma
> alternate username: Kma
>


Re: [ANNOUNCE] New committer: Lucas Bradstreet

2023-02-17 Thread Bill Bejeck
Congratulations Lucas!

On Fri, Feb 17, 2023 at 4:28 AM Mickael Maison 
wrote:

> Congratulations Lucas!
>
> On Fri, Feb 17, 2023 at 7:59 AM Tom Bentley  wrote:
> >
> > Congratulations!
> >
> > On Fri, 17 Feb 2023 at 05:26, Yash Mayya  wrote:
> >
> > > Congratulations Lucas!
> > >
> > > On Fri, Feb 17, 2023 at 3:25 AM Jun Rao 
> wrote:
> > >
> > > > Hi, Everyone,
> > > >
> > > > The PMC of Apache Kafka is pleased to announce a new Kafka committer
> > > Lucas
> > > > Bradstreet.
> > > >
> > > > Lucas has been a long time Kafka contributor since Oct. 2018. He has
> been
> > > > extremely valuable for Kafka on both performance and correctness
> > > > improvements.
> > > >
> > > > The following are his performance related contributions.
> > > >
> > > > KAFKA-9820: validateMessagesAndAssignOffsetsCompressed allocates
> batch
> > > > iterator which is not used
> > > > KAFKA-9685: Solve Set concatenation perf issue in AclAuthorizer
> > > > KAFKA-9729: avoid readLock in authorizer ACL lookups
> > > > KAFKA-9039: Optimize ReplicaFetcher fetch path
> > > > KAFKA-8841: Reduce overhead of
> ReplicaManager.updateFollowerFetchState
> > > >
> > > > The following are his correctness related contributions.
> > > >
> > > > KAFKA-13194: LogCleaner may clean past highwatermark
> > > > KAFKA-10432: LeaderEpochCache is incorrectly recovered on segment
> > > recovery
> > > > for epoch 0
> > > > KAFKA-9137: Fix incorrect FetchSessionCache eviction logic
> > > >
> > > > Congratulations, Lucas!
> > > >
> > > > Thanks,
> > > >
> > > > Jun (on behalf of the Apache Kafka PMC)
> > > >
> > >
>


Re: [VOTE] 3.4.0 RC2

2023-02-03 Thread Bill Bejeck
I did the following:


   - Validated all checksums and signatures
   - Built from source and ran all the unit tests
   - Ran quickstart steps for ZK, KRaft, and Kafka Streams (with KRaft)
   - Spot checked the docs and Javadocs

Thanks for running the release!

+1(binding)

-Bill


On Fri, Feb 3, 2023 at 5:14 AM David Jacot 
wrote:

> I performed the following validations:
> * Verified all checksums and signatures.
> * Built from source and ran unit tests.
> * Ran the first quickstart steps for both ZK and KRaft.
> * Spotchecked the Javadocs.
>
> I am +1 (binding). Thanks for running the release!
>
> Best,
> David
>
> On Tue, Jan 31, 2023 at 8:00 PM David Arthur 
> wrote:
>
> > Hey folks, we found a couple of blockers with RC1 and have fixed them in
> > the latest release candidate, RC2.
> >
> > The major features of this release include:
> >
> > * KIP-881: Rack-aware Partition Assignment for Kafka Consumers
> > <
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-881%3A+Rack-aware+Partition+Assignment+for+Kafka+Consumers
> > >
> >
> > * KIP-876: Time based cluster metadata snapshots
> > <
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-876%3A+Time+based+cluster+metadata+snapshots
> > >
> >
> > * KIP-787: MM2 manage Kafka resources with custom Admin implementation.
> > <
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=191335620
> > >
> >
> > * KIP-866 ZooKeeper to KRaft Migration
> > <
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-866+ZooKeeper+to+KRaft+Migration
> > >
> > (Early
> > Access)
> >
> >
> >
> > Release notes for the 3.4.0 release:
> >
> > https://home.apache.org/~davidarthur/kafka-3.4.0-rc2/RELEASE_NOTES.html
> >
> >
> > Please download, test and vote by Friday, February 3, 5pm PT
> >
> >
> > ---
> >
> >
> > Kafka's KEYS file containing PGP keys we use to sign the release:
> >
> > https://kafka.apache.org/KEYS
> >
> >
> > * Release artifacts to be voted upon (source and binary):
> >
> > https://home.apache.org/~davidarthur/kafka-3.4.0-rc2/
> >
> >
> > * Maven artifacts to be voted upon:
> >
> > https://repository.apache.org/content/groups/staging/org/apache/kafka/
> >
> >
> > * Javadoc:
> >
> > https://home.apache.org/~davidarthur/kafka-3.4.0-rc2/javadoc/
> >
> >
> > * Tag to be voted upon (off 3.4 branch) is the 3.4.0 tag:
> >
> > https://github.com/apache/kafka/releases/tag/3.4.0-rc2
> >
> >
> > * Documentation:
> >
> > https://kafka.apache.org/34/documentation.html
> >
> >
> > * Protocol:
> >
> > https://kafka.apache.org/34/protocol.html
> >
> >
> > ---
> >
> >
> > Test results:
> >
> >
> > We haven't had a 100% passing build, but the latest system test run looks
> > pretty good:
> >
> >
> http://confluent-kafka-system-test-results.s3-us-west-2.amazonaws.com/3.4/2023-01-31--001.system-test-kafka-3.4--1675184554--confluentinc--3.4--ef3f5bd834/report.html
> >
> >
> > Here are the Jenkins test runs for 3.4:
> > https://ci-builds.apache.org/job/Kafka/job/kafka/job/3.4/. We will
> > continue
> > trying to diagnose the flaky test failures as the release continues. I do
> > not expect that any of these test failures are blockers for the release.
> >
> >
> > Thanks!
> >
> > David Arthur
> >
>


Re: Jira account

2023-02-01 Thread Bill Bejeck
Hi Nelson,

I've created your account and assigned you the role of contributor so
you should be able assign tickets to yourself.
Thanks for your interest in Apache Kafka!

-Bill

On Tue, Jan 31, 2023 at 9:15 PM Nelson Bighetti 
wrote:

> Hi Bill,
>
> Thanks for the prompt reply.
>
> bachmanity...@gmail.com
> bachmanity1
> Nelson Bighetti
>
> Thanks!
>
>
> On Wed, Feb 1, 2023 at 8:15 AM Bill Bejeck  wrote:
>
> > Hi Nelson,
> >
> > Can you provide your preferred email, user-name, and display name I can
> set
> > up your account.
> >
> > Thanks,
> > Bill
> >
> > On Tue, Jan 31, 2023 at 12:51 PM Nelson Bighetti <
> bachmanity...@gmail.com>
> > wrote:
> >
> > > Hello,
> > >
> > > Since November of last year, it's not possible to create Jira account
> in
> > > the Apache organisation. The website says to email the project's
> > > private mailing list to request a Jira account, so can anybody please
> > help
> > > me?
> > >
> > > Thanks in advance!
> > >
> >
>


Re: Jira account

2023-01-31 Thread Bill Bejeck
Hi Nelson,

Can you provide your preferred email, user-name, and display name I can set
up your account.

Thanks,
Bill

On Tue, Jan 31, 2023 at 12:51 PM Nelson Bighetti 
wrote:

> Hello,
>
> Since November of last year, it's not possible to create Jira account in
> the Apache organisation. The website says to email the project's
> private mailing list to request a Jira account, so can anybody please help
> me?
>
> Thanks in advance!
>


Re: [VOTE] KIP-821: Connect Transforms support for nested structures

2023-01-27 Thread Bill Bejeck
Hi Jorge,

Recasting my vote +1(binding).

I'm looking forward to this KIP!

Thanks,
Bill

On Fri, Jan 27, 2023 at 10:11 AM Jorge Esteban Quilcate Otoya <
quilcate.jo...@gmail.com> wrote:

> Hi all,
>
> I'm pleased to announce that the KIP-821 has been accepted with 3 binding
> votes from Chris, John, Mickael, 1 non-binding vote by Robert, and 1
> binding vote to be confirmed by Bill.
>
> Thank you all for your great feedback and contribution to the KIP!
>
> Cheers,
> Jorge.
>
> On Thu, 26 Jan 2023 at 16:21, Mickael Maison 
> wrote:
>
> > +1 (binding)
> > Thanks for the KIP
> >
> > On Tue, Jun 28, 2022 at 10:42 PM Jorge Esteban Quilcate Otoya
> >  wrote:
> > >
> > > Hi everyone,
> > >
> > > I'd like to bump this vote thread. Currently it's missing 1 +1 binding
> > vote
> > > to pass (2 +1 binding, 1 +1 non-binding).
> > >
> > > There has been additional discussions to consider array access and
> > > deep-scan (similar to JsonPath) but hasn't been included as part of
> this
> > > KIP.
> > > The only minor change since the previous votes has been the change of
> > > configuration name: from `field.style` to `field.syntax.version`.
> > >
> > > KIP:
> > >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-821%3A+Connect+Transforms+support+for+nested+structures
> > >
> > > Cheers,
> > > Jorge.
> > >
> > > On Fri, 22 Apr 2022 at 00:01, Bill Bejeck  wrote:
> > >
> > > > Thanks for the KIP, Jorge.
> > > >
> > > > This looks like a great addition to Kafka Connect.
> > > >
> > > > +1(binding)
> > > >
> > > > -Bill
> > > >
> > > > On Thu, Apr 21, 2022 at 6:41 PM John Roesler 
> > wrote:
> > > >
> > > > > Thanks for the KIP, Jorge!
> > > > >
> > > > > I’ve just looked over the KIP, and it looks good to me.
> > > > >
> > > > > I’m +1 (binding)
> > > > >
> > > > > Thanks,
> > > > > John
> > > > >
> > > > > On Thu, Apr 21, 2022, at 09:10, Chris Egerton wrote:
> > > > > > This is a worthwhile addition to the SMTs that ship out of the
> box
> > with
> > > > > > Kafka Connect. +1 non-binding
> > > > > >
> > > > > > On Thu, Apr 21, 2022, 09:51 Jorge Esteban Quilcate Otoya <
> > > > > > quilcate.jo...@gmail.com> wrote:
> > > > > >
> > > > > >> Hi all,
> > > > > >>
> > > > > >> I'd like to start a vote on KIP-821:
> > > > > >>
> > > > > >>
> > > > >
> > > >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-821%3A+Connect+Transforms+support+for+nested+structures
> > > > > >>
> > > > > >> Thanks,
> > > > > >> Jorge
> > > > > >>
> > > > >
> > > >
> >
>


Re: [ANNOUNCE] Apache Kafka 3.3.2

2023-01-25 Thread Bill Bejeck
Thanks for running the release Chris!

On Mon, Jan 23, 2023 at 5:18 PM Chris Egerton  wrote:

> The Apache Kafka community is pleased to announce the release for Apache
> Kafka 3.3.2
>
> Apache Kafka 3.3.2 is a bugfix release and it contains, among other things,
> fixes for 20 issues reported since 3.3.1.
>
> All of the changes in this release can be found in the release notes:
> https://www.apache.org/dist/kafka/3.3.2/RELEASE_NOTES.html
>
>
> You can download the source and binary release (Scala 2.12 and 2.13) from:
> https://kafka.apache.org/downloads#3.3.2
>
>
> ---
>
>
> Apache Kafka is a distributed streaming platform with four core APIs:
>
>
> ** The Producer API allows an application to publish a stream of records to
> one or more Kafka topics.
>
> ** The Consumer API allows an application to subscribe to one or more
> topics and process the stream of records produced to them.
>
> ** The Streams API allows an application to act as a stream processor,
> consuming an input stream from one or more topics and producing an
> output stream to one or more output topics, effectively transforming the
> input streams to output streams.
>
> ** The Connector API allows building and running reusable producers or
> consumers that connect Kafka topics to existing applications or data
> systems. For example, a connector to a relational database might
> capture every change to a table.
>
>
> With these APIs, Kafka can be used for two broad classes of application:
>
> ** Building real-time streaming data pipelines that reliably get data
> between systems or applications.
>
> ** Building real-time streaming applications that transform or react
> to the streams of data.
>
>
> Apache Kafka is in use at large and small companies worldwide, including
> Capital One, Goldman Sachs, ING, LinkedIn, Netflix, Pinterest, Rabobank,
> Target, The New York Times, Uber, Yelp, and Zalando, among others.
>
> A big thank you for the following 39 contributors to this release!
>
> A. Sophie Blee-Goldman, Alyssa Huang, Artem Livshits, Bill Bejeck, Calvin
> Liu, Chia-Ping Tsai, Chris Egerton, Christo Lolov, Colin Patrick McCabe,
> Dan Stelljes, David Arthur, David Jacot, Divij Vaidya, FUNKYE, Greg Harris,
> Huilin Shi, Igor Soarez, Ismael Juma, Jason Gustafson, Jeff Kim, Jorge
> Esteban Quilcate Otoya, José Armando García Sancio, Justine Olshan, Kirk
> True, liuzhuang2017, Lucas Brutschy, Luke Chen, Matthias J. Sax, Mickael
> Maison, Niket, Pratim SC, Purshotam Chauhan, Rohan, Ron Dagostino, Shawn,
> srishti-saraswat, Sushant Mahajan, Vicky Papavasileiou, zou shengfu
>
> We welcome your help and feedback. For more information on how to
> report problems, and to get involved, visit the project website at
> https://kafka.apache.org/
>
> Thank you!
>
>
> Regards,
>
> Chris
>


Re: [ANNOUNCE] New committer: Walker Carlson

2023-01-17 Thread Bill Bejeck
Congratulations, Walker!

-Bill

On Tue, Jan 17, 2023 at 4:57 PM Matthias J. Sax  wrote:

> Dear community,
>
> I am pleased to announce Walker Carlson as a new Kafka committer.
>
> Walker has been contributing to Apache Kafka since November 2019. He
> made various contributions including the following KIPs.
>
> KIP-671: Introduce Kafka Streams Specific Uncaught Exception Handler
> KIP-696: Update Streams FSM to clarify ERROR state meaning
> KIP-715: Expose Committed offset in streams
>
>
> Congratulations Walker and welcome on board!
>
>
> Thanks,
>-Matthias (on behalf of the Apache Kafka PMC)
>


Re: [ANNOUNCE] New committer: Stanislav Kozlovski

2023-01-17 Thread Bill Bejeck
Congratulations Stan!

-Bill

On Tue, Jan 17, 2023 at 11:37 AM Bruno Cadonna  wrote:

> Congrats Stan!
>
> Well deserved!
>
> Best,
> Bruno
>
> On 17.01.23 16:50, Jun Rao wrote:
> > Hi, Everyone,
> >
> > The PMC of Apache Kafka is pleased to announce a new Kafka committer
> > Stanislav Kozlovski.
> >
> > Stan has been contributing to Apache Kafka since June 2018. He made
> various
> > contributions including the following KIPs.
> >
> > KIP-455: Create an Administrative API for Replica Reassignment
> > KIP-412: Extend Admin API to support dynamic application log levels
> >
> > Congratulations, Stan!
> >
> > Thanks,
> >
> > Jun (on behalf of the Apache Kafka PMC)
> >
>


[jira] [Resolved] (KAFKA-14609) Kafka Streams Processor API cannot use state stores

2023-01-09 Thread Bill Bejeck (Jira)


 [ 
https://issues.apache.org/jira/browse/KAFKA-14609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bill Bejeck resolved KAFKA-14609.
-
Resolution: Fixed

Fixed by https://issues.apache.org/jira/browse/KAFKA-14388

> Kafka Streams Processor API cannot use state stores
> ---
>
> Key: KAFKA-14609
> URL: https://issues.apache.org/jira/browse/KAFKA-14609
> Project: Kafka
>  Issue Type: Bug
>  Components: streams
>Affects Versions: 3.3.0
>Reporter: Philipp Schirmer
>Priority: Major
>
> The recently introduced Kafka Streams Processor API (since 3.3, 
> https://issues.apache.org/jira/browse/KAFKA-13654) likely has a bug with 
> regards to using state stores. The 
> [getStateStore|https://javadoc.io/static/org.apache.kafka/kafka-streams/3.3.1/org/apache/kafka/streams/processor/api/ProcessingContext.html#getStateStore-java.lang.String-]
>  method returns null, even though the store has been registered according to 
> the docs. The old transformer API still works. I created a small project that 
> demonstrates the behavior. It uses both methods to register a store for the 
> transformer, as well as the processor API: 
> https://github.com/bakdata/kafka-streams-state-store-demo/blob/main/src/test/java/com/bakdata/kafka/StreamsStateStoreTest.java



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


Re: [ANNOUNCE] New committer: Edoardo Comar

2023-01-07 Thread Bill Bejeck
Congratulations, Edoardo!

-Bill

On Sat, Jan 7, 2023 at 12:11 PM John Roesler  wrote:

> Congrats, Edoardo!
> -John
>
> On Fri, Jan 6, 2023, at 20:47, Matthias J. Sax wrote:
> > Congrats!
> >
> > On 1/6/23 5:15 PM, Luke Chen wrote:
> >> Congratulations, Edoardo!
> >>
> >> Luke
> >>
> >> On Sat, Jan 7, 2023 at 7:58 AM Mickael Maison  >
> >> wrote:
> >>
> >>> Congratulations Edo!
> >>>
> >>>
> >>> On Sat, Jan 7, 2023 at 12:05 AM Jun Rao 
> wrote:
> 
>  Hi, Everyone,
> 
>  The PMC of Apache Kafka is pleased to announce a new Kafka committer
> >>> Edoardo
>  Comar.
> 
>  Edoardo has been a long time Kafka contributor since 2016. His major
>  contributions are the following.
> 
>  KIP-302: Enable Kafka clients to use all DNS resolved IP addresses
>  KIP-277: Fine Grained ACL for CreateTopics API
>  KIP-136: Add Listener name to SelectorMetrics tags
> 
>  Congratulations, Edoardo!
> 
>  Thanks,
> 
>  Jun (on behalf of the Apache Kafka PMC)
> >>>
> >>
>


Re: [ANNOUNCE] New committer: Josep Prat

2023-01-03 Thread Bill Bejeck
Congratulations, Josep!

-Bill

On Tue, Dec 20, 2022 at 9:03 PM Luke Chen  wrote:

> Congratulations, Josep!
>
> Luke
>
> On Wed, Dec 21, 2022 at 6:26 AM Viktor Somogyi-Vass
>  wrote:
>
> > Congrats Josep!
> >
> > On Tue, Dec 20, 2022, 21:56 Matthias J. Sax  wrote:
> >
> > > Congrats!
> > >
> > > On 12/20/22 12:01 PM, Josep Prat wrote:
> > > > Thank you all!
> > > >
> > > > ———
> > > > Josep Prat
> > > >
> > > > Aiven Deutschland GmbH
> > > >
> > > > Immanuelkirchstraße 26, 10405 Berlin
> > > >
> > > > Amtsgericht Charlottenburg, HRB 209739 B
> > > >
> > > > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
> > > >
> > > > m: +491715557497
> > > >
> > > > w: aiven.io
> > > >
> > > > e: josep.p...@aiven.io
> > > >
> > > > On Tue, Dec 20, 2022, 20:42 Bill Bejeck  wrote:
> > > >
> > > >> Congratulations Josep!
> > > >>
> > > >> -Bill
> > > >>
> > > >> On Tue, Dec 20, 2022 at 1:11 PM Mickael Maison <
> > > mickael.mai...@gmail.com>
> > > >> wrote:
> > > >>
> > > >>> Congratulations Josep!
> > > >>>
> > > >>> On Tue, Dec 20, 2022 at 6:55 PM Bruno Cadonna 
> > > >> wrote:
> > > >>>>
> > > >>>> Congrats, Josep!
> > > >>>>
> > > >>>> Well deserved!
> > > >>>>
> > > >>>> Best,
> > > >>>> Bruno
> > > >>>>
> > > >>>> On 20.12.22 18:40, Kirk True wrote:
> > > >>>>> Congrats Josep!
> > > >>>>>
> > > >>>>> On Tue, Dec 20, 2022, at 9:33 AM, Jorge Esteban Quilcate Otoya
> > wrote:
> > > >>>>>> Congrats Josep!!
> > > >>>>>>
> > > >>>>>> On Tue, 20 Dec 2022, 17:31 Greg Harris,
> > > >>  > > >>>>
> > > >>>>>> wrote:
> > > >>>>>>
> > > >>>>>>> Congratulations Josep!
> > > >>>>>>>
> > > >>>>>>> On Tue, Dec 20, 2022 at 9:29 AM Chris Egerton <
> > > >>> fearthecel...@gmail.com>
> > > >>>>>>> wrote:
> > > >>>>>>>
> > > >>>>>>>> Congrats Josep! Well-earned.
> > > >>>>>>>>
> > > >>>>>>>> On Tue, Dec 20, 2022, 12:26 Jun Rao  >
> > > >>> wrote:
> > > >>>>>>>>
> > > >>>>>>>>> Hi, Everyone,
> > > >>>>>>>>>
> > > >>>>>>>>> The PMC of Apache Kafka is pleased to announce a new Kafka
> > > >>> committer
> > > >>>>>>>> Josep
> > > >>>>>>>>>Prat.
> > > >>>>>>>>>
> > > >>>>>>>>> Josep has been contributing to Kafka since May 2021. He
> > > >>> contributed 20
> > > >>>>>>>> PRs
> > > >>>>>>>>> including the following 2 KIPs.
> > > >>>>>>>>>
> > > >>>>>>>>> KIP-773 Differentiate metric latency measured in ms and ns
> > > >>>>>>>>> KIP-744: Migrate TaskMetadata and ThreadMetadata to an
> > interface
> > > >>> with
> > > >>>>>>>>> internal implementation
> > > >>>>>>>>>
> > > >>>>>>>>> Congratulations, Josep!
> > > >>>>>>>>>
> > > >>>>>>>>> Thanks,
> > > >>>>>>>>>
> > > >>>>>>>>> Jun (on behalf of the Apache Kafka PMC)
> > > >>>>>>>>>
> > > >>>>>>>>
> > > >>>>>>>
> > > >>>>>>
> > > >>>>>
> > > >>>
> > > >>
> > > >
> > >
> >
>


Re: [ANNOUNCE] New committer: Justine Olshan

2022-12-29 Thread Bill Bejeck
Congratulations Justine!


-Bill

On Thu, Dec 29, 2022 at 4:36 PM Philip Nee  wrote:

> wow congrats!
>
> On Thu, Dec 29, 2022 at 1:05 PM Chris Egerton 
> wrote:
>
> > Congrats, Justine!
> >
> > On Thu, Dec 29, 2022, 15:58 David Jacot  wrote:
> >
> > > Hi all,
> > >
> > > The PMC of Apache Kafka is pleased to announce a new Kafka committer
> > > Justine
> > > Olshan.
> > >
> > > Justine has been contributing to Kafka since June 2019. She contributed
> > 53
> > > PRs including the following KIPs.
> > >
> > > KIP-480: Sticky Partitioner
> > > KIP-516: Topic Identifiers & Topic Deletion State Improvements
> > > KIP-854: Separate configuration for producer ID expiry
> > > KIP-890: Transactions Server-Side Defense (in progress)
> > >
> > > Congratulations, Justine!
> > >
> > > Thanks,
> > >
> > > David (on behalf of the Apache Kafka PMC)
> > >
> >
>


Re: [ANNOUNCE] New committer: Satish Duggana

2022-12-29 Thread Bill Bejeck
Congratulations Satish!

-Bill

On Thu, Dec 29, 2022 at 11:05 AM Satish Duggana 
wrote:

> Thank you, everyone!
>
> On Wed, 28 Dec 2022 at 00:02, Matthias J. Sax  wrote:
> >
> > Congrats!
> >
> > On 12/27/22 10:20 AM, Kirk True wrote:
> > > Congrats, Satish!
> > >
> > > On Fri, Dec 23, 2022, at 10:07 AM, Jun Rao wrote:
> > >> Hi, Everyone,
> > >>
> > >> The PMC of Apache Kafka is pleased to announce a new Kafka committer
> Satish
> > >> Duggana.
> > >>
> > >> Satish has been a long time Kafka contributor since 2017. He is the
> main
> > >> driver behind KIP-405 that integrates Kafka with remote storage, a
> > >> significant and much anticipated feature in Kafka.
> > >>
> > >> Congratulations, Satish!
> > >>
> > >> Thanks,
> > >>
> > >> Jun (on behalf of the Apache Kafka PMC)
> > >>
> > >
>


Re: [ANNOUNCE] New committer: Josep Prat

2022-12-20 Thread Bill Bejeck
Congratulations Josep!

-Bill

On Tue, Dec 20, 2022 at 1:11 PM Mickael Maison 
wrote:

> Congratulations Josep!
>
> On Tue, Dec 20, 2022 at 6:55 PM Bruno Cadonna  wrote:
> >
> > Congrats, Josep!
> >
> > Well deserved!
> >
> > Best,
> > Bruno
> >
> > On 20.12.22 18:40, Kirk True wrote:
> > > Congrats Josep!
> > >
> > > On Tue, Dec 20, 2022, at 9:33 AM, Jorge Esteban Quilcate Otoya wrote:
> > >> Congrats Josep!!
> > >>
> > >> On Tue, 20 Dec 2022, 17:31 Greg Harris,  >
> > >> wrote:
> > >>
> > >>> Congratulations Josep!
> > >>>
> > >>> On Tue, Dec 20, 2022 at 9:29 AM Chris Egerton <
> fearthecel...@gmail.com>
> > >>> wrote:
> > >>>
> >  Congrats Josep! Well-earned.
> > 
> >  On Tue, Dec 20, 2022, 12:26 Jun Rao 
> wrote:
> > 
> > > Hi, Everyone,
> > >
> > > The PMC of Apache Kafka is pleased to announce a new Kafka
> committer
> >  Josep
> > >   Prat.
> > >
> > > Josep has been contributing to Kafka since May 2021. He
> contributed 20
> >  PRs
> > > including the following 2 KIPs.
> > >
> > > KIP-773 Differentiate metric latency measured in ms and ns
> > > KIP-744: Migrate TaskMetadata and ThreadMetadata to an interface
> with
> > > internal implementation
> > >
> > > Congratulations, Josep!
> > >
> > > Thanks,
> > >
> > > Jun (on behalf of the Apache Kafka PMC)
> > >
> > 
> > >>>
> > >>
> > >
>


Re: [ANNOUNCE] New Kafka PMC Member: Luke Chen

2022-12-16 Thread Bill Bejeck
Congratulations Luke!

-Bill

On Fri, Dec 16, 2022 at 2:47 PM Chris Egerton 
wrote:

> Congrats Luke, well-deserved!
>
> On Fri, Dec 16, 2022, 14:41 Jun Rao  wrote:
>
> > Hi, Everyone,
> >
> > Luke Chen has been a Kafka committer since Feb. 9, 2022. He has been very
> > instrumental to the community since becoming a committer. It's my
> pleasure
> > to announce that Luke  is now a member of Kafka PMC.
> >
> > Congratulations Luke!
> >
> > Jun
> > on behalf of Apache Kafka PMC
> >
>


Re: [ANNOUNCE] New committer: Ron Dagostino

2022-12-16 Thread Bill Bejeck
Congratulations, Ron!

-Bill

On Fri, Dec 16, 2022 at 12:33 PM Matthias J. Sax  wrote:

> Congrats!
>
> On 12/15/22 7:09 AM, Rajini Sivaram wrote:
> > Congratulations, Ron! Well deserved!!
> >
> > Regards,
> >
> > Rajini
> >
> > On Thu, Dec 15, 2022 at 11:42 AM Ron Dagostino 
> wrote:
> >
> >> Thank you, everyone!
> >>
> >> Ron
> >>
> >>> On Dec 15, 2022, at 5:09 AM, Bruno Cadonna  wrote:
> >>>
> >>> Congrats Ron!
> >>>
> >>> Best,
> >>> Bruno
> >>>
>  On 15.12.22 10:23, Viktor Somogyi-Vass wrote:
>  Congrats Ron! :)
> > On Thu, Dec 15, 2022 at 10:22 AM Mickael Maison <
> >> mickael.mai...@gmail.com>
> > wrote:
> > Congratulations Ron!
> >
> > On Thu, Dec 15, 2022 at 9:41 AM Eslam Farag 
> >> wrote:
> >>
> >> Congratulations, Ron ☺️
> >>
> >> On Thu, 15 Dec 2022 at 10:40 AM Tom Bentley 
> >> wrote:
> >>
> >>> Congratulations!
> >>>
> >>> On Thu, 15 Dec 2022 at 07:40, Satish Duggana <
> >> satish.dugg...@gmail.com
> >>
> >>> wrote:
> >>>
>  Congratulations, Ron!!
> 
>  On Thu, 15 Dec 2022 at 07:48, ziming deng <
> dengziming1...@gmail.com
> >>>
>  wrote:
> 
> > Congratulations, Ron!
> > Well deserved!
> >
> > --
> > Ziming
> >
> >> On Dec 15, 2022, at 09:16, Luke Chen  wrote:
> >>
> >> Congratulations, Ron!
> >> Well deserved!
> >>
> >> Luke
> >
> >
> 
> >>>
> >
> >>
> >
>


Re: [ANNOUNCE] New committer: Viktor Somogyi-Vass

2022-12-16 Thread Bill Bejeck
Congratulations, Viktor!

-Bill

On Fri, Dec 16, 2022 at 12:32 PM Matthias J. Sax  wrote:

> Congrats!
>
> On 12/15/22 7:10 AM, Rajini Sivaram wrote:
> > Congratulations, Viktor!
> >
> > Regards,
> >
> > Rajini
> >
> >
> > On Thu, Dec 15, 2022 at 11:41 AM Ron Dagostino 
> wrote:
> >
> >> Congrats to you too, Victor!
> >>
> >> Ron
> >>
> >>> On Dec 15, 2022, at 4:59 AM, Viktor Somogyi-Vass <
> >> viktor.somo...@cloudera.com.invalid> wrote:
> >>>
> >>> Thank you everyone! :)
> >>>
>  On Thu, Dec 15, 2022 at 10:22 AM Mickael Maison <
> >> mickael.mai...@gmail.com>
>  wrote:
> 
>  Congratulations Viktor!
> 
> > On Thu, Dec 15, 2022 at 10:06 AM Tamas Barnabas Egyed
> >  wrote:
> >
> > Congratulations, Viktor!
> 
> >>
> >
>


Re: [VOTE] KIP-878: Internal Topic Autoscaling for Kafka Streams

2022-12-08 Thread Bill Bejeck
Thanks for the KIP, Sophie.

+1(binding)

-Bill

On Thu, Dec 8, 2022 at 11:39 AM Bruno Cadonna  wrote:

> Thanks for the KIP!
>
> +1 (binding)
>
> Best,
> Bruno
>
> On 07.12.22 17:24, Matthias J. Sax wrote:
> > +1 (binding)
> >
> > On 12/1/22 9:39 PM, Sophie Blee-Goldman wrote:
> >> Thanks to all who participated for a great discussion on this KIP. Seems
> >> we're ready to kick off the voting on this, but please don't hesitate to
> >> call
> >> out anything of concern or raise questions over on the voting thread.
> >>
> >> Otherwise, please give it a final look over and cast your vote!
> >>
> >> KIP-878: Internal Topic Autoscaling for Kafka Streams
> >> <
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-878%3A+Internal+Topic+Autoscaling+for+Kafka+Streams
> >
> >> (note the change in name to reflect the decisions in the KIP discussion)
> >>
> >> Thanks,
> >> Sophie
> >>
>


[jira] [Resolved] (KAFKA-14388) NPE When Retrieving StateStore with new Processor API

2022-11-16 Thread Bill Bejeck (Jira)


 [ 
https://issues.apache.org/jira/browse/KAFKA-14388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bill Bejeck resolved KAFKA-14388.
-
Resolution: Fixed

Merged PR to trunk

> NPE When Retrieving StateStore with new Processor API
> -
>
> Key: KAFKA-14388
> URL: https://issues.apache.org/jira/browse/KAFKA-14388
> Project: Kafka
>  Issue Type: Bug
>Affects Versions: 3.3.0, 3.3.1
>    Reporter: Bill Bejeck
>    Assignee: Bill Bejeck
>Priority: Major
> Fix For: 3.4.0, 3.3.2
>
>
> Using the new Processor API introduced with KIP-820 when adding a state store 
> to the Processor when executing `context().getStore("store-name")` always 
> returns `null` as the store is not in the `stores` `HashMap` in the 
> `ProcessorStateManager`.  This occurs even when using the 
> `ConnectedStoreProvider.stores()` method
> I've confirmed the store is associated with the processor by viewing the 
> `Topology` description.   
> From some initial triage, it looks like the store is never registered.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


Re: [DISCUSS] Apache Kafka 3.3.2

2022-11-16 Thread Bill Bejeck
Thanks for volunteering for the release!
+1

-Bill

On Wed, Nov 16, 2022 at 10:58 AM David Jacot 
wrote:

> +1. Thanks for volunteering!
>
> On Wed, Nov 16, 2022 at 4:09 PM Chris Egerton 
> wrote:
> >
> > Hi all,
> >
> > I'd like to volunteer to be the release manager for the next bugfix
> > release, 3.3.2.
> >
> > If there are no objections, I'll send out a release plan by EOD (Eastern
> > Time) Friday that includes a list of all of the fixes we are targeting
> > along with a timeline.
> >
> > Cheers,
> >
> > Chris
>


[jira] [Created] (KAFKA-14388) NPE When Retrieving StateStore with new Processor API

2022-11-14 Thread Bill Bejeck (Jira)
Bill Bejeck created KAFKA-14388:
---

 Summary: NPE When Retrieving StateStore with new Processor API
 Key: KAFKA-14388
 URL: https://issues.apache.org/jira/browse/KAFKA-14388
 Project: Kafka
  Issue Type: Bug
Affects Versions: 3.3.1, 3.3.0
Reporter: Bill Bejeck
Assignee: Bill Bejeck
 Fix For: 3.4.0


Using the new Processor API introduced with KIP-820 when adding a state store 
to the Processor when executing `context().getStore("store-name")` always 
returns `null` as the store is not in the `stores` `HashMap` in the 
`ProcessorStateManager`.  This occurs even when using the 
`ConnectedStoreProvider.stores()` method

I've confirmed the store is associated with the processor by viewing the 
`Topology` description.   

>From some initial triage, it looks like the store is never registered.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


Re: [ANNOUNCE] New Kafka PMC Member: Bruno Cadonna

2022-11-01 Thread Bill Bejeck
Congrats Bruno! Well deserved.

-Bill

On Tue, Nov 1, 2022 at 3:36 PM Guozhang Wang  wrote:

> Hi everyone,
>
> I'd like to introduce our new Kafka PMC member, Bruno.
>
> Bruno has been a committer since April. 2021 and has been very active in
> the community. He's a key contributor to Kafka Streams, and also helped
> review a lot of horizontal improvements such as Mockito. It is my pleasure
> to announce that Bruno has agreed to join the Kafka PMC.
>
> Congratulations, Bruno!
>
> -- Guozhang Wang, on behalf of Apache Kafka PMC
>


Re: [DISCUSS] KIP-878: Autoscaling for Statically Partitioned Streams

2022-10-25 Thread Bill Bejeck
Hi Sophie,

Thanks for the KIP! I think this is a worthwhile feature to add.  I have
two main questions about how this new feature will work.


   1. You mention that for stateless applications auto-scaling is a sticker
   situation.  But I was thinking that the auto-scaling would actually benefit
   stateless applications the most, let me explain my thinking.  Let's say you
   have a stateless Kafka Streams application with one input topic and 2
   partitions, meaning you're limited to at most 2 stream threads.  In order
   to increase the throughput, you increase the number of partitions of the
   source topic to 4, so you can 4 stream threads.  In this case would the
   auto-scaling feature automatically increase the number of tasks from 2 to
   4?  Since the application is stateless, say using a filter then a map for
   example, the partition for the record doesn't matter, so it seems that
   stateless applications would stand to gain a great deal.
   2. For stateful applications I can see the immediate benefit from
   autoscaling and static partitioning.   But again going with a partition
   expansion for increased throughput example, what would be the mitigation
   strategy for a stateful application that eventually wants to take advantage
   of the increased number of partitions? Otherwise keeping all keys on their
   original partition means you could end up with "key skew" due to not
   allowing keys to distribute out to the new partitions.

One last comment, the KIP states "only the key, rather than the key and
value, are passed in to the partitioner", but the interface has it taking a
key and a value as parameters.  Based on your comments earlier in this
thread I was thinking that the text needs to be updated.

Thanks,
Bill

On Fri, Oct 21, 2022 at 12:21 PM Lucas Brutschy
 wrote:

> Hi all,
>
> thanks, Sophie, this makes sense. I suppose then the way to help the user
> not apply this in the wrong setting is having good documentation and a one
> or two examples of good use cases.
>
> I think Colt's time-based partitioning is a good example of how to use
> this. It actually doesn't have to be time, the same will work with any
> monotonically increasing identifier. I.e. the new partitions will only get
> records for users with a "large" user ID greater than some user ID
> threshold hardcoded in the static partitioner. At least in this restricted
> use-case, lookups by user ID would still be possible.
>
> Cheers,
> Lucas
>
> On Fri, Oct 21, 2022 at 5:37 PM Colt McNealy  wrote:
>
> > Sophie,
> >
> > Regarding item "3" (my last paragraph from the previous email), perhaps I
> > should give a more general example now that I've had more time to clarify
> > my thoughts:
> >
> > In some stateful applications, certain keys have to be findable without
> any
> > information about when the relevant data was created. For example, if I'm
> > running a word-count app and I want to use Interactive Queries to find
> the
> > count for "foo", I would need to know whether "foo" first arrived before
> or
> > after time T before I could find the correct partition to look up the
> data.
> > In this case, I don't think static partitioning is possible. Is this
> > use-case a non-goal of the KIP, or am I missing something?
> >
> > Colt McNealy
> > *Founder, LittleHorse.io*
> >
> >
> > On Thu, Oct 20, 2022 at 6:37 PM Sophie Blee-Goldman
> >  wrote:
> >
> > > Thanks for the responses guys! I'll get the easy stuff out of the way
> > > first:
> > >
> > > 1) Fixed the KIP so that StaticStreamPartitioner extends
> > StreamPartitioner
> > > 2) I totally agree with you Colt, the record value might have valuable
> > (no
> > > pun) information
> > > in it that is needed to compute the partition without breaking the
> static
> > > constraint. As in my
> > > own example earlier, maybe the userId is a field in the value and not
> the
> > > key itself. Actually
> > > it was that exact thought that made me do a U-turn on this but I forgot
> > to
> > > update the thread
> > > 3) Colt, I'm not  sure I follow what you're trying to say in that last
> > > paragraph, can you expand?
> > > 4) Lucas, it's a good question as to what kind of guard-rails we could
> > put
> > > up to enforce or even
> > > detect a violation of static partitioning. Most likely Streams would
> need
> > > to track every key to
> > > partition mapping in an internal state store, but we have no guarantee
> > the
> > > key space is bounded
> > > and the store wouldn't grow out of control. Mostly however I imagine
> > users
> > > would be frustrated
> > > to find out there's a secret, extra state store taking up space when
> you
> > > enable autoscaling, and
> > > it's not even to provide functionality but just to make sure users
> aren't
> > > doing something wrong.
> > >
> > > I wish I had a better idea, but sadly I think the only practical
> solution
> > > here is to try and make this
> > > condition as clear and obvious and easy to understand as possible,
> > perhaps
> 

Re: [ANNOUNCE] New committer: Deng Ziming

2022-10-10 Thread Bill Bejeck
Congrats Ziming!

Regards,
Bill

On Mon, Oct 10, 2022 at 5:32 PM Ismael Juma  wrote:

> Congratulations Ziming!
>
> Ismael
>
> On Mon, Oct 10, 2022 at 9:30 AM Jason Gustafson  >
> wrote:
>
> > Hi All
> >
> > The PMC for Apache Kafka has invited Deng Ziming to become a committer,
> > and we are excited to announce that he has accepted!
> >
> > Ziming has been contributing to Kafka for about three years. He has
> > authored
> > more than 100 patches and helped to review nearly as many. In particular,
> > he made significant contributions to the KRaft project which had a big
> part
> > in reaching our production readiness goal in the 3.3 release:
> > https://blogs.apache.org/kafka/entry/what-rsquo-s-new-in.
> >
> > Please join me in congratulating Ziming! Thanks for all of your
> > contributions!
> >
> > -- Jason, on behalf of the Apache Kafka PMC
> >
>


Re: [VOTE] 3.3.1 RC0

2022-09-30 Thread Bill Bejeck
Hi,

I did the following to validate the release:

   1. Validated all checksums, signatures
   2. Built from source and ran all the unit tests
   3. Ran the ZK and KRaft quickstart
   4. Ran the Raft single quorum test
   5. Ran the Kafka Streams quick start

+1(binding) pending successful system test run

Thanks,
Bill

On Fri, Sep 30, 2022 at 5:30 AM David Jacot 
wrote:

> Hey,
>
> I performed the following validations:
> * Verified all checksums and signatures.
> * Built from source and ran unit tests.
> * Ran the first quickstart steps for both ZK and KRaft.
> * Spotchecked the Javadocs.
>
> I am +1 (binding), assuming that the system tests look good.
>
> Thanks for running the release.
>
> Best,
> David
>
> On Fri, Sep 30, 2022 at 2:23 AM José Armando García Sancio
>  wrote:
> >
> > On Thu, Sep 29, 2022 at 2:39 PM José Armando García Sancio
> >  wrote:
> > > Please download, test and vote by Tuesday, October 4, 9am PT.
> >
> > The vote will be open for 72 hours. Please vote by Sunday, October 2nd,
> 3 PM PT.
> >
> > Thanks!
> > --
> > -José
>


Re: [VOTE] 3.3.0 RC2

2022-09-26 Thread Bill Bejeck
Hi Jose and David,

Thanks for running the release!
I did the following verification steps:
I performed the following validations:

   1.   Verified all checksums and signatures.
   2.   Built from source and ran unit tests.
   3.   Ran the first quickstart steps
  1. Zookeeper quick start
  2. KRaft quick start
  3. The raft test script
   4.  Spot checked the docs


I noticed the docs page is a little mal-formed, but this doesn't need to
block the release we can fix it separately.  Also, the quickstart page
still references 3.2, but this can be fixed on a followup docs PR.

+1(binding)

Thanks,
Bill

On Mon, Sep 26, 2022 at 12:01 PM David Jacot 
wrote:

> Thanks for running the release, José and David.
>
> I performed the following validations:
> * Verified all checksums and signatures.
> * Built from source and ran unit tests.
> * Ran the first quickstart steps for both ZK and KRaft.
> * Spotchecked the Javadocs.
>
> I have also noticed that the doc is malformed but we can fix this
> separately.
>
> I am +1 (binding), assuming that the system tests look good. It would
> be great if you could share them.
>
> Best,
> David
>
> On Mon, Sep 26, 2022 at 5:36 PM John Roesler  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 doc tree is only halfway collapsed, and
> there's a weird empty panel on the right).
> >
> > We can fix the docs site independent of this release, so I'm +1
> (binding).
> >
> > Thanks,
> > -John
> >
> > On Tue, Sep 20, 2022, at 18:17, David Arthur wrote:
> > > Hello Kafka users, developers and client-developers,
> > >
> > > This is the second release candidate for Apache Kafka 3.3.0. Many new
> > > features and bug fixes are included in this major release of Kafka. A
> > > significant number of the issues in this release are related to KRaft,
> > > which will be considered "production ready" as part of this release
> > > (KIP-833)
> > >
> > > KRaft improvements:
> > > * KIP-778: Online KRaft to KRaft Upgrades
> > > * KIP-833: Mark KRaft as Production Ready
> > > * KIP-835: Monitor Quorum health (many new KRaft metrics)
> > > * KIP-836: Expose voter lag via kafka-metadata-quorum.sh
> > > * KIP-841: Fenced replicas should not be allowed to join the ISR in
> KRaft
> > > * KIP-859: Add Metadata Log Processing Error Related Metrics
> > >
> > > Other major improvements include:
> > > * KIP-618: Exactly-Once Support for Source Connectors
> > > * KIP-831: Add metric for log recovery progress
> > > * KIP-827: Expose logdirs total and usable space via Kafka API
> > > * KIP-834: Add ability to Pause / Resume KafkaStreams Topologies
> > >
> > > The full release notes are available here:
> > >
> https://home.apache.org/~davidarthur/kafka-3.3.0-rc2/RELEASE_NOTES.html
> > >
> > > Please download, test and vote by Monday, Sep 26 at 5pm EDT
> > >
> > > Also, huge thanks to José for running the release so far. He has done
> > > the vast majority of the work to prepare this rather large release :)
> > >
> > > -
> > >
> > > Kafka's KEYS file containing PGP keys we use to sign the release:
> > > https://kafka.apache.org/KEYS
> > >
> > > * Release artifacts to be voted upon (source and binary):
> > > https://home.apache.org/~davidarthur/kafka-3.3.0-rc2/
> > >
> > > * Maven artifacts to be voted upon:
> > > https://repository.apache.org/content/groups/staging/org/apache/kafka/
> > >
> > > * Javadoc:
> https://home.apache.org/~davidarthur/kafka-3.3.0-rc2/javadoc/
> > >
> > > * Tag to be voted upon (off 3.3 branch) is the 3.3.0 tag:
> > > https://github.com/apache/kafka/releases/tag/3.3.0-rc2
> > >
> > > * Documentation:  https://kafka.apache.org/33/documentation.html
> > >
> > > * Protocol: https://kafka.apache.org/33/protocol.html
> > >
> > >
> > >
> > >
> > > Successful Jenkins builds to follow in a future update to this email.
> > >
> > >
> > > Thanks!
> > > David Arthur
>


Re: [VOTE] KIP-865: Support --bootstrap-server in kafka-streams-application-reset

2022-09-12 Thread Bill Bejeck
Thanks for the KIP!

+1(binding)

-Bill

On Mon, Sep 12, 2022 at 1:39 PM Николай Ижиков  wrote:

> Community, please, share your vote for this KIP.
>
> > 9 сент. 2022 г., в 19:55, Guozhang Wang  написал(а):
> >
> > +1. Thanks.
> >
> > Guozhang
> >
> > On Fri, Sep 9, 2022 at 9:52 AM Николай Ижиков 
> wrote:
> >
> >> Hello.
> >>
> >> I'd like to start a vote on KIP-865 which adds support of
> >> —bootstrap-server parameter in kafka-streams-application-reset tool
> >>
> >> Discuss Thread:
> >> https://lists.apache.org/thread/5c1plw7mgmzd4zzqh1w59cqopn8kv21c
> >> KIP:
> >>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-865%3A+Support+--bootstrap-server+in+kafka-streams-application-reset
> >> JIRA: https://issues.apache.org/jira/browse/KAFKA-12878
> >
> >
> >
> > --
> > -- Guozhang
>
>


Re: Hosting Kafka Videos on ASF YouTube channel

2022-09-12 Thread Bill Bejeck
Hi Joe

Thanks for that.  I'm working with our media team now, stay tuned, I'll get
back to you when I have them and the location for you to get access.

-Bill

On Wed, Sep 7, 2022 at 10:08 AM Joe Brockmeier  wrote:

> Hi Bill, all,
>
> Next steps would be to get the videos ready for posting + we can start
> uploading them. I'd need them in a central location I can do that
> from.
>
> On Wed, Aug 31, 2022 at 2:45 PM Bill Bejeck  wrote:
> >
> > This thread has been open for 22 days, so I will close the vote now.
> >
> > The question of hosting the four Kafka Streams videos passes:
> >
> > +1 votes
> > PMC Members:
> > * Mickael Maison
> > * John Roesler
> > * Bill Bejeck
> >
> > Vote thread:
> > https://www.mail-archive.com/dev@kafka.apache.org/msg126019.html
> >
> > Joe,
> > Provided this vote is sufficient, what are the next steps?
> >
> > Thanks,
> > Bill
> >
> > On Thu, Aug 25, 2022 at 12:48 PM John Roesler 
> wrote:
> >>
> >> Thanks all,
> >>
> >> I’m also +1 on the Kafka Streams videos.
> >>
> >> Thanks,
> >> John
> >>
> >> On Tue, Aug 9, 2022, at 03:54, Mickael Maison wrote:
> >> > Hi,
> >> >
> >> > I checked the four Streams videos
> >> > (https://kafka.apache.org/32/documentation/streams/), they are good
> >> > and don't mention any vendors.
> >> > +1 (binding) for these four videos
> >> >
> >> > For the last video (https://kafka.apache.org/intro and
> >> > https://kafka.apache.org/quickstart) we will have to wait till the
> >> > intro is edited.
> >> >
> >> > Thanks,
> >> > Mickael
> >> >
> >> >
> >> > On Mon, Aug 8, 2022 at 11:12 PM Joe Brockmeier 
> wrote:
> >> >>
> >> >> Repurpose away. Thanks!
> >> >>
> >> >> On Mon, Aug 8, 2022 at 4:55 PM Bill Bejeck 
> wrote:
> >> >> >
> >> >> > Hi Joe,
> >> >> >
> >> >> > Thanks that works for me. As for you watching the videos, they are
> about 10 minutes each, and you can watch them at 1.5 - 1.75 playback speed.
> >> >> >
> >> >> > If it's ok with you, I'm going to repurpose this thread as a
> voting thread for the videos.
> >> >> >
> >> >> > I watched the Kafka Streams videos on
> https://kafka.apache.org/32/documentation/streams/, and I can confirm
> they are vendor-neutral.
> >> >> > The other videos and logo that show up at the end are coming from
> YouTube, so once move the videos to the ASF channel, that should go away.
> >> >> >
> >> >> > +1(binding).
> >> >> >
> >> >> > Thanks,
> >> >> > Bill
> >> >> >
> >> >> >
> >> >> >
> >> >> > On Mon, Aug 8, 2022 at 9:46 AM Joe Brockmeier 
> wrote:
> >> >> >>
> >> >> >> If we can get a +1 from the PMC on each video that they're happy
> that
> >> >> >> the videos are vendor neutral I think we can do that. I'll also
> need
> >> >> >> to view them as well. I hope they're not long videos. :-)
> >> >> >>
> >> >> >> On Tue, Aug 2, 2022 at 3:38 PM Bill Bejeck 
> wrote:
> >> >> >> >
> >> >> >> > Hi Joe,
> >> >> >> >
> >> >> >> > Yes, that is correct.  Sorry, I should have mentioned that in
> the original email.  That is the only video where Tim says that.
> >> >> >> > The Kafka Streams videos do not mention Confluent.
> >> >> >> >
> >> >> >> > We're currently pursuing editing the video to remove the "from
> Confluent" part.
> >> >> >> > Note that the site also uses the same video on the "quickstart"
> page, so both places will be fixed when editing is completed.
> >> >> >> >
> >> >> >> > Can we pursue hosting the Kafka Streams videos for now, then
> revisit the "What is Apache Kafka?" when the editing is done?
> >> >> >> >
> >> >> >> > Thanks,
> >> >> >> > Bill
> >> >> >> >
> >> >> >> >
> >> >> >> > On Tue, Aug 2, 2022 at 3:12 PM Joe Brockmeier 
&

Re: [DISCUSSION] KIP-864: Support --bootstrap-server in kafka-streams-application-reset

2022-09-09 Thread Bill Bejeck
Hi Николай,

Thanks for the KIP; consistency across the tooling is important, so I'm
a +1 for this KIP.
I agree with Guozhang on voting right away.

-Bill

On Fri, Sep 9, 2022 at 12:05 PM Guozhang Wang  wrote:

> Hi, I think we can vote right away.
>
> Guozhang
>
> On Fri, Sep 9, 2022 at 2:24 AM Николай Ижиков  wrote:
>
> > Hello, Guozhang.
> >
> > Thanks for the feedback.
> > As this KIP very straightforward, is it worth to be voted right now?
> > Or should we wait more feedback?
> >
> > > 9 сент. 2022 г., в 08:11, Guozhang Wang 
> написал(а):
> > >
> > > Hello Николай,
> > >
> > > Thanks for writing the KIP, I think it's rather straightforward and
> > better
> > > to be consistent in tooling params. I'm +1.
> > >
> > > Guozhang
> > >
> > >
> > > On Mon, Sep 5, 2022 at 11:25 PM Николай Ижиков 
> > wrote:
> > >
> > >> Hello.
> > >>
> > >> Do we still want to make parameter names consistent in tools?
> > >> If yes, please, share your feedback on KIP.
> > >>
> > >>> 31 авг. 2022 г., в 11:50, Николай Ижиков 
> > >> написал(а):
> > >>>
> > >>> Hello.
> > >>>
> > >>> I would like to start discussion on small KIP [1]
> > >>> The goal of KIP is to add the same —boostrap-server parameter to
> > >> `kafka-streams-appliation-reset.sh` tool as other tools use.
> > >>> Please, share your feedback.
> > >>>
> > >>> [1]
> > >>
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-864%3A+Support+--bootstrap-server+in+kafka-streams-application-reset
> > >>>
> > >>
> > >>
> > >
> > > --
> > > -- Guozhang
> >
> >
>
> --
> -- Guozhang
>


Re: Hosting Kafka Videos on ASF YouTube channel

2022-08-31 Thread Bill Bejeck
This thread has been open for 22 days, so I will close the vote now.

The question of hosting the four Kafka Streams videos passes:

+1 votes
PMC Members:
* Mickael Maison
* John Roesler
* Bill Bejeck

Vote thread:
https://www.mail-archive.com/dev@kafka.apache.org/msg126019.html

Joe,
Provided this vote is sufficient, what are the next steps?

Thanks,
Bill

On Thu, Aug 25, 2022 at 12:48 PM John Roesler  wrote:

> Thanks all,
>
> I’m also +1 on the Kafka Streams videos.
>
> Thanks,
> John
>
> On Tue, Aug 9, 2022, at 03:54, Mickael Maison wrote:
> > Hi,
> >
> > I checked the four Streams videos
> > (https://kafka.apache.org/32/documentation/streams/), they are good
> > and don't mention any vendors.
> > +1 (binding) for these four videos
> >
> > For the last video (https://kafka.apache.org/intro and
> > https://kafka.apache.org/quickstart) we will have to wait till the
> > intro is edited.
> >
> > Thanks,
> > Mickael
> >
> >
> > On Mon, Aug 8, 2022 at 11:12 PM Joe Brockmeier  wrote:
> >>
> >> Repurpose away. Thanks!
> >>
> >> On Mon, Aug 8, 2022 at 4:55 PM Bill Bejeck  wrote:
> >> >
> >> > Hi Joe,
> >> >
> >> > Thanks that works for me. As for you watching the videos, they are
> about 10 minutes each, and you can watch them at 1.5 - 1.75 playback speed.
> >> >
> >> > If it's ok with you, I'm going to repurpose this thread as a voting
> thread for the videos.
> >> >
> >> > I watched the Kafka Streams videos on
> https://kafka.apache.org/32/documentation/streams/, and I can confirm
> they are vendor-neutral.
> >> > The other videos and logo that show up at the end are coming from
> YouTube, so once move the videos to the ASF channel, that should go away.
> >> >
> >> > +1(binding).
> >> >
> >> > Thanks,
> >> > Bill
> >> >
> >> >
> >> >
> >> > On Mon, Aug 8, 2022 at 9:46 AM Joe Brockmeier  wrote:
> >> >>
> >> >> If we can get a +1 from the PMC on each video that they're happy that
> >> >> the videos are vendor neutral I think we can do that. I'll also need
> >> >> to view them as well. I hope they're not long videos. :-)
> >> >>
> >> >> On Tue, Aug 2, 2022 at 3:38 PM Bill Bejeck 
> wrote:
> >> >> >
> >> >> > Hi Joe,
> >> >> >
> >> >> > Yes, that is correct.  Sorry, I should have mentioned that in the
> original email.  That is the only video where Tim says that.
> >> >> > The Kafka Streams videos do not mention Confluent.
> >> >> >
> >> >> > We're currently pursuing editing the video to remove the "from
> Confluent" part.
> >> >> > Note that the site also uses the same video on the "quickstart"
> page, so both places will be fixed when editing is completed.
> >> >> >
> >> >> > Can we pursue hosting the Kafka Streams videos for now, then
> revisit the "What is Apache Kafka?" when the editing is done?
> >> >> >
> >> >> > Thanks,
> >> >> > Bill
> >> >> >
> >> >> >
> >> >> > On Tue, Aug 2, 2022 at 3:12 PM Joe Brockmeier 
> wrote:
> >> >> >>
> >> >> >> Hi Bill,
> >> >> >>
> >> >> >> I'm not sure changing hosting would quite solve the problem. The
> first
> >> >> >> video I see on this page:
> >> >> >>
> >> >> >> https://kafka.apache.org/intro
> >> >> >>
> >> >> >> Starts with "Hi, I'm Bill Berglund from *Confluent*" rather than
> "Hi,
> >> >> >> I'm Bill from Apache Kafka" -- so moving to the ASF Youtube
> channel
> >> >> >> wouldn't completely solve the problem.
> >> >> >>
> >> >> >> On Tue, Aug 2, 2022 at 3:05 PM Bill Bejeck 
> wrote:
> >> >> >> >
> >> >> >> > Hi,
> >> >> >> >
> >> >> >> > I am an Apache Kafka® committer and PMC member, and I'm working
> on our site to address some issues around our embedded videos and branding.
> >> >> >> >
> >> >> >> > The Kafka site has six embedded videos:
> https://kafka.apache.org/intro, https://kafka.apache.org/quickstart, and
> four videos on https://kafka.apache.org/32/documentation/streams/.
> >> >> >> >
> >> >> >> > The videos are hosted on the Confluent YouTube channel, so the
> branding on the video is from Confluent.  Since it's coming from YouTube,
> there's no way to change it.
> >> >> >> >
> >> >> >> > Would it be possible to upload these videos to the Apache
> Foundation YouTube channel (
> https://www.youtube.com/c/TheApacheFoundation/featured)?  Doing this
> would automatically change the branding to Apache.
> >> >> >> >
> >> >> >> > Thanks, and I look forward to working with you on this matter.
> >> >> >> >
> >> >> >> > Bill Bejeck
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> Joe Brockmeier
> >> >> >> Vice President Marketing & Publicity
> >> >> >> j...@apache.org
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> Joe Brockmeier
> >> >> Vice President Marketing & Publicity
> >> >> j...@apache.org
> >>
> >>
> >>
> >> --
> >> Joe Brockmeier
> >> Vice President Marketing & Publicity
> >> j...@apache.org
>


Re: Hosting Kafka Videos on ASF YouTube channel

2022-08-08 Thread Bill Bejeck
Hi Joe,

Thanks that works for me. As for you watching the videos, they are about 10
minutes each, and you can watch them at 1.5 - 1.75 playback speed.

If it's ok with you, I'm going to repurpose this thread as a voting thread
for the videos.

I watched the Kafka Streams videos on
https://kafka.apache.org/32/documentation/streams/, and I can confirm they
are vendor-neutral.
The other videos and logo that show up at the end are coming from YouTube,
so once move the videos to the ASF channel, that should go away.

+1(binding).

Thanks,
Bill



On Mon, Aug 8, 2022 at 9:46 AM Joe Brockmeier  wrote:

> If we can get a +1 from the PMC on each video that they're happy that
> the videos are vendor neutral I think we can do that. I'll also need
> to view them as well. I hope they're not long videos. :-)
>
> On Tue, Aug 2, 2022 at 3:38 PM Bill Bejeck  wrote:
> >
> > Hi Joe,
> >
> > Yes, that is correct.  Sorry, I should have mentioned that in the
> original email.  That is the only video where Tim says that.
> > The Kafka Streams videos do not mention Confluent.
> >
> > We're currently pursuing editing the video to remove the "from
> Confluent" part.
> > Note that the site also uses the same video on the "quickstart" page, so
> both places will be fixed when editing is completed.
> >
> > Can we pursue hosting the Kafka Streams videos for now, then revisit the
> "What is Apache Kafka?" when the editing is done?
> >
> > Thanks,
> > Bill
> >
> >
> > On Tue, Aug 2, 2022 at 3:12 PM Joe Brockmeier  wrote:
> >>
> >> Hi Bill,
> >>
> >> I'm not sure changing hosting would quite solve the problem. The first
> >> video I see on this page:
> >>
> >> https://kafka.apache.org/intro
> >>
> >> Starts with "Hi, I'm Bill Berglund from *Confluent*" rather than "Hi,
> >> I'm Bill from Apache Kafka" -- so moving to the ASF Youtube channel
> >> wouldn't completely solve the problem.
> >>
> >> On Tue, Aug 2, 2022 at 3:05 PM Bill Bejeck  wrote:
> >> >
> >> > Hi,
> >> >
> >> > I am an Apache Kafka® committer and PMC member, and I'm working on
> our site to address some issues around our embedded videos and branding.
> >> >
> >> > The Kafka site has six embedded videos:
> https://kafka.apache.org/intro, https://kafka.apache.org/quickstart, and
> four videos on https://kafka.apache.org/32/documentation/streams/.
> >> >
> >> > The videos are hosted on the Confluent YouTube channel, so the
> branding on the video is from Confluent.  Since it's coming from YouTube,
> there's no way to change it.
> >> >
> >> > Would it be possible to upload these videos to the Apache Foundation
> YouTube channel (https://www.youtube.com/c/TheApacheFoundation/featured)?
> Doing this would automatically change the branding to Apache.
> >> >
> >> > Thanks, and I look forward to working with you on this matter.
> >> >
> >> > Bill Bejeck
> >>
> >>
> >>
> >> --
> >> Joe Brockmeier
> >> Vice President Marketing & Publicity
> >> j...@apache.org
>
>
>
> --
> Joe Brockmeier
> Vice President Marketing & Publicity
> j...@apache.org
>


Re: Hosting Kafka Videos on ASF YouTube channel

2022-08-02 Thread Bill Bejeck
Hi Joe,

Yes, that is correct.  Sorry, I should have mentioned that in the original
email.  That is the only video where Tim says that.
The Kafka Streams videos do not mention Confluent.

We're currently pursuing editing the video to remove the "from Confluent"
part.
Note that the site also uses the same video on the "quickstart" page, so
both places will be fixed when editing is completed.

Can we pursue hosting the Kafka Streams videos for now, then revisit the
"What is Apache Kafka?" when the editing is done?

Thanks,
Bill


On Tue, Aug 2, 2022 at 3:12 PM Joe Brockmeier  wrote:

> Hi Bill,
>
> I'm not sure changing hosting would quite solve the problem. The first
> video I see on this page:
>
> https://kafka.apache.org/intro
>
> Starts with "Hi, I'm Bill Berglund from *Confluent*" rather than "Hi,
> I'm Bill from Apache Kafka" -- so moving to the ASF Youtube channel
> wouldn't completely solve the problem.
>
> On Tue, Aug 2, 2022 at 3:05 PM Bill Bejeck  wrote:
> >
> > Hi,
> >
> > I am an Apache Kafka® committer and PMC member, and I'm working on our
> site to address some issues around our embedded videos and branding.
> >
> > The Kafka site has six embedded videos:  https://kafka.apache.org/intro,
> https://kafka.apache.org/quickstart, and four videos on
> https://kafka.apache.org/32/documentation/streams/.
> >
> > The videos are hosted on the Confluent YouTube channel, so the branding
> on the video is from Confluent.  Since it's coming from YouTube, there's no
> way to change it.
> >
> > Would it be possible to upload these videos to the Apache Foundation
> YouTube channel (https://www.youtube.com/c/TheApacheFoundation/featured)?
> Doing this would automatically change the branding to Apache.
> >
> > Thanks, and I look forward to working with you on this matter.
> >
> > Bill Bejeck
>
>
>
> --
> Joe Brockmeier
> Vice President Marketing & Publicity
> j...@apache.org
>


Hosting Kafka Videos on ASF YouTube channel

2022-08-02 Thread Bill Bejeck
Hi,

I am an Apache Kafka® committer and PMC member, and I'm working on our site
to address some issues around our embedded videos and branding.

The Kafka site has six embedded videos:  https://kafka.apache.org/intro,
https://kafka.apache.org/quickstart, and four videos on
https://kafka.apache.org/32/documentation/streams/.

The videos are hosted on the Confluent YouTube channel, so the branding on
the video is from Confluent.  Since it's coming from YouTube, there's no
way to change it.

Would it be possible to upload these videos to the Apache Foundation
YouTube channel (https://www.youtube.com/c/TheApacheFoundation/featured)
<https://www.youtube.com/c/TheApacheFoundation/featured),>?  Doing this would
automatically change the branding to Apache.

Thanks, and I look forward to working with you on this matter.

Bill Bejeck


Re: [ANNOUNCE] Apache Kafka 3.2.1

2022-08-02 Thread Bill Bejeck
Thanks for running the release David!

-Bill

On Tue, Aug 2, 2022 at 4:34 AM Mickael Maison 
wrote:

> Thanks David for driving this release!
>
> On Tue, Aug 2, 2022 at 1:46 AM David Arthur 
> wrote:
> >
> > The Apache Kafka community is pleased to announce the release for
> > Apache Kafka 3.2.1
> >
> > This is a bugfix release with several fixes since the release of
> > 3.2.0. A few of the major issues include:
> >
> > * KAFKA-14062 OAuth client token refresh fails with SASL extensions
> > * KAFKA-14079 Memory leak in connectors using errors.tolerance=all
> > * KAFKA-14024 Cooperative rebalance regression causing clients to get
> stuck
> >
> >
> > All of the changes in this release can be found in the release notes:
> >
> > https://www.apache.org/dist/kafka/3.2.1/RELEASE_NOTES.html
> >
> >
> > You can download the source and binary release (Scala 2.12 and 2.13)
> from:
> >
> > https://kafka.apache.org/downloads#3.2.1
> >
> >
> ---
> >
> >
> > Apache Kafka is a distributed streaming platform with four core APIs:
> >
> > ** The Producer API allows an application to publish a stream of
> > records to one or more Kafka topics.
> >
> > ** The Consumer API allows an application to subscribe to one or more
> > topics and process the stream of records produced to them.
> >
> > ** The Streams API allows an application to act as a stream processor,
> > consuming an input stream from one or more topics and producing an
> > output stream to one or more output topics, effectively transforming
> > the input streams to output streams.
> >
> > ** The Connector API allows building and running reusable producers or
> > consumers that connect Kafka topics to existing applications or data
> > systems. For example, a connector to a relational database might
> > capture every change to a table.
> >
> >
> > With these APIs, Kafka can be used for two broad classes of application:
> >
> > ** Building real-time streaming data pipelines that reliably get data
> > between systems or applications.
> >
> > ** Building real-time streaming applications that transform or react
> > to the streams of data.
> >
> >
> > Apache Kafka is in use at large and small companies worldwide,
> > including Capital One, Goldman Sachs, ING, LinkedIn, Netflix,
> > Pinterest, Rabobank, Target, The New York Times, Uber, Yelp, and
> > Zalando, among others.
> >
> > A big thank you for the following 19 contributors to this release!
> >
> > Akhilesh Chaganti, Bruno Cadonna, Christopher L. Shannon, David
> > Arthur, Divij Vaidya, Eugene Tolbakov, Guozhang Wang, Ismael Juma,
> > James Hughes, Jason Gustafson, Kirk True, Lucas Bradstreet, Luke Chen,
> > Nicolas Guyomar, Niket Goel, Okada Haruki, Shawn Wang, Viktor
> > Somogyi-Vass, Walker Carlson
> >
> > We welcome your help and feedback. For more information on how to
> > report problems, and to get involved, visit the project website at
> > https://kafka.apache.org/
> >
> >
> > Thank you!
> >
> > Regards,
> > David Arthur
>


Re: [ANNOUNCE] New Kafka PMC Member: A. Sophie Blee-Goldman

2022-08-02 Thread Bill Bejeck
Congrats Sophie!

-Bill

On Tue, Aug 2, 2022 at 7:12 AM Tom Bentley  wrote:

> Congratulations Sophie!
>
> On Tue, 2 Aug 2022 at 11:54, Robin Moffatt 
> wrote:
>
> > Congrats Sophie, great news!
> >
> >
> > --
> >
> > Robin Moffatt | Principal Developer Advocate | ro...@confluent.io |
> @rmoff
> >
> >
> > On Tue, 2 Aug 2022 at 00:42, Guozhang Wang  wrote:
> >
> > > Hi everyone,
> > >
> > > I'd like to introduce our new Kafka PMC member, Sophie. She has been a
> > > committer since Oct. 2020 and has been contributing to the community
> > > consistently, especially around Kafka Streams and Kafka java consumer.
> > She
> > > has also presented about Kafka Streams at Kafka Summit London this
> year.
> > It
> > > is my pleasure to announce that Sophie agreed to join the Kafka PMC.
> > >
> > > Congratulations, Sophie!
> > >
> > > -- Guozhang Wang, on behalf of Apache Kafka PMC
> > >
> >
>


Re: [VOTE] 3.2.1 RC3

2022-07-27 Thread Bill Bejeck
Hi David,

Thanks for running the release!

I did the following steps:

   - Validated all signatures and checksums
   - Built from source
   - Ran all the unit tests
   - I spot-checked the doc.  I did notice the same version number as
   Randal - but I expect that will get fixed when the docs are updated with
   the release.

+1(binding)

Thanks,
Bill

On Tue, Jul 26, 2022 at 5:56 PM Matthew Benedict de Detrich
 wrote:

> Thanks for the RC,
>
> I ran the full (unit + integration) tests using Scala 2.12 and 2.13 across
> OpenJDK (Linux) 11 and 17 and all tests passed apart from a single one
> which is documented at https://issues.apache.org/jira/browse/KAFKA-13514
>
> +1 (non binding)
>
>
>
> On Fri, Jul 22, 2022 at 3:15 AM David Arthur 
> wrote:
>
> > Hello Kafka users, developers and client-developers,
> >
> > This is the first release candidate of Apache Kafka 3.2.1.
> >
> > This is a bugfix release with several fixes since the release of 3.2.0. A
> > few of the major issues include:
> >
> > * KAFKA-14062 OAuth client token refresh fails with SASL extensions
> > * KAFKA-14079 Memory leak in connectors using errors.tolerance=all
> > * KAFKA-14024 Cooperative rebalance regression causing clients to get
> stuck
> >
> >
> > Release notes for the 3.2.1 release:
> > https://home.apache.org/~davidarthur/kafka-3.2.1-rc3/RELEASE_NOTES.html
> >
> >
> >
> >  Please download, test and vote by Wednesday July 27, 2022 at 17:00
> PT.
> > 
> > Kafka's KEYS file containing PGP keys we use to sign the release:
> > https://kafka.apache.org/KEYS
> >
> > Release artifacts to be voted upon (source and binary):
> > https://home.apache.org/~davidarthur/kafka-3.2.1-rc3/
> >
> > Maven artifacts to be voted upon:
> > https://repository.apache.org/content/groups/staging/org/apache/kafka/
> >
> > Javadoc: https://home.apache.org/~davidarthur/kafka-3.2.1-rc3/javadoc/
> >
> > Tag to be voted upon (off 3.2 branch) is the 3.2.1 tag:
> > https://github.com/apache/kafka/releases/tag/3.2.1-rc3
> >
> > Documentation: https://kafka.apache.org/32/documentation.html
> >
> > Protocol: https://kafka.apache.org/32/protocol.html
> >
> >
> > The past few builds have had flaky test failures. I will update this
> thread
> > with passing build links soon.
> >
> > Unit/Integration test job:
> > https://ci-builds.apache.org/job/Kafka/job/kafka/job/3.2/
> > System test job:
> > https://jenkins.confluent.io/job/system-test-kafka/job/3.2/
> >
> >
> > Thanks!
> > David Arthur
> >
>
>
> --
>
> Matthew de Detrich
>
> *Aiven Deutschland GmbH*
>
> Immanuelkirchstraße 26, 10405 Berlin
>
> Amtsgericht Charlottenburg, HRB 209739 B
>
> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
>
> *m:* +491603708037
>
> *w:* aiven.io *e:* matthew.dedetr...@aiven.io
>


Re: [ANNOUNCE] New Committer: Chris Egerton

2022-07-25 Thread Bill Bejeck
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!
> >
> >
> > --
> >
> > Robin Moffatt | Principal Developer Advocate | ro...@confluent.io |
> @rmoff
> >
> >
> > On Mon, 25 Jul 2022 at 17:26, Mickael Maison 
> wrote:
> >
> > > Hi all,
> > >
> > > The PMC for Apache Kafka has invited Chris Egerton as a committer, and
> > > we are excited to announce that he accepted!
> > >
> > > Chris has been contributing to Kafka since 2017. He has made over 80
> > > commits mostly around Kafka Connect. His most notable contributions
> > > include KIP-507: Securing Internal Connect REST Endpoints and KIP-618:
> > > Exactly-Once Support for Source Connectors.
> > >
> > > He has been an active participant in discussions and reviews on the
> > > mailing lists and on Github.
> > >
> > > Thanks for all of your contributions Chris. Congratulations!
> > >
> > > -- Mickael, on behalf of the Apache Kafka PMC
> > >
> >
>


Re: [DISCUSS] KIP-854 Separate configuration for producer ID expiry

2022-07-25 Thread Bill Bejeck
Hi Justine,

I just took another look at the KIP, and I realize my question/suggestion
about default values has already been addressed in the `Compatibility`
section.

I'm +1 on the KIP.

-Bill

On Thu, Jul 21, 2022 at 6:20 PM Bill Bejeck  wrote:

> Hi Justine,
>
> Thanks for the well written KIP, this looks like it will be a useful
> addition.
>
> Overall the KIP looks good to me, I have one question/comment.
>
> You mentioned that setting the `producer.id.expiration.ms` less than the
> delivery timeout could lead to duplicates, which makes sense.  To help
> avoid this situation, do we want to consider a default value that is the
> same as the delivery timeout?
>
> Thanks again for the KIP.
>
> Bill
>
> On Thu, Jul 21, 2022 at 4:54 PM Justine Olshan
>  wrote:
>
>> Hey all!
>>
>> I'd like to start a discussion on my proposal to separate time-based
>> producer ID expiration from transactional ID expiration by introducing a
>> new configuration.
>>
>> The KIP Is pretty small and simple, but will be helpful in controlling
>> memory usage in brokers -- especially now that by default producers are
>> idempotent and create producer ID state.
>>
>> Please take a look and leave any comments you may have!
>>
>> KIP:
>>
>> https://cwiki.apache.org/confluence/display/KAFKA/KIP-854+Separate+configuration+for+producer+ID+expiry
>> JIRA: https://issues.apache.org/jira/browse/KAFKA-14097
>>
>> Thanks!
>> Justine
>>
>


Re: [DISCUSS] Website changes required for Apache projects

2022-07-22 Thread Bill Bejeck
Hi Divij,

After thinking about the embedded videos some more I think it's probably
best for now to go with option 1 you presented above (text links to the
videos).
I will do a follow on PR for option #2 - creating an image placeholder that
will trigger the video once clicked.

Thanks again for driving this update effort.

-Bill

On Thu, Jul 21, 2022 at 5:25 PM Bill Bejeck  wrote:

> Hi All,
>
> I've filed an issue with INFRA (
> https://issues.apache.org/jira/browse/INFRA-23499) to ask about uploading
> the videos to the ASF YouTube channel, which would resolve the branding
> issue.
>
> Thanks,
> Bill
>
> On Thu, Jul 21, 2022 at 1:43 PM Bill Bejeck  wrote:
>
>> Hi Divij,
>>
>> First of all, let me say thanks for taking up this task.
>>
>> We seem to have two options:
>>> 1. Replace videos on the website with links to the videos OR
>>> 2. Take a placeholder image and use JS to trigger playback after the user
>>> clicks.
>>>
>>> I would suggest going with option#1 right now due to time constraints and
>>> create a ticket to do (more user friendly) option#2 in the future.* What
>>> do
>>> you think?*
>>>
>>
>> I'm inclined to go with option #2.
>>
>> But taking a look at the https://apache.org/ site, there's an embedded
>> video directly on the page, not an image or a link.
>>
>> So I'm wondering, since the video doesn't start playing right away and
>> requires a user to click to start it, that the "click image to start"
>> requirement is satisfied,
>>
>> as it aligns with what we see now on the Apache® Software Foundation page.
>>
>>
>> Regarding the branding, that's not in the video file itself but comes
>> from YouTube and the video's channel.
>>
>> I propose that we host the video on the Apache YouTube
>> <https://www.youtube.com/c/TheApacheFoundation/featured> channel, and
>> that would take care of the branding issue.
>>
>>
>> What do you think?
>>
>>
>> On Thu, Jul 21, 2022 at 4:19 AM Divij Vaidya 
>> wrote:
>>
>>> Thanks for chiming in with your opinions John/Mickael.
>>>
>>> The current set of videos are very helpful and removing them might be a
>>> disservice to our users. The most ideal solution would be to host the
>>> videos on Apache servers without any branding. Another less than ideal
>>> solution would be to host a repository of links to educational content on
>>> our website.
>>>
>>> As for the next steps, I am going to do the following which would help us
>>> get answers on whether solution 1 or solution 2 is more feasible. Please
>>> let me know if you think we need to do something different here.
>>> 1. Reach out to ASF legal and ask what permissions/licence would we
>>> require
>>> from the video owners to host the videos ourselves.
>>> 2. Reach out to ASF community mailing list
>>> <
>>> https://www.apache.org/foundation/mailinglists.html#foundation-community
>>> >
>>> and ask how other communities are hosting educational content.
>>>
>>> There is still an open question about how we decide what content gets
>>> added
>>> and what doesn't. I would propose that the model should be the same as
>>> accepting code changes i.e. it goes through a community review requiring
>>> votes committers/PMC members.
>>>
>>> Regards,
>>> Divij Vaidya
>>>
>>>
>>>
>>> On Thu, Jul 21, 2022 at 3:57 AM John Roesler 
>>> wrote:
>>>
>>> > Hi all,
>>> >
>>> > Yes, thanks Divij for driving this!
>>> >
>>> > I tend to agree with Mickael about having vendor branding
>>> > front-and-center like that.
>>> >
>>> > On the other hand, I think the video itself is quite nice, and
>>> > it's a good thing to put in front of newcomers for a human
>>> > introduction to the project.
>>> >
>>> > I took a look at the video on those pages, and I'm not sure
>>> > if the videos themselves are branded. It looks like the branding
>>> > marks are markup that YouTube pastes on top of the video.
>>> >
>>> > Perhaps a solution is for Kafka to set up a channel of our own
>>> > and upload the videos there? Or maybe just host the videos
>>> > as static resources on our site directly? Approaches like those
>>> > are  probably good policy anyway, because then we
>>> > would contr

Re: [DISCUSS] KIP-854 Separate configuration for producer ID expiry

2022-07-21 Thread Bill Bejeck
Hi Justine,

Thanks for the well written KIP, this looks like it will be a useful
addition.

Overall the KIP looks good to me, I have one question/comment.

You mentioned that setting the `producer.id.expiration.ms` less than the
delivery timeout could lead to duplicates, which makes sense.  To help
avoid this situation, do we want to consider a default value that is the
same as the delivery timeout?

Thanks again for the KIP.

Bill

On Thu, Jul 21, 2022 at 4:54 PM Justine Olshan 
wrote:

> Hey all!
>
> I'd like to start a discussion on my proposal to separate time-based
> producer ID expiration from transactional ID expiration by introducing a
> new configuration.
>
> The KIP Is pretty small and simple, but will be helpful in controlling
> memory usage in brokers -- especially now that by default producers are
> idempotent and create producer ID state.
>
> Please take a look and leave any comments you may have!
>
> KIP:
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-854+Separate+configuration+for+producer+ID+expiry
> JIRA: https://issues.apache.org/jira/browse/KAFKA-14097
>
> Thanks!
> Justine
>


Re: [DISCUSS] Website changes required for Apache projects

2022-07-21 Thread Bill Bejeck
Hi All,

I've filed an issue with INFRA (
https://issues.apache.org/jira/browse/INFRA-23499) to ask about uploading
the videos to the ASF YouTube channel, which would resolve the branding
issue.

Thanks,
Bill

On Thu, Jul 21, 2022 at 1:43 PM Bill Bejeck  wrote:

> Hi Divij,
>
> First of all, let me say thanks for taking up this task.
>
> We seem to have two options:
>> 1. Replace videos on the website with links to the videos OR
>> 2. Take a placeholder image and use JS to trigger playback after the user
>> clicks.
>>
>> I would suggest going with option#1 right now due to time constraints and
>> create a ticket to do (more user friendly) option#2 in the future.* What
>> do
>> you think?*
>>
>
> I'm inclined to go with option #2.
>
> But taking a look at the https://apache.org/ site, there's an embedded
> video directly on the page, not an image or a link.
>
> So I'm wondering, since the video doesn't start playing right away and
> requires a user to click to start it, that the "click image to start"
> requirement is satisfied,
>
> as it aligns with what we see now on the Apache® Software Foundation page.
>
>
> Regarding the branding, that's not in the video file itself but comes from
> YouTube and the video's channel.
>
> I propose that we host the video on the Apache YouTube
> <https://www.youtube.com/c/TheApacheFoundation/featured> channel, and
> that would take care of the branding issue.
>
>
> What do you think?
>
>
> On Thu, Jul 21, 2022 at 4:19 AM Divij Vaidya 
> wrote:
>
>> Thanks for chiming in with your opinions John/Mickael.
>>
>> The current set of videos are very helpful and removing them might be a
>> disservice to our users. The most ideal solution would be to host the
>> videos on Apache servers without any branding. Another less than ideal
>> solution would be to host a repository of links to educational content on
>> our website.
>>
>> As for the next steps, I am going to do the following which would help us
>> get answers on whether solution 1 or solution 2 is more feasible. Please
>> let me know if you think we need to do something different here.
>> 1. Reach out to ASF legal and ask what permissions/licence would we
>> require
>> from the video owners to host the videos ourselves.
>> 2. Reach out to ASF community mailing list
>> <https://www.apache.org/foundation/mailinglists.html#foundation-community
>> >
>> and ask how other communities are hosting educational content.
>>
>> There is still an open question about how we decide what content gets
>> added
>> and what doesn't. I would propose that the model should be the same as
>> accepting code changes i.e. it goes through a community review requiring
>> votes committers/PMC members.
>>
>> Regards,
>> Divij Vaidya
>>
>>
>>
>> On Thu, Jul 21, 2022 at 3:57 AM John Roesler  wrote:
>>
>> > Hi all,
>> >
>> > Yes, thanks Divij for driving this!
>> >
>> > I tend to agree with Mickael about having vendor branding
>> > front-and-center like that.
>> >
>> > On the other hand, I think the video itself is quite nice, and
>> > it's a good thing to put in front of newcomers for a human
>> > introduction to the project.
>> >
>> > I took a look at the video on those pages, and I'm not sure
>> > if the videos themselves are branded. It looks like the branding
>> > marks are markup that YouTube pastes on top of the video.
>> >
>> > Perhaps a solution is for Kafka to set up a channel of our own
>> > and upload the videos there? Or maybe just host the videos
>> > as static resources on our site directly? Approaches like those
>> > are  probably good policy anyway, because then we
>> > would control the content that shows on our site.
>> >
>> > Thanks,
>> > John
>> >
>> > On Tue, Jul 19, 2022, at 11:48, Mickael Maison wrote:
>> > > Hi Divij,
>> > >
>> > > Thanks for leading this work.
>> > >
>> > > To be honest I'm not sure what to do with the videos. I'm actually
>> > > wondering if these videos should be on our website at all.
>> > >
>> > > My concerns is that they are branded. I find the content of the videos
>> > > very good but I don't think we should include branded content from
>> > > vendors on the Apache website, or at least not put it front and
>> > > center. This is literally the first thing we show to newcomers,
>> > > ther

Re: [DISCUSS] Website changes required for Apache projects

2022-07-21 Thread Bill Bejeck
Hi Divij,

First of all, let me say thanks for taking up this task.

We seem to have two options:
> 1. Replace videos on the website with links to the videos OR
> 2. Take a placeholder image and use JS to trigger playback after the user
> clicks.
>
> I would suggest going with option#1 right now due to time constraints and
> create a ticket to do (more user friendly) option#2 in the future.* What do
> you think?*
>

I'm inclined to go with option #2.

But taking a look at the https://apache.org/ site, there's an embedded
video directly on the page, not an image or a link.

So I'm wondering, since the video doesn't start playing right away and
requires a user to click to start it, that the "click image to start"
requirement is satisfied,

as it aligns with what we see now on the Apache® Software Foundation page.


Regarding the branding, that's not in the video file itself but comes from
YouTube and the video's channel.

I propose that we host the video on the Apache YouTube
 channel, and that
would take care of the branding issue.


What do you think?


On Thu, Jul 21, 2022 at 4:19 AM Divij Vaidya 
wrote:

> Thanks for chiming in with your opinions John/Mickael.
>
> The current set of videos are very helpful and removing them might be a
> disservice to our users. The most ideal solution would be to host the
> videos on Apache servers without any branding. Another less than ideal
> solution would be to host a repository of links to educational content on
> our website.
>
> As for the next steps, I am going to do the following which would help us
> get answers on whether solution 1 or solution 2 is more feasible. Please
> let me know if you think we need to do something different here.
> 1. Reach out to ASF legal and ask what permissions/licence would we require
> from the video owners to host the videos ourselves.
> 2. Reach out to ASF community mailing list
> 
> and ask how other communities are hosting educational content.
>
> There is still an open question about how we decide what content gets added
> and what doesn't. I would propose that the model should be the same as
> accepting code changes i.e. it goes through a community review requiring
> votes committers/PMC members.
>
> Regards,
> Divij Vaidya
>
>
>
> On Thu, Jul 21, 2022 at 3:57 AM John Roesler  wrote:
>
> > Hi all,
> >
> > Yes, thanks Divij for driving this!
> >
> > I tend to agree with Mickael about having vendor branding
> > front-and-center like that.
> >
> > On the other hand, I think the video itself is quite nice, and
> > it's a good thing to put in front of newcomers for a human
> > introduction to the project.
> >
> > I took a look at the video on those pages, and I'm not sure
> > if the videos themselves are branded. It looks like the branding
> > marks are markup that YouTube pastes on top of the video.
> >
> > Perhaps a solution is for Kafka to set up a channel of our own
> > and upload the videos there? Or maybe just host the videos
> > as static resources on our site directly? Approaches like those
> > are  probably good policy anyway, because then we
> > would control the content that shows on our site.
> >
> > Thanks,
> > John
> >
> > On Tue, Jul 19, 2022, at 11:48, Mickael Maison wrote:
> > > Hi Divij,
> > >
> > > Thanks for leading this work.
> > >
> > > To be honest I'm not sure what to do with the videos. I'm actually
> > > wondering if these videos should be on our website at all.
> > >
> > > My concerns is that they are branded. I find the content of the videos
> > > very good but I don't think we should include branded content from
> > > vendors on the Apache website, or at least not put it front and
> > > center. This is literally the first thing we show to newcomers,
> > > there's one at the top of both the Intro
> > > (https://kafka.apache.org/intro) and quickstart
> > > (https://kafka.apache.org/quickstart) pages.
> > >
> > > If tomorrow another vendor was to open a PR adding their videos to
> > > other pages, would we allow that? I searched the archives and couldn't
> > > find a discussion about adding branded third party content to the
> > > website. If I missed that, please share a link, otherwise I think this
> > > should be discussed.
> > >
> > > Thanks,
> > > Mickael
> > >
> > > On Tue, Jul 19, 2022 at 4:08 PM Divij Vaidya 
> > wrote:
> > >>
> > >> Hi community
> > >>
> > >> We have managed to fix most of the required items, thanks to Mickael
> > >> Maison, Luke Chen and Tom Bentley for quick reviews.
> > >>
> > >> But we still need to talk about item #5 i.e. the problem with
> "Embedded
> > >> videos don't have an image placeholder". Quoting from the ASF
> > guidelines:
> > >> *Can I embed videos (from YouTube, Vimeo, etc.)?*
> > >>
> > >> *Yes, you can embed videos on the website, but they should load only
> > after
> > >> the user actively wants them to load. Arrange this by 

Re: [VOTE] KIP-846: Processor-level Streams metrics for records/bytes Producedd

2022-05-30 Thread Bill Bejeck
+1 (binding)

-Bill

On Mon, May 30, 2022 at 4:49 AM Sagar  wrote:

> +1 (non-binding).
>
> Thanks!
> Sagar.
>
> On Mon, May 30, 2022 at 1:11 PM Bruno Cadonna  wrote:
>
> > +1 (binding)
> >
> > Thanks!
> > Bruno
> >
> > On 30.05.22 09:36, Sophie Blee-Goldman wrote:
> > > Hey all,
> > >
> > >   I'd like to kick off the voting thread for the KIP I proposed to add
> > > processor-level "bytes/records produced" metrics to Kafka Streams.
> > >
> > > Thanks!
> > >
> > > KIP-846: Task-level Streams metrics for bytes/records Produced
> > > <
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=211886093
> > >
> > >
> > > Cheers,
> > > Sophie
> > >
> >
>


Re: [DISCUSS] KIP-846: Task-level Streams metrics for bytes/records Produced

2022-05-30 Thread Bill Bejeck
Thanks for the KIP Sophie.

I'm in favor of this change as well. I don't have any comments in
addition to the ones already expressed.

-Bill

On Mon, May 30, 2022 at 4:55 AM Sagar  wrote:

> Hi Sophie,
>
> A very minor comment but you might want to remove this KIP template related
> information from the top of the KIP:
>
> *This page is meant as a template for writing a KIP
> <
> https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals
> >.
> To create a KIP choose Tools->Copy on this page and modify with your
> content and replace the heading with the next KIP number and a description
> of your issue. Replace anything in italics with your own description.*
>
>
> Thanks!
> Sagar.
>
> On Mon, May 30, 2022 at 1:04 PM Sophie Blee-Goldman
>  wrote:
>
> > >
> > > Why does the title of the KIP talk about task-level metrics, but the
> > > specified metrics are on processor-level?
> >
> >
> > Ah, my mistake -- it should indeed say "processor-level metrics". Thanks
> > for the catch Bruno, the title has been fixed.
> >
> > Since there don't seem to be any concerns I'll proceed with kicking off
> the
> > vote. Thanks all!
> >
> > On Mon, May 30, 2022 at 12:01 AM Bruno Cadonna 
> wrote:
> >
> > > Thanks for the KIP, Sophie!
> > >
> > > I am also in favor of this KIP!
> > >
> > > I have one minor question:
> > >
> > > Why does the title of the KIP talk about task-level metrics, but the
> > > specified metrics are on processor-level?
> > >
> > > For the rest, I am +1.
> > >
> > > Best,
> > > Bruno
> > >
> > > On 29.05.22 00:20, John Roesler wrote:
> > > > Thanks for the well motivated and documented KIP, Sophie! I’m in
> favor
> > > of this change.
> > > >
> > > > -John
> > > >
> > > > On Sat, May 28, 2022, at 06:42, Sophie Blee-Goldman wrote:
> > > >> Hey all,
> > > >>
> > > >> I'd like to propose a very small KIP to add two metrics that will
> help
> > > fill
> > > >> a gap in the derivable produced and consumed metrics. Please take a
> > look
> > > >> and reply here with any questions or concerns.
> > > >>
> > > >> KIP-846: Task-level Streams metrics for bytes/records Produced
> > > >> <
> > >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=211886093
> > > >
> > > >>
> > > >> Given the small nature of this I'm going to call for a vote soon,
> but
> > > >> please don't hesitate to raise anything you feel should be discussed
> > in
> > > >> more detail first.
> > > >>
> > > >> Thanks!
> > > >> Sophie
> > >
> >
>


Re: [VOTE] KIP-833: Mark KRaft as Production Ready

2022-05-24 Thread Bill Bejeck
Hi Colin,

Thanks for the KIP, I'm +1 (binding).

-Bill

On Tue, May 24, 2022 at 11:28 AM José Armando García Sancio
 wrote:

> Hi Colin,
>
> Thank you for the KIP. +1 (binding).
>
> --
> -José
>


Re: Request contributor access

2022-05-18 Thread Bill Bejeck
Hi Patrik,

Done.  Thanks for your interest in Apache Kafka!

-Bill

On Wed, May 18, 2022 at 10:27 AM Patrik Nagy 
wrote:

> Hi,
>
> I would like to get my JIRA account added to the list of contributors in
> order to be able to assign a JIRA ticket to me for fixing.
>
> My JIRA username is pnagy.
>
> Thanks in advance,
> Patrik
>


Re: Permission request to contribute

2022-05-18 Thread Bill Bejeck
Hi Alex,

You're all set on Jira and the Wiki now.
Thanks for your interest in Apache Kafka!

-Bill

On Wed, May 18, 2022 at 10:27 AM Alexandre Garnier 
wrote:

> Hi there!
> I'd like to request permission to contribute to Kafka.
>
> Wiki ID: zigarn
> Jira ID: zigarn
>
> Thanks,
> --
> Alex
>


Re: Permission request to contribute

2022-05-17 Thread Bill Bejeck
Hi Austin,

You're all set with Jira, but at the moment it seems like there's a
connection issue with the wiki and I haven't been able to add you there yet.
I'll try again later on.

Thanks for your interest in the Apache Kafka project!

-Bill

On Tue, May 17, 2022 at 5:18 PM Austin Heyne  wrote:

> I'd like to request permission to contribute to Kafka
>
> Wiki ID: aheyne
> Jira ID: aheyne
>
> Thanks,
> Austin
>
>
>


Re: [ANNOUNCE] Apache Kafka 3.2.0

2022-05-17 Thread Bill Bejeck
Thanks for running the release Bruno!

On Tue, May 17, 2022 at 12:02 PM Bruno Cadonna  wrote:

> The Apache Kafka community is pleased to announce the release for Apache
> Kafka 3.2.0
>
> * log4j 1.x is replaced with reload4j (KAFKA-9366)
> * StandardAuthorizer for KRaft (KIP-801)
> * Send a hint to the partition leader to recover the partition (KIP-704)
> * Top-level error code field in DescribeLogDirsResponse (KIP-784)
> * kafka-console-producer writes headers and null values (KIP-798 and
> KIP-810)
> * JoinGroupRequest and LeaveGroupRequest have a reason attached (KIP-800)
> * Static membership protocol lets the leader skip assignment (KIP-814)
> * Rack-aware standby task assignment in Kafka Streams (KIP-708)
> * Interactive Query v2 (KIP-796, KIP-805, and KIP-806)
> * Connect APIs list all connector plugins and retrieve their
> configuration (KIP-769)
> * TimestampConverter SMT supports different unix time precisions (KIP-808)
> * Connect source tasks handle producer exceptions (KIP-779)
>
> All of the changes in this release can be found in the release notes:
> https://www.apache.org/dist/kafka/3.2.0/RELEASE_NOTES.html
>
>
> You can download the source and binary release (Scala 2.12 and 2.13) from:
> https://kafka.apache.org/downloads#3.2.0
>
>
> ---
>
>
> Apache Kafka is a distributed streaming platform with four core APIs:
>
>
> ** The Producer API allows an application to publish a stream of records to
> one or more Kafka topics.
>
> ** The Consumer API allows an application to subscribe to one or more
> topics and process the stream of records produced to them.
>
> ** The Streams API allows an application to act as a stream processor,
> consuming an input stream from one or more topics and producing an
> output stream to one or more output topics, effectively transforming the
> input streams to output streams.
>
> ** The Connector API allows building and running reusable producers or
> consumers that connect Kafka topics to existing applications or data
> systems. For example, a connector to a relational database might
> capture every change to a table.
>
>
> With these APIs, Kafka can be used for two broad classes of application:
>
> ** Building real-time streaming data pipelines that reliably get data
> between systems or applications.
>
> ** Building real-time streaming applications that transform or react
> to the streams of data.
>
>
> Apache Kafka is in use at large and small companies worldwide, including
> Capital One, Goldman Sachs, ING, LinkedIn, Netflix, Pinterest, Rabobank,
> Target, The New York Times, Uber, Yelp, and Zalando, among others.
>
> A big thank you for the following 113 contributors to this release!
>
> A. Sophie Blee-Goldman, Adam Kotwasinski, Aleksandr Sorokoumov,
> Alexandre Garnier, Alok Nikhil, aSemy, Bounkong Khamphousone, bozhao12,
> Bruno Cadonna, Chang, Chia-Ping Tsai, Chris Egerton, Colin P. Mccabe,
> Colin Patrick McCabe, Cong Ding, David Arthur, David Jacot, David Mao,
> defhacks, dengziming, Ed B, Edwin, florin-akermann, GauthamM-official,
> GuoPhilipse, Guozhang Wang, Hao Li, Haoze Wu, Idan Kamara, Ismael Juma,
> Jason Gustafson, Jason Koch, Jeff Kim, jiangyuan, Joel Hamill, John
> Roesler, Jonathan Albrecht, Jorge Esteban Quilcate Otoya, Josep Prat,
> Joseph (Ting-Chou) Lin, José Armando García Sancio, Jules Ivanic, Julien
> Chanaud, Justin Lee, Justine Olshan, Kamal Chandraprakash, Kate Stanley,
> keashem, Kirk True, Knowles Atchison, Jr, Konstantine Karantasis,
> Kowshik Prakasam, kurtostfeld, Kvicii, Lee Dongjin, Levani Kokhreidze,
> lhunyady, Liam Clarke-Hutchinson, liym, loboya~, Lucas Bradstreet,
> Ludovic DEHON, Luizfrf3, Luke Chen, Marc Löhe, Matthew Wong, Matthias J.
> Sax, Michal T, Mickael Maison, Mike Lothian, mkandaswamy, Márton
> Sigmond, Nick Telford, Niket, Okada Haruki, Paolo Patierno, Patrick
> Stuedi, Philip Nee, Prateek Agarwal, prince-mahajan, Rajini Sivaram,
> Randall Hauch, Richard, RivenSun, Rob Leland, Ron Dagostino, Sayantanu
> Dey, Stanislav Vodetskyi, sunshujie1990, Tamara Skokova, Tim Patterson,
> Tolga H. Dur, Tom Bentley, Tomonari Yamashita, vamossagar12, Vicky
> Papavasileiou, Victoria Xia, Vijay Krishna, Vincent Jiang, Walker
> Carlson, wangyap, Wenhao Ji, Wenjun Ruan, Xiaobing Fang, Xiaoyue Xue,
> xuexiaoyue, Yang Yu, yasar03, Yu, Zhang Hongyi, zzccctv, 工业废水, 彭小漪
>
> We welcome your help and feedback. For more information on how to
> report problems, and to get involved, visit the project website at
> https://kafka.apache.org/
>
> Thank you!
>
>
> Regards,
>
> Bruno
>


Re: [DISCUSS] Apache Kafka 3.3.0 Release

2022-05-11 Thread Bill Bejeck
Thanks for volunteering to run the release José!

+1

-Bill

On Wed, May 11, 2022 at 3:26 AM Bruno Cadonna  wrote:

> Thanks José!
>
> +1
>
> Best,
> Bruno
>
> On 11.05.22 04:38, John Roesler wrote:
> > +1 from me! Thanks for volunteering, José.
> > -John
> >
> > On Tue, May 10, 2022, at 17:53, José Armando García Sancio wrote:
> >> Hi all,
> >>
> >> I would like to volunteer for the release of Apache Kafka 3.3.0. If
> >> people agree, I'll start working on the release plan and update this
> >> thread.
> >>
> >> Thanks,
> >> -José
>


Re: [VOTE] KIP-834: Pause / Resume KafkaStreams Topologies

2022-05-11 Thread Bill Bejeck
Thanks for the KIP!

+1 (binding)

-Bill

On Wed, May 11, 2022 at 9:36 AM Luke Chen  wrote:

> Hi Jim,
>
> I'm +1. (please add some note in KIP about the stream resetting tool can't
> be used in paused state)
> Thanks for the KIP!
>
> Luke
>
> On Wed, May 11, 2022 at 9:09 AM Guozhang Wang  wrote:
>
> > Thanks Jim. +1 from me.
> >
> > On Tue, May 10, 2022 at 4:51 PM Matthias J. Sax 
> wrote:
> >
> > > 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:
> > > >
> > > >> Thanks Jim,
> > > >>
> > > >> +1 (binding)
> > > >>
> > > >> Best,
> > > >> Bruno
> > > >>
> > > >> On 10.05.22 21:19, John Roesler wrote:
> > > >>> Thanks Jim,
> > > >>>
> > > >>> I’m +1 (binding)
> > > >>>
> > > >>> -John
> > > >>>
> > > >>> On Tue, May 10, 2022, at 14:05, Jim Hughes wrote:
> > >  Hi all,
> > > 
> > >  I'm asking for a vote on KIP-834:
> > > 
> > > >>
> > >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=211882832
> > > 
> > >  Thanks in advance!
> > > 
> > >  Jim
> > > >>
> > > >
> > >
> >
> >
> > --
> > -- Guozhang
> >
>


Re: [VOTE] KIP-832 Allow creating a producer/consumer using a producer/consumer

2022-05-10 Thread Bill Bejeck
Thanks for the KIP, François.

+1 (binding)

-Bill

On Tue, May 10, 2022 at 10:45 AM John Roesler  wrote:

> +1 (binding)
>
> Thanks, François!
> -John
>
> On Tue, May 10, 2022, at 03:09, Bruno Cadonna wrote:
> > Hi Francois,
> >
> > Thanks for the KIP whose link is:
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=211882578
> >
> > +1 (binding)
> >
> > Best,
> > Bruno
> >
> > On 09.05.22 23:23, François Rosière wrote:
> >>
> >>
>


Re: [DISCUSS] KIP-834: Pause / Resume KafkaStreams Topologies

2022-05-10 Thread Bill Bejeck
;>>> effects, users won't have to tolerate weird edge cases where a
> >> pause
> >>>>>> occurs
> >>>>>>>> after a processor sees a record, but before the result is sent to
> >>>> its
> >>>>>>>> outputs.
> >>>>>>>>
> >>>>>>>> 5. I noticed that you proposed not to add a PAUSED state, but I
> >>>> didn't
> >>>>>>>> follow
> >>>>>>>> the rationale. Adding a state seems beneficial for a number of
> >>>>> reasons:
> >>>>>>>> StreamThreads already use the thread state to determine whether
> >> to
> >>>>>> process
> >>>>>>>> or not, so avoiding a new State would just mean adding a separate
> >>>> flag
> >>>>>> to
> >>>>>>>> track
> >>>>>>>> and then checking your new flag in addition to the State in the
> >>>>> thread.
> >>>>>>>> Also,
> >>>>>>>> operating Streams applications is a non-trivial task, and users
> >> rely
> >>>>> on
> >>>>>>>> the State
> >>>>>>>> (and transitions) to understand Streams's behavior. Adding a
> >> PAUSED
> >>>>>> state
> >>>>>>>> is an elegant way to communicate to operators what is happening
> >> with
> >>>>> the
> >>>>>>>> application. Note that the person digging though logs and
> >> metrics,
> >>>>>> trying
> >>>>>>>> to understand why the application isn't doing anything is
> >> probably
> >>>> not
> >>>>>>>> going
> >>>>>>>> to be the same person who is calling pause() and resume(). Also,
> >> if
> >>>>> you
> >>>>>> add
> >>>>>>>> a state, you don't need `isPaused()`.
> >>>>>>>>
> >>>>>>>> 5b. If you buy the arguments to go ahead and commit as well as
> >> the
> >>>>>>>> argument to add a State, then I'd also suggest to follow the
> >>>> existing
> >>>>>>>> patterns
> >>>>>>>> for the shutdown states by also adding PAUSING. That
> >>>>>>>> way, you'll also expose a way to understand that Streams received
> >>>> the
> >>>>>>>> signal
> >>>>>>>> to pause, and that it's still processing and committing some
> >> records
> >>>>> in
> >>>>>>>> preparation to enter a PAUSED state. I'm not sure if a RESUMING
> >>>> state
> >>>>>> would
> >>>>>>>> also make sense.
> >>>>>>>>
> >>>>>>>
> >>>>>>> I hit a tricky bit when thinking through having a PAUSED
> >> state...  If
> >>>>> one
> >>>>>>> is using Named Topologies, and some of them are paused, what
> >> state is
> >>>>> the
> >>>>>>> Streams instance in?  If we can agree on that, things may become
> >>>>>> clear
> >>>>>>> I can see two quick ideas:
> >>>>>>>
> >>>>>>> 1.  The state is RUNNING and NamedTopologies have some other way
> >> to
> >>>>>>> indicate state.
> >>>>>>>
> >>>>>>> 2.  The state is something messy like PARTIALLY_PAUSED to reflect
> >>>> that
> >>>>>> the
> >>>>>>> instance has something interesting going on.
> >>>>>>>
> >>>>>>> When I poked at things initially, I did try out having different
> >>>>> states,
> >>>>>>> and I readily agree that a PAUSING state may make sense.
> >> (Especially
> >>>>> if
> >>>>>>> there's a need to run commits before transitioning all the way to
> >>>>>> PAUSED.)
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>> And that's all I have to say about that. I hope you don'

Re: [DISCUSS] KIP-834: Pause / Resume KafkaStreams Topologies

2022-05-06 Thread Bill Bejeck
Hi Jim,

Thanks for the KIP.  I have a couple of meta-questions as well:

1) Regarding pausing only a subset of running instances, I'm thinking there
may be a use case for pausing all of them.
   Would it make sense to also allow for pausing all instances by adding a
method `pauseAll()` or something similar?

2) Would pausing affect standby tasks?  For example, imagine there are 3
instances A, B, and C.
   A user elects to pause instance C only but it hosts the standby tasks
for A.
   Would the standby tasks on the paused application continue to read from
the changelog topic?

Thanks!
Bill


On Fri, May 6, 2022 at 2:44 PM Jim Hughes 
wrote:

> Hi Guozhang,
>
> Thanks for the feedback; responses inline below:
>
> On Fri, May 6, 2022 at 1:09 PM Guozhang Wang  wrote:
>
> > Hello Jim,
> >
> > Thanks for the proposed KIP. I have some meta questions about it:
> >
> > 1) Would an instance always pause/resume all of its current owned
> > topologies (i.e. the named topologies), or are there any scenarios where
> we
> > only want to pause/resume a subset of them?
> >
>
> An instance may wish to pause some of its named topologies.  I was unsure
> what to say about named topologies in the KIP since they seem to be an
> internal detail at the moment.
>
> I intend to add to KafkaStreamsNamedTopologyWrapper methods like:
> public void pauseNamedTopology(final String topologyToPause)
> public boolean isNamedTopologyPaused(final String topology)
> public void resumeNamedTopology(final String topologyToResume)
>
>
>
> > 2) From a user's perspective, do we want to always issue a `pause/resume`
> > to all the instances or not? For example, we can define the semantics of
> > the function as "you only need to call this function on any of the
> > application's instances, and all instances would then pause (via the
> > rebalance error codes)", or as "you would call this function for all the
> > instances of an application". Which one are you referring to?
> >
>
> My initial intent is that one would call this function on any instances of
> the application that one wishes to pause.  This should allow more control
> (in case one wanted to pause a portion of the instances).  On the other
> hand, this approach would put more work on the implementer to coordinate
> calling pause or resume across instances.
>
> If the other option is more suitable, happy to do that instead.
>
>
> > 3) With EOS, there's a transaction timeout which would determine how
> long a
> > transaction can stay idle before it's force-aborted on the broker side. I
> > think when a pause is issued, that means we'd need to immediately commit
> > the current transaction for EOS since we do not know how long we could
> > pause for. Is that right? If yes could you please clarify that in the doc
> > as well.
> >
>
> Good point.  My intent is for pause() to wait for the next iteration
> through `runOnce()` and then only skip over the processing for paused tasks
> in `taskManager.process(numIterations, time)`.
>
> Do commits live inside that call or do they live across/outside of it?  In
> the former case, I think there shouldn't be any issues with EOS.
> Otherwise, we may need to work through some details to get EOS right.
>
> Once we figure that out, I can update the KIP.
>
> Thanks,
>
> Jim
>
>
>
> >
> >
> > Guozhang
> >
> >
> >
> > On Wed, May 4, 2022 at 10:51 AM Jim Hughes  >
> > wrote:
> >
> > > Hi all,
> > >
> > > I have written up a KIP for adding the ability to pause and resume the
> > > processing of a topology in AK Streams.  The KIP is here:
> > >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=211882832
> > >
> > > Thanks in advance for your feedback!
> > >
> > > Cheers,
> > >
> > > Jim
> > >
> >
> >
> > --
> > -- Guozhang
> >
>


Re: [VOTE] 3.1.1 RC1

2022-05-04 Thread Bill Bejeck
Hi Tom,

Thanks for running the release!

I did the following checks:

   1. Validated all the checksum and signatures
   2. Built from source and ran the unit tests (Java 11)
   3. Ran the quickstart and the Kafka Streams demo (Java 11)
   4. Did a quick scan of the Javadoc and the documentation

I noticed the same issues as Mickael on the website, but otherwise, it
looks good.
+1 (binding)

Thanks,
Bill

On Tue, May 3, 2022 at 10:17 AM Jakub Scholz  wrote:

> +1 (non-binding). I used the Scala 2.13 binaries and staged Maven artifacts
> and ran various tests with them. Thanks for doing the release.
>
> Jakub
>
> On Fri, Apr 29, 2022 at 8:16 PM Mickael Maison 
> wrote:
>
> > Hi Tom,
> >
> > Thanks for running this release!
> >
> > I've done the following:
> > - Checked signatures and checksums
> > - Checked javadocs/maven artifacts
> > - Built from source and run all tests with Java 11
> > - Ran quickstart on Scala 2.13 artifact with Java 11
> >
> > It looks like the website has not been updated yet, I still only see
> > 3.1.0. When you'll add 3.1.1, let's make sure we mention reload4j in
> > the notable changes section.
> >
> > +1 (binding)
> >
> > Thanks,
> > Mickael
> >
> >
> >
> > On Fri, Apr 29, 2022 at 11:12 AM Tom Bentley 
> wrote:
> > >
> > > Hello Kafka users, developers and client-developers,
> > >
> > > This is the first candidate for release of Apache Kafka 3.1.1.
> > >
> > > Apache Kafka 3.1.1 is a bugfix release and 30 issues have been fixed
> > > since 3.1.0.
> > >
> > > Release notes for the 3.1.1 release:
> > > https://home.apache.org/~tombentley/kafka-3.1.1-rc1/RELEASE_NOTES.html
> > >
> > > *** Please download, test and vote by 09:00 UTC, Friday 6th May
> > >
> > > Kafka's KEYS file containing PGP keys we use to sign the release:
> > > https://kafka.apache.org/KEYS
> > >
> > > * Release artifacts to be voted upon (source and binary):
> > > https://home.apache.org/~tombentley/kafka-3.1.1-rc1/
> > >
> > > * Maven artifacts to be voted upon:
> > > https://repository.apache.org/content/groups/staging/org/apache/kafka/
> > >
> > > * Javadoc:
> > > https://home.apache.org/~tombentley/kafka-3.1.1-rc1/javadoc/
> > >
> > > * Tag to be voted upon (off 3.1 branch) is the 3.1.1 tag:
> > > https://github.com/apache/kafka/releases/tag/3.1.1-rc1
> > >
> > > * Documentation:
> > > https://kafka.apache.org/31/documentation.html
> > >
> > > * Protocol:
> > > https://kafka.apache.org/31/protocol.html
> > >
> > > * Successful Jenkins builds for the 3.1 branch:
> > > I will share a link one the build is complete.
> > >
> > > /**
> > >
> > > Thanks,
> > > Tom
> >
>


Re: [VOTE] 3.2.0 RC1

2022-05-03 Thread Bill Bejeck
Hi Bruno,

Thanks for running the 3.2 release!

I did the following:

   1. Built from source
   2. Ran the unit tests
   3. Validated keys and checksums
   4. Lightly checked the Javadoc
   5. Ran the quickstart and the Kafka Streams demo app
   6. Looked over the docs
   7. Ran the KRaft quickstart including the dump-log and metadata-shell

In the docs, I found that in section 1.3 on the main page the  `Kafka
Streams Demo` and `app development tutorial` still point to version 2.5.
But since this is a document-only change only we can directly update the
kafka-site repo.

+1(binding)

Thanks,
Bill


On Tue, May 3, 2022 at 10:07 AM Bruno Cadonna  wrote:

> Hello Kafka users, developers and client-developers,
>
> This is the second candidate for release of Apache Kafka 3.2.0.
>
> * log4j 1.x is replaced with reload4j (KAFKA-9366)
> * StandardAuthorizer for KRaft (KIP-801)
> * Send a hint to the partition leader to recover the partition (KIP-704)
> * Top-level error code field in DescribeLogDirsResponse (KIP-784)
> * kafka-console-producer writes headers and null values (KIP-798 and
> KIP-810)
> * JoinGroupRequest and LeaveGroupRequest have a reason attached (KIP-800)
> * Static membership protocol lets the leader skip assignment (KIP-814)
> * Rack-aware standby task assignment in Kafka Streams (KIP-708)
> * Interactive Query v2 (KIP-796, KIP-805, and KIP-806)
> * Connect APIs list all connector plugins and retrieve their
> configuration (KIP-769)
> * TimestampConverter SMT supports different unix time precisions (KIP-808)
> * Connect source tasks handle producer exceptions (KIP-779)
>
>
> Release notes for the 3.2.0 release:
> https://home.apache.org/~cadonna/kafka-3.2.0-rc1/RELEASE_NOTES.html
>
> *** Please download, test and vote by Tuesday, May 10th, 9am PDT
>
> Kafka's KEYS file containing PGP keys we use to sign the release:
> https://kafka.apache.org/KEYS
>
> * Release artifacts to be voted upon (source and binary):
> https://home.apache.org/~cadonna/kafka-3.2.0-rc1/
>
> * Maven artifacts to be voted upon:
> https://repository.apache.org/content/groups/staging/org/apache/kafka/
>
> * Javadoc:
> https://home.apache.org/~cadonna/kafka-3.2.0-rc1/javadoc/
>
> * Tag to be voted upon (off 3.2 branch) is the 3.2.0 tag:
> https://github.com/apache/kafka/releases/tag/3.2.0-rc1
>
> * Documentation:
> https://kafka.apache.org/32/documentation.html
>
> * Protocol:
> https://kafka.apache.org/32/protocol.html
>
> * Successful Jenkins builds for the 3.2 branch:
> Unit/integration tests: I'll share a link once the builds complete
> System tests:
> https://jenkins.confluent.io/job/system-test-kafka/job/3.2/30/
>
> /**
>
> Thanks,
> Bruno
>


Re: [VOTE] KIP-821: Connect Transforms support for nested structures

2022-04-21 Thread Bill Bejeck
Thanks for the KIP, Jorge.

This looks like a great addition to Kafka Connect.

+1(binding)

-Bill

On Thu, Apr 21, 2022 at 6:41 PM John Roesler  wrote:

> Thanks for the KIP, Jorge!
>
> I’ve just looked over the KIP, and it looks good to me.
>
> I’m +1 (binding)
>
> Thanks,
> John
>
> On Thu, Apr 21, 2022, at 09:10, Chris Egerton wrote:
> > This is a worthwhile addition to the SMTs that ship out of the box with
> > Kafka Connect. +1 non-binding
> >
> > On Thu, Apr 21, 2022, 09:51 Jorge Esteban Quilcate Otoya <
> > quilcate.jo...@gmail.com> wrote:
> >
> >> Hi all,
> >>
> >> I'd like to start a vote on KIP-821:
> >>
> >>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-821%3A+Connect+Transforms+support+for+nested+structures
> >>
> >> Thanks,
> >> Jorge
> >>
>


Re: JIRA Access

2022-04-06 Thread Bill Bejeck
You're all set now.

Regards,
Bill

On Wed, Apr 6, 2022 at 6:40 PM Rittika Adhikari 
wrote:

> Hello,
> I recently created a JIRA (KAFKA-13803) and opened a PR. Can I get JIRA
> access to assign myself to the issue?
> Thanks,
> Rittika
>
> --
>


Re: [VOTE] KIP-813 Shared State Stores

2022-04-05 Thread Bill Bejeck
Thanks for the KIP, Daan.

I've caught up on the discussion thread and I've gone over the KIP.  This
seems like a good addition to me.

+1 (binding)

Thanks,
Bill

On Fri, Apr 1, 2022 at 2:13 PM Matthias J. Sax  wrote:

> +1 (binding)
>
>
> On 4/1/22 6:47 AM, John Roesler wrote:
> > Thanks for the KIP, Daan!
> >
> > I’m +1 (binding)
> >
> > -John
> >
> > On Tue, Mar 29, 2022, at 06:01, Daan Gertis wrote:
> >> I would like to start a vote on this one:
> >>
> >>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-813%3A+Shareable+State+Stores
> >>
> >> Cheers,
> >> D.
>


Re: Developer access

2022-04-04 Thread Bill Bejeck
Hey Jim,

You're all set now on Jira and the Wiki.

-Bill



On Mon, Apr 4, 2022 at 4:52 PM Jim Hughes 
wrote:

> Hi all,
>
> Could I get access to the Kafka project in JIRA and on the Wiki?  My
> username for each is jhughes.
>
> Thanks in advance!
>
> Cheers,
>
> Jim
>


Re: [DISCUSS] KIP-0422: Add Record Footers

2022-04-01 Thread Bill Bejeck
Hi Matthias

This is a great idea, and I have one suggestion, can we name them record
footnotes?

Thanks,
Bill

On Fri, Apr 1, 2022 at 10:45 AM Matthias J. Sax  wrote:

> Hi,
>
> we added record header support to Kafka via KIP-82 many years ago. I
> think it's time to complement this feature with record footers.
>
> Looking forward to your feedback.
>
> https://tinyurl.com/43jubbaj
>
>
> -Matthias
>


Re: [VOTE] KIP-825: introduce a new API to control when aggregated results are produced

2022-03-24 Thread Bill Bejeck
Thanks for KIP Hao!

Glad to see we settled on option 1

+1(binding)

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 
> wrote:
> >
> >> Hi Hao,
> >>
> >> Actually, this is the VOTE thread. Do you use GMail? Sometimes it is a
> >> bit weird how it shows e-mails in threads.
> >>
> >> Anyways, thank you for the KIP and your patience!
> >>
> >> +1 (binding)
> >>
> >> Best,
> >> Bruno
> >>
> >> On 24.03.22 17:36, Hao Li wrote:
> >>> Thanks John and Guozhang. Didn't realize I used this discussion thread
> >> for
> >>> voting. Let me start a new thread for voting. Will fix the KIP.
> >>>
> >>> On Thu, Mar 24, 2022 at 9:28 AM Guozhang Wang 
> >> wrote:
> >>>
>  +1 (binding).
> 
>  Thanks Hao!
> 
> 
>  Guozhang
> 
>  On Thu, Mar 24, 2022 at 9:20 AM John Roesler 
> >> wrote:
> 
> > Thanks, Hao!
> >
> > I'm +1 (binding)
> >
> > -John
> >
> > On Wed, 2022-03-23 at 22:25 -0700, Hao Li wrote:
> >> Hi all,
> >>
> >> I'd like to start a vote on Kafka Streams KIP-825:
> >>
> >
> 
> >>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-825%3A+introduce+a+new+API+to+control+when+aggregated+results+are+produced
> >
> >
> 
>  --
>  -- Guozhang
> 
> >>>
> >>>
> >>
> >
> >
>


Re: Need permission to be contributor on Apache Kafka project

2022-03-16 Thread Bill Bejeck
Done.

Thanks for your interest in Apache Kafka.

-Bill

On Wed, Mar 16, 2022 at 6:03 PM Akhilesh Chaganti 
wrote:

> My username is akhileshchg.
>
> Thanks
> Akhilesh
>
>
> On Wed, Mar 16, 2022 at 2:46 PM Bill Bejeck  wrote:
>
> > Hi Akhilesh,
> >
> > Can you provide your Jira username? We can get you setup after that.
> >
> > Thanks,
> > Bill
> >
> > On Wed, Mar 16, 2022 at 4:38 PM Akhilesh Chaganti <
> akhilesh@gmail.com>
> > wrote:
> >
> > > Hi,
> > >
> > > I raised a bug (https://issues.apache.org/jira/browse/KAFKA-13749) for
> > > Apache Kafka. I want to submit a PR for this by becoming a contributor.
> > Can
> > > anyone help with getting the approval to assign the bug to me?
> > >
> > >
> > > Thanks
> > > Akhilesh
> > >
> >
>


  1   2   3   4   5   6   7   8   9   10   >