[jira] [Created] (KAFKA-12576) Renaming log segment should not result in a copy

Jose Armando Garcia Sancio created KAFKA-12576: -- Summary: Renaming log segment should not result in a copy Key: KAFKA-12576 URL: https://issues.apache.org/jira/browse/KAFKA-12576 Project:

[jira] [Created] (KAFKA-12574) Deprecate eos-alpha

A. Sophie Blee-Goldman created KAFKA-12574: -- Summary: Deprecate eos-alpha Key: KAFKA-12574 URL: https://issues.apache.org/jira/browse/KAFKA-12574 Project: Kafka Issue Type:

Jenkins build is back to normal : Kafka » kafka-2.8-jdk8 #84

See

[jira] [Created] (KAFKA-12575) Eliminate Log.isLogDirOffline boolean attribute

Kowshik Prakasam created KAFKA-12575: Summary: Eliminate Log.isLogDirOffline boolean attribute Key: KAFKA-12575 URL: https://issues.apache.org/jira/browse/KAFKA-12575 Project: Kafka

Build failed in Jenkins: Kafka » kafka-2.8-jdk8 #83

See Changes: [A. Sophie Blee-Goldman] KAFKA-12523: handle TaskCorruption and TimeoutException during handleCorruption and handleRevocation (#10407) --

Re: [DISCUSS] KIP-712: Shallow Mirroring

It's interesting this VOTE thread finally becomes a DISCUSS thread. For MM2 concern, I will take a look to see whether I can add the support for MM2. For Ismael's concern on multiple batches in the ProduceRequest (conflicting with KIP-98), here is my take: 1. We do need to group multiple

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

Hi Sophie & Ismael, Thank you for your feedback. No problem, let's pause this KIP and wait for this improvement: KAFKA-12477 . Stay tuned :) Thank you. Luke On Tue, Mar 30, 2021 at 3:14 AM Ismael Juma wrote: > Hi Sophie, > > I didn't analyze

[jira] [Created] (KAFKA-12570) Improve Documentation on COMPACT_ARRAY usage

Pavol Ipoth created KAFKA-12570: --- Summary: Improve Documentation on COMPACT_ARRAY usage Key: KAFKA-12570 URL: https://issues.apache.org/jira/browse/KAFKA-12570 Project: Kafka Issue Type:

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

Hi Ismael, Thanks for your good question. Answer them below: *1. Are we saying that every consumer upgraded would have to follow the complex path described in the KIP? * --> We suggest that every consumer did these 2 steps of rolling upgrade. And after KAFKA-12477

[jira] [Created] (KAFKA-12571) Eliminate LogEndOffset dependency on LeaderEpochFileCache c'tor

Kowshik Prakasam created KAFKA-12571: Summary: Eliminate LogEndOffset dependency on LeaderEpochFileCache c'tor Key: KAFKA-12571 URL: https://issues.apache.org/jira/browse/KAFKA-12571 Project:

Re: [DISCUSS] KIP-712: Shallow Mirroring

Ryanne, You misunderstood the referenced comment. It is about the produce request change to have multiple batches: "Up to ProduceRequest V2, a ProduceRequest can contain multiple batches of messages stored in the record_set field, but this was disabled in V3. We are proposing to bring the

[jira] [Created] (KAFKA-12572) Add import ordering checkstyle rule and configure an automatic formatter

Dongjin Lee created KAFKA-12572: --- Summary: Add import ordering checkstyle rule and configure an automatic formatter Key: KAFKA-12572 URL: https://issues.apache.org/jira/browse/KAFKA-12572 Project:

Re: [DISCUSS] KIP-718: Make KTable Join on Foreign key unopinionated

Hi Guozhang, Apologies for the late answer. Originally that was my proposal - to piggyback on the provided materialisation method ( https://issues.apache.org/jira/browse/KAFKA-10383). John Roesler suggested to us to provide even further fine tuning on API level parameters. Maybe we could see this

[jira] [Created] (KAFKA-12573) Removed deprecated `Metric#value`

David Jacot created KAFKA-12573: --- Summary: Removed deprecated `Metric#value` Key: KAFKA-12573 URL: https://issues.apache.org/jira/browse/KAFKA-12573 Project: Kafka Issue Type: Improvement

Re: [VOTE] KIP-707: The future of KafkaFuture

+1, thanks! On Mon, Mar 29, 2021, 10:54 AM Ismael Juma wrote: > Thanks for the KIP, +1 (binding). > > Ismael > > On Mon, Mar 29, 2021 at 8:35 AM Tom Bentley wrote: > > > Hi, > > > > I'd like to start a vote on KIP-707, which proposes to add > > KafkaFuture.toCompletionStage(), deprecate

[VOTE] KIP-707: The future of KafkaFuture

Hi, I'd like to start a vote on KIP-707, which proposes to add KafkaFuture.toCompletionStage(), deprecate KafkaFuture.Function and make a couple of other minor cosmetic changes. https://cwiki.apache.org/confluence/display/KAFKA/KIP-707%3A+The+future+of+KafkaFuture Many thanks, Tom

Re: [DISCUSS] KIP-712: Shallow Mirroring

Ah, I see, thanks Ismael. Now I understand your concern. >From KIP-98, re this change in v3: "This allows us to remove the message set size since each message set already contains a field for the size. More importantly, since there is only one message set to be written to the log, partial

Re: [VOTE] KIP-707: The future of KafkaFuture

Thanks for the KIP, +1 (binding). Ismael On Mon, Mar 29, 2021 at 8:35 AM Tom Bentley wrote: > Hi, > > I'd like to start a vote on KIP-707, which proposes to add > KafkaFuture.toCompletionStage(), deprecate KafkaFuture.Function and make a > couple of other minor cosmetic changes. > > >

[GitHub] [kafka-site] AdilHoumadi commented on pull request #341: MINOR: Fix typo in MirrorMaker v2 documentation

AdilHoumadi commented on pull request #341: URL: https://github.com/apache/kafka-site/pull/341#issuecomment-809546494 @mimaison, sure! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the

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

Hi Sophie, I didn't analyze the KIP in detail, but the two suggestions you mentioned sound like great improvements. A bit more context: breaking changes for a widely used product like Kafka are costly and hence why we try as hard as we can to avoid them. When it comes to the brokers, they are

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

Ismael, It seems like given 3.0 is a breaking release, we have to rely on users being aware of this and responsible enough to read the upgrade guide. Otherwise we could never ever make any breaking changes beyond just removing deprecated APIs or other compilation-breaking errors that would be

[jira] [Resolved] (KAFKA-12428) Add a last-heartbeat-seconds-ago metric to Kafka Consumer

[ https://issues.apache.org/jira/browse/KAFKA-12428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-12428. --- Resolution: Duplicate > Add a last-heartbeat-seconds-ago metric to Kafka Consumer >