[jira] [Created] (KAFKA-12921) Upgrade ZSTD JNI from 1.4.9-1 to 1.5.0-1

David Christle created KAFKA-12921: -- Summary: Upgrade ZSTD JNI from 1.4.9-1 to 1.5.0-1 Key: KAFKA-12921 URL: https://issues.apache.org/jira/browse/KAFKA-12921 Project: Kafka Issue Type:

Re: [DISCUSS] KIP-726: Make the CooperativeStickyAssignor as the default assignor

Hi Konstantine, Thanks for your good comments. I've updated the KIP. Thank you. Luke On Wed, Jun 9, 2021 at 2:42 AM Konstantine Karantasis wrote: > Thanks for the KIP Luke. > > Looks good overall. Just a few minor suggestions: > > 1. How about replacing > "Note that this change will also

Re: [VOTE] KIP-750: Drop support for Java 8 in Kafka 4.0 (deprecate in 3.0)

This is great! Thanks for the KIP +1 (non-binding) On Tue, Jun 8, 2021 at 3:13 AM Bruno Cadonna wrote: > Hi Ismael, > > Thank you for the KIP! > > +1 (binding) > > Best, > Bruno > > On 08.06.21 10:11, Matthew de Detrich wrote: > > +1 (non binding) > > > > On Tue, Jun 8, 2021 at 4:48 AM Luke

Re: [DISCUSS] KIP-726: Make the CooperativeStickyAssignor as the default assignor

Hey Ryan, Yes, I believe any open bugs regarding the cooperative-sticky assignor should be considered as blockers to it being made the default, if not blockers to the release in general. I don't think they need to block the acceptance of this KIP, though, just possibly the implementation of it.

Re: [DISCUSS] KIP-747 Add support for basic aggregation APIs

Hi Alex, On Tue, Jun 8, 2021 at 2:44 PM Alexandre Brasil wrote: > > My point here is that, when we're only interested in a max/min numeric > value, it doesn't > matter when we have repeated values, since we'd be only forwarding the > number downstream, > so I could disregard when the Comparator

[jira] [Created] (KAFKA-12920) Consumer's cooperative sticky assignor need to clear generation / assignment data upon `onPartitionsLost`

Guozhang Wang created KAFKA-12920: - Summary: Consumer's cooperative sticky assignor need to clear generation / assignment data upon `onPartitionsLost` Key: KAFKA-12920 URL:

Re: [DISCUSS] KIP-747 Add support for basic aggregation APIs

Hi Mohan, > I like your idea though it is odd that min/max returns KTable instead of the > KTable (like in count), but mapValues should do the trick. My line of thought is that min/max could forward the min/max V associated with each K downstream. It'd not be the same as in count, where it'll

[jira] [Resolved] (KAFKA-12918) Watch-Free Animated 'America: The Motion Picture' Trailer 2021 Full Hd Download

[ https://issues.apache.org/jira/browse/KAFKA-12918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-12918. --- > Watch-Free Animated 'America: The Motion Picture' Trailer 2021 Full Hd > Download >

[jira] [Resolved] (KAFKA-12917) Watch Animated 'America: The Motion Picture' Trailer Full Hd Download-Now

[ https://issues.apache.org/jira/browse/KAFKA-12917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justine Olshan resolved KAFKA-12917. Resolution: Invalid > Watch Animated 'America: The Motion Picture' Trailer Full Hd

[jira] [Created] (KAFKA-12919) Watch-Free Animated 'America: The Motion Picture' Trailer 2021 Full Hd Download-Here

mushfiqur rahoman created KAFKA-12919: - Summary: Watch-Free Animated 'America: The Motion Picture' Trailer 2021 Full Hd Download-Here Key: KAFKA-12919 URL: https://issues.apache.org/jira/browse/KAFKA-12919

[jira] [Created] (KAFKA-12918) Watch-Free Animated 'America: The Motion Picture' Trailer 2021 Full Hd Download

mushfiqur rahoman created KAFKA-12918: - Summary: Watch-Free Animated 'America: The Motion Picture' Trailer 2021 Full Hd Download Key: KAFKA-12918 URL: https://issues.apache.org/jira/browse/KAFKA-12918

[jira] [Created] (KAFKA-12917) Watch Animated 'America: The Motion Picture' Trailer Full Hd Download-Now

mushfiqur rahoman created KAFKA-12917: - Summary: Watch Animated 'America: The Motion Picture' Trailer Full Hd Download-Now Key: KAFKA-12917 URL: https://issues.apache.org/jira/browse/KAFKA-12917

[DISCUSS] KIP-756: Move StreamsResetter tool outside of core

Hi everyone, Hope you are all well and safe. I'd like to propose the following KIP: https://cwiki.apache.org/confluence/display/KAFKA/KIP-756%3A+Move+StreamsResetter+tool+outside+of+core The goal is to move `StreamsResetter` tool outside of `core` module, and allow Kafka Streams users to access

Re: [DISCUSS] KIP-494 Connect REST Endpoint for Transformations (SMTs) and other Plugins

I'd like to keep the scope pretty tight -- getting SMTs is the real motivation here. If you think deprecation of the existing `/connector-plugins` endpoint necessitates expanding the scope to re-thinking a new top-level API and the implications for every subtype, then I think the right move here

[jira] [Resolved] (KAFKA-12912) fdgfdgfg

[ https://issues.apache.org/jira/browse/KAFKA-12912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-12912. - Resolution: Invalid > fdgfdgfg > > > Key: KAFKA-12912 >

Re: [DISCUSS] KIP-494 Connect REST Endpoint for Transformations (SMTs) and other Plugins

That's a valid point based on what the implementation is today. But this new endpoint aims to be an extension and a superset in terms of functionality of the existing `/connector-plugins` endpoint. This last discussion and the fact that the endpoint `/plugins/connector` that you suggest is almost

Re: [DISCUSS] KIP-726: Make the CooperativeStickyAssignor as the default assignor

Thanks for the KIP Luke. Looks good overall. Just a few minor suggestions: 1. How about replacing "Note that this change will also propagate to Connect." with -> "Note that this change will also automatically be inherited by sink connectors, like any other application that uses Kafka consumers,

[DISCUSS] KIP-755: Add new AUTO_CREATE ACL for auto topic creation

Hi Everyone, I'd like to propose KIP-755: Add new AUTO_CREATE ACL for auto topic creation The KIP can be found here: https://cwiki.apache.org/confluence/display/KAFKA/KIP-755%3A+Add+new+AUTO_CREATE+ACL+for+auto+topic+creation I submitted the following PR:

[jira] [Created] (KAFKA-12916) Add new AUTO_CREATE ACL for auto topic creation

Christopher L. Shannon created KAFKA-12916: -- Summary: Add new AUTO_CREATE ACL for auto topic creation Key: KAFKA-12916 URL: https://issues.apache.org/jira/browse/KAFKA-12916 Project: Kafka

Re: [DISCUSS] KIP-746: Revise KRaft Metadata Records

Hi, Colin, Thanks for the update KIP. 2. BrokerRegistrationChangeRecord: 2.1 Should the listeners field be named EndPoints to be consistent with RegisterBrokerRecord? 2.2 Does the listeners field indicate the addition/removal or the full current state of listeners? 2.3. Does

Re: [DISCUSS] KIP-724: Drop support for message formats v0 and v1

Hi, Ismael, Thanks for the KIP. Regarding log.record.version.force.upgrade: 1. Is that a topic level or a broker level config? The slight benefit of topic level is that it allows people to upgrade incrementally. The potential downside is the additional complexity associated with it. 2. When

[jira] [Created] (KAFKA-12915) Online TV Channel

mushfiqur rahoman created KAFKA-12915: - Summary: Online TV Channel Key: KAFKA-12915 URL: https://issues.apache.org/jira/browse/KAFKA-12915 Project: Kafka Issue Type: Bug

Build failed in Jenkins: Kafka » Kafka Branch Builder » 2.8 #30

See Changes: -- [...truncated 463627 lines...] [2021-06-08T15:51:16.260Z] > Task :metadata:compileJava UP-TO-DATE [2021-06-08T15:51:16.260Z] > Task :metadata:classes

Build failed in Jenkins: Kafka » Kafka Branch Builder » trunk #206

See Changes: -- [...truncated 470697 lines...] [2021-06-08T15:50:17.974Z] TopicCommandIntegrationTest > testCreateWithDefaultPartitions() PASSED [2021-06-08T15:50:17.974Z]

[jira] [Created] (KAFKA-12914) StreamSourceNode.toString() throws with StreamsBuilder.stream(Pattern) ctor

Will Bartlett created KAFKA-12914: - Summary: StreamSourceNode.toString() throws with StreamsBuilder.stream(Pattern) ctor Key: KAFKA-12914 URL: https://issues.apache.org/jira/browse/KAFKA-12914

Re: [DISCUSS] KIP-390: Support Compression Level (rebooted)

Btw, I am OK with doing compression level first, but I don't want to rule out the buffer size change without understanding better. Ismael On Tue, Jun 8, 2021 at 8:33 AM Ismael Juma wrote: > Hi Dongjin, > > I was thinking of a simple test: Snappy with 1 KB block size vs 32 KB > block size. If

Re: [DISCUSS] KIP-390: Support Compression Level (rebooted)

Hi Dongjin, I was thinking of a simple test: Snappy with 1 KB block size vs 32 KB block size. If the compression rate is similar for both, then it seems very wasteful to use 32 KB. I suspect you will see a significant difference though. Ismael On Tue, Jun 8, 2021 at 8:27 AM Dongjin Lee wrote:

Re: [DISCUSS] KIP-390: Support Compression Level (rebooted)

Hi Ismael, I added the linear write benchmark result to the proposal. Like the producer benchmark, the least compression level showed the best MB/sec for any case. I tested several configurations, but the result was almost the same. If you have any proposals for the benchmark, don't hesitate to

Re: [DISCUSS] KIP-724: Drop support for message formats v0 and v1

Hi Jason, Thanks for the thoughtful comments. Responses below. 1. Good point. I updated the KIP to up-convert during replication if the IBP is 3.0. I am still not 100% sure if this is truly required, but it does seem like a good idea to avoid flip-flopping like this. I'll follow up with you to

Re: [DISCUSS] KIP--754: Make Scala case class's final

So I am only changing Scala code within the core project, if there are no public interfaces within that project then yes I think you are right. On Tue, 8 Jun 2021, 16:07 Ismael Juma, wrote: > Hi, > > Thanks for the KIP. KIPs are meant to focus on public facing APIs, > protocols, configs, etc.

Re: [DISCUSS] KIP--754: Make Scala case class's final

Hi, Thanks for the KIP. KIPs are meant to focus on public facing APIs, protocols, configs, etc. The only Scala API that is public facing is the Kafka Streams Scala API. Is this KIP focused on that? Ismael On Tue, Jun 8, 2021 at 3:29 AM Matthew de Detrich wrote: > Hello everyone, > > I'd like

Apache Version upgrade

Dear Kafka Experts 1- Can any one share the upgrade plan with steps /Plan /tracker or any useful documentation please. 2- upgrading kafka from old version of 0.11 to 2.5 .Any suggestions/directions is highly appreciated. Thanks

Re: [DISCUSS] KIP-726: Make the CooperativeStickyAssignor as the default assignor

Hi Ryan, Thanks for the comments. The KAFKA-12896 is already set as blocker for V3.0, which means, V3.0 won't be released before KAFKA-12896 is fixed. I think this KIP and KAFKA-12896

Re: [DISCUSS] KIP--754: Make Scala case class's final

Pull request has been made at https://github.com/apache/kafka/pull/10839 On Tue, Jun 8, 2021 at 12:28 PM Matthew de Detrich < matthew.dedetr...@aiven.io> wrote: > Hello everyone, > > I'd like to discuss the following KIP which involves making all scala case > class's final due to best practices

[DISCUSS] KIP--754: Make Scala case class's final

Hello everyone, I'd like to discuss the following KIP which involves making all scala case class's final due to best practices https://cwiki.apache.org/confluence/display/KAFKA/KIP-754%3A+Make+Scala+case+class%27s+final Doing this for the upcoming Kafka 3.0.0 release would be ideal due to source

[jira] [Created] (KAFKA-12913) Make Scala Case class's final

Matthew de Detrich created KAFKA-12913: -- Summary: Make Scala Case class's final Key: KAFKA-12913 URL: https://issues.apache.org/jira/browse/KAFKA-12913 Project: Kafka Issue Type:

Re: [VOTE] KIP-751: Drop support for Scala 2.12 in Kafka 4.0 (deprecate in 3.0)

Hi Ismael, Thank you for the KIP! +1 (binding) Best, Bruno On 08.06.21 10:11, Matthew de Detrich wrote: +1 (non binding) On Tue, Jun 8, 2021 at 4:34 AM Luke Chen wrote: Hi Ismael, Thanks for the KIP! +1 (non-binding) Thanks. Luke On Tue, Jun 8, 2021 at 8:16 AM Israel Ekpo wrote: I

Re: [VOTE] KIP-750: Drop support for Java 8 in Kafka 4.0 (deprecate in 3.0)

Hi Ismael, Thank you for the KIP! +1 (binding) Best, Bruno On 08.06.21 10:11, Matthew de Detrich wrote: +1 (non binding) On Tue, Jun 8, 2021 at 4:48 AM Luke Chen wrote: Hi Ismael, Thanks for the KIP. +1 (non-binding) Thanks. Luke On Tue, Jun 8, 2021 at 7:18 AM Konstantine Karantasis

Re: [VOTE] KIP-751: Drop support for Scala 2.12 in Kafka 4.0 (deprecate in 3.0)

+1 (non binding) On Tue, Jun 8, 2021 at 4:34 AM Luke Chen wrote: > Hi Ismael, > Thanks for the KIP! > +1 (non-binding) > > Thanks. > Luke > > On Tue, Jun 8, 2021 at 8:16 AM Israel Ekpo wrote: > > > I support this as well. The motivation and proposed changes makes sense > to > > me > > > > +1

Re: [VOTE] KIP-750: Drop support for Java 8 in Kafka 4.0 (deprecate in 3.0)

+1 (non binding) On Tue, Jun 8, 2021 at 4:48 AM Luke Chen wrote: > Hi Ismael, > Thanks for the KIP. > +1 (non-binding) > > Thanks. > Luke > > On Tue, Jun 8, 2021 at 7:18 AM Konstantine Karantasis > wrote: > > > Thanks for the KIP Ismael. I agree that giving an early enough > deprecation > >

Build failed in Jenkins: Kafka » Kafka Branch Builder » trunk #205

See Changes: -- [...truncated 472979 lines...] [2021-06-08T07:08:57.889Z] ZooKeeperClientTest > testDeleteExistingZNode() PASSED [2021-06-08T07:08:57.889Z]