[
https://issues.apache.org/jira/browse/KAFKA-16944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16944.
-
Fix Version/s: 3.9.0
Resolution: Fixed
> Range assignor doesn't co-partit
[
https://issues.apache.org/jira/browse/KAFKA-17058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-17058.
-
Fix Version/s: 3.9.0
Resolution: Fixed
> Extend CoordinatorRuntime to support non-ato
1, Jun Rao wrote:
> > Hi, David,
> >
> > Yes, that's another option. It probably has its own challenges. For
> > example, the FeatureCommand tool currently treats disabling a feature as
> > setting the version to 0. It would be useful to get Jose's opinion on
> this
> >
[
https://issues.apache.org/jira/browse/KAFKA-17047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-17047.
-
Fix Version/s: 3.9.0
Resolution: Fixed
> Refactor Consumer group and shared clas
[
https://issues.apache.org/jira/browse/KAFKA-17050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-17050.
-
Fix Version/s: 3.8.0
Resolution: Fixed
> Revert group.version for 3.8 and
Hi Omnia,
Thanks for the KIP. I agree that we should migrate admin APIs to the new
pattern.
DJ1: Why do we want to migrate only a subset of the APIs vs migrating all
of them? For instance, there are DescribeGroups, ConsumerGroupDescribe,
etc. Do we have reasons not to migrate them too? I think
David Jacot created KAFKA-17058:
---
Summary: Extend CoordinatorRuntime to support non-atomic writes
Key: KAFKA-17058
URL: https://issues.apache.org/jira/browse/KAFKA-17058
Project: Kafka
Issue
t; > > > value is 0 for clients that send v3
> > >>> >> > > > >
> > >>> >> > > > > For 3.8, I planned to set the 0s in the response to 1. Is
> it
> > >>> better
> > >>> >> > to
> >
Hi Colin,
I agree that we try hard to avoid breaking compatibility. I am not
questioning this at all. I also agree with your concern.
My point was about requiring users to opt-in for a feature vs having it
enabled by default during the EA and the Preview phases. With KIP-1022, the
only way to
[
https://issues.apache.org/jira/browse/KAFKA-16822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16822.
-
Fix Version/s: 3.9.0
Resolution: Fixed
> Abstract consumer group in coordinator to sh
Hi all,
I think that it would be nice to have an official way to enable
non-production-ready features in order to have a way to test them in
development/soak clusters. For instance, I would like the new consumer
protocol to be disabled by default but users should be able to enable it if
they want
[
https://issues.apache.org/jira/browse/KAFKA-16973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16973.
-
Fix Version/s: 3.9.0
Resolution: Fixed
> Fix caught-up condit
is
cut.
David
Le lun. 17 juin 2024 à 19:33, Matthias J. Sax a écrit :
> Why would 4.0 be based on 3.8? My understanding is, that it will be
> based on 3.9.
>
> -Matthias
>
> On 6/14/24 11:22 PM, David Jacot wrote:
> > I agree that we should keep 4.0 time-based. My qu
+1 for the release plan. Thanks!
+1 for releasing 4.0 four months after 3.9. 4.0 is actually a pretty big
release as we will GA KIP-848, including new group coordinator and new
consumer rebalance protocol. This is a pretty big change :).
Best,
David
Le lun. 17 juin 2024 à 20:36, Colin McCabe a
[
https://issues.apache.org/jira/browse/KAFKA-16673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16673.
-
Fix Version/s: 3.9.0
Resolution: Fixed
> Optimize toTopicPartiti
David Jacot created KAFKA-16973:
---
Summary: Fix caught-up condition
Key: KAFKA-16973
URL: https://issues.apache.org/jira/browse/KAFKA-16973
Project: Kafka
Issue Type: Sub-task
ginally.
> >
> > The 3.9 one should really be an additional "out of schedule" release not
> > impacting any other releases.
> >
> >
> > -Matthias
> >
> > On 6/14/24 1:29 PM, David Jacot wrote:
> >> The plan sounds good to me. I s
The plan sounds good to me. I suppose that we will follow our regular
cadence for 4.0 and release it four months after 3.9 (in November?). Is
this correct?
Best,
David
Le ven. 14 juin 2024 à 21:57, José Armando García Sancio
a écrit :
> +1 on the proposed release plan for 3.8.
>
> Thanks!
>
>
[
https://issues.apache.org/jira/browse/KAFKA-16317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16317.
-
Resolution: Won't Do
> Add event rate in GroupCoordinatorRuntimeMetr
[
https://issues.apache.org/jira/browse/KAFKA-16674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16674.
-
Resolution: Fixed
This was done in https://github.com/apache/kafka/pull/15785.
> Adj
[
https://issues.apache.org/jira/browse/KAFKA-16673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot reopened KAFKA-16673:
-
> Optimize toTopicPartitions with ConsumerProtocolSubscript
[
https://issues.apache.org/jira/browse/KAFKA-16673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16673.
-
Fix Version/s: 3.8.0
Resolution: Duplicate
This was done as part of https://github.com
[
https://issues.apache.org/jira/browse/KAFKA-16770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16770.
-
Resolution: Fixed
> Coalesce records into bigger batc
[
https://issues.apache.org/jira/browse/KAFKA-16930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16930.
-
Resolution: Fixed
> UniformHeterogeneousAssignmentBuilder throws NPE when member
David Jacot created KAFKA-16930:
---
Summary: UniformHeterogeneousAssignmentBuilder throws NPE when
member has not subscriptions
Key: KAFKA-16930
URL: https://issues.apache.org/jira/browse/KAFKA-16930
[
https://issues.apache.org/jira/browse/KAFKA-16821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16821.
-
Fix Version/s: 3.8.0
Resolution: Fixed
> Create a new interface to store member metad
[
https://issues.apache.org/jira/browse/KAFKA-14509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-14509.
-
Fix Version/s: 3.8.0
Resolution: Fixed
> Add ConsumerGroupDescribe
[
https://issues.apache.org/jira/browse/KAFKA-14701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-14701.
-
Fix Version/s: 3.8.0
Resolution: Fixed
> More broker side partition assignor to com
[
https://issues.apache.org/jira/browse/KAFKA-16664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16664.
-
Fix Version/s: 3.8.0
Resolution: Fixed
> Re-add EventAccumulator.take(time
[
https://issues.apache.org/jira/browse/KAFKA-16861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16861.
-
Fix Version/s: 3.8.0
Resolution: Fixed
> Don't convert to group to classic if the s
[
https://issues.apache.org/jira/browse/KAFKA-16864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16864.
-
Fix Version/s: 3.8.0
Resolution: Fixed
> Copy on write in the Optimized Uniform Assig
[
https://issues.apache.org/jira/browse/KAFKA-16860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16860.
-
Resolution: Fixed
> Introduce `group.version` feature f
Hi all,
Thanks for the KIP. This is definitely a worthwhile feature. However, I am
a bit sceptical on the ZK part of the story. The 3.8 release is supposed to
be the last one supporting ZK so I don't really see how we could bring it
to ZK, knowing that we don't plan to do a 3.9 release (current
[
https://issues.apache.org/jira/browse/KAFKA-16722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16722.
-
Reviewer: David Jacot
Resolution: Fixed
> Add ConsumerGroupPartitionAssignor interf
[
https://issues.apache.org/jira/browse/KAFKA-16569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16569.
-
Resolution: Won't Do
> Target Assignment Format Cha
[
https://issues.apache.org/jira/browse/KAFKA-16832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16832.
-
Fix Version/s: 3.8.0
Resolution: Fixed
> LeaveGroup API for upgrading ConsumerGr
David Jacot created KAFKA-16860:
---
Summary: Introduce `group.version` feature flag
Key: KAFKA-16860
URL: https://issues.apache.org/jira/browse/KAFKA-16860
Project: Kafka
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/KAFKA-16371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16371.
-
Fix Version/s: 3.8.0
3.7.1
Assignee: David Jacot
Resolution
David Jacot created KAFKA-16846:
---
Summary: Should TxnOffsetCommit API fail all the offsets if any
fails the validation?
Key: KAFKA-16846
URL: https://issues.apache.org/jira/browse/KAFKA-16846
Project
[
https://issues.apache.org/jira/browse/KAFKA-16625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16625.
-
Fix Version/s: 3.8.0
Reviewer: David Jacot
Resolution: Fixed
> Reverse Loo
[
https://issues.apache.org/jira/browse/KAFKA-16831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16831.
-
Fix Version/s: 3.8.0
Reviewer: David Jacot
Resolution: Fixed
[
https://issues.apache.org/jira/browse/KAFKA-16815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16815.
-
Fix Version/s: 3.8.0
Reviewer: David Jacot
Resolution: Fixed
> Han
[
https://issues.apache.org/jira/browse/KAFKA-16626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16626.
-
Fix Version/s: 3.8.0
Resolution: Fixed
> Uuid to String for subscribed topic na
[
https://issues.apache.org/jira/browse/KAFKA-16793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16793.
-
Fix Version/s: 3.8.0
Reviewer: David Jacot
Resolution: Fixed
> Heartbeat
[
https://issues.apache.org/jira/browse/KAFKA-16762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16762.
-
Fix Version/s: 3.8.0
Reviewer: David Jacot
Resolution: Fixed
> SyncGroup
Hi Andrew,
Thanks for the KIP! This is really exciting! +1 (binding) from me.
One note regarding the partition assignor interface changes that you
proposed, it would be great to get the changes in 3.8 in order to not break
the API of KIP-848 after the preview.
Best,
David
On Wed, May 15, 2024
David Jacot created KAFKA-16770:
---
Summary: Coalesce records into bigger batches
Key: KAFKA-16770
URL: https://issues.apache.org/jira/browse/KAFKA-16770
Project: Kafka
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/KAFKA-16694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16694.
-
Fix Version/s: 3.8.0
Resolution: Fixed
> Remove rack aware code in assignors temporar
[
https://issues.apache.org/jira/browse/KAFKA-15578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-15578.
-
Resolution: Fixed
> Run System Tests for Old protocol in the New Coordina
[
https://issues.apache.org/jira/browse/KAFKA-16117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16117.
-
Fix Version/s: 3.8.0
Resolution: Fixed
> Add Integration test for check
[
https://issues.apache.org/jira/browse/KAFKA-16735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16735.
-
Resolution: Fixed
> Deprecate offsets.commit.required.acks in
David Jacot created KAFKA-16736:
---
Summary: Remove offsets.commit.required.acks in 4.0
Key: KAFKA-16736
URL: https://issues.apache.org/jira/browse/KAFKA-16736
Project: Kafka
Issue Type: Sub
David Jacot created KAFKA-16735:
---
Summary: Deprecate offsets.commit.required.acks in 3.8
Key: KAFKA-16735
URL: https://issues.apache.org/jira/browse/KAFKA-16735
Project: Kafka
Issue Type: Sub
gt; >
> > > On Wed, May 8, 2024 at 5:27 PM Andrew Schofield
> > > wrote:
> > > >
> > > > Hi,
> > > > Thanks for the KIP.
> > > >
> > > > +1 (non-binding)
> > > >
> > > > Thanks,
> > > > A
[
https://issues.apache.org/jira/browse/KAFKA-16587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16587.
-
Fix Version/s: 3.8.0
Reviewer: David Jacot
Resolution: Fixed
> St
[
https://issues.apache.org/jira/browse/KAFKA-16663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16663.
-
Fix Version/s: 3.8.0
Reviewer: David Jacot
Resolution: Fixed
Hi folks,
I'd like to start a voting thread for KIP-1041: Drop
`offsets.commit.required.acks` config in 4.0 (deprecate in 3.8).
KIP: https://cwiki.apache.org/confluence/x/9YobEg
Best,
David
[
https://issues.apache.org/jira/browse/KAFKA-16307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16307.
-
Fix Version/s: 3.8.0
Reviewer: David Jacot
Resolution: Fixed
>
[
https://issues.apache.org/jira/browse/KAFKA-16615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16615.
-
Fix Version/s: 3.8.0
Reviewer: David Jacot
Assignee: Dongnuo Lyu
Hi folks,
I have put together a very small KIP to
deprecate offsets.commit.required.acks in 3.8 and remove it in 4.0. See the
motivation for the reason.
KIP: https://cwiki.apache.org/confluence/x/9YobEg
Please let me know what you think.
Best,
David
David Jacot created KAFKA-16658:
---
Summary: Drop `offsets.commit.required.acks` config in 4.0
(deprecate in 3.8)
Key: KAFKA-16658
URL: https://issues.apache.org/jira/browse/KAFKA-16658
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-16568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16568.
-
Fix Version/s: 3.8.0
Resolution: Fixed
> Add JMH Benchmarks for assignor performa
t;
> >>>> Thanks,
> >>>> Andrew
> >>>>
> >>>>> On 22 Apr 2024, at 20:04, Jun Rao wrote:
> >>>>>
> >>>>> Hi, Andrew,
> >>>>>
> >>>>> Thanks for the reply.
>
Hi Andrew,
Thanks for the KIP. This work is really exciting.
I finally had a bit of time to go through the KIP. I need to read it a
second time in order to get into the details. I have noted a few
points/questions:
001: The dynamic config to force the group type is really weird. As you
said,
[
https://issues.apache.org/jira/browse/KAFKA-16294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16294.
-
Fix Version/s: 3.8.0
Resolution: Fixed
> Add group protocol migration enabling con
Hey,
I think that we discussed this in this KIP:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-906%3A+Tools+migration+guidelines.
I don't remember all the details though.
Best,
David
On Wed, Apr 10, 2024 at 2:54 PM Chia-Ping Tsai wrote:
> Dear Kafka,
>
> Migrating command tools from
David Jacot created KAFKA-16503:
---
Summary: getOrMaybeCreateClassicGroup should not thrown
GroupIdNotFoundException
Key: KAFKA-16503
URL: https://issues.apache.org/jira/browse/KAFKA-16503
Project: Kafka
+1 (binding). Thanks for the KIP!
On Mon, Apr 8, 2024 at 7:23 PM Andrew Schofield <
andrew_schofield_j...@outlook.com> wrote:
> Hi Justine,
> Thanks for the KIP.
>
> +1 (non-binding)
>
> Thanks,
> Andrew
>
> > On 8 Apr 2024, at 18:07, Justine Olshan
> wrote:
> >
> > Hello all,
> > I would like
Thanks, Michal. Let me add it to my review queue.
BR,
David
On Fri, Apr 5, 2024 at 3:29 PM Michał Łowicki wrote:
> Hi there!
>
> Created https://issues.apache.org/jira/browse/KAFKA-16371 few weeks back
> but there wasn't any attention. Any chance someone knowing that code could
> take a look
David Jacot created KAFKA-16470:
---
Summary: kafka-dump-log --offsets-decoder should support new
records
Key: KAFKA-16470
URL: https://issues.apache.org/jira/browse/KAFKA-16470
Project: Kafka
s.
> >> > > > > > > KIP-915 introduced flexible versions, but it was never put
> to
> >> > use.
> >> > > MV
> >> > > > > has
> >> > > > > > > never gated these. This KIP will do that. I can includ
[
https://issues.apache.org/jira/browse/KAFKA-16148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16148.
-
Fix Version/s: 3.8.0
Resolution: Fixed
> Implement GroupMetadataManager#onUnloa
the group coordinator as we may use it for queues
too. It would also be aligned with `metadata.version`. I apologize if this
was already discussed.
Best,
David
On Tue, Apr 2, 2024 at 11:18 AM David Jacot wrote:
> Hi Jun,
>
> > Historically, the format of all records were controlle
gt; that right? It would be useful to document that.
> > > >>
> > > >> Also, we should align on the version numbering. "kafka-feature
> > disable"
> > > >> says "Disable one or more feature flags. This is the same as
> > downgrading
> > >
Hi, Jun, Justine,
Regarding `group.coordinator.version`, the idea is to use it to gate
records and APIs of the group coordinator. The first use case will be
KIP-848. We will use version 2 of the flag to gate all the new records and
the new ConsumerGroupHeartbeat/Describe APIs present in AK 3.8.
[
https://issues.apache.org/jira/browse/KAFKA-16353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16353.
-
Resolution: Fixed
> Offline protocol migration integration te
[
https://issues.apache.org/jira/browse/KAFKA-16374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16374.
-
Fix Version/s: 3.8.0
Resolution: Fixed
> High watermark updates should have a hig
[
https://issues.apache.org/jira/browse/KAFKA-15989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-15989.
-
Fix Version/s: 3.8.0
Resolution: Fixed
> Upgrade existing generic group to consu
[
https://issues.apache.org/jira/browse/KAFKA-15763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-15763.
-
Resolution: Won't Fix
We went with another approach.
> Group Coordinator should not deli
[
https://issues.apache.org/jira/browse/KAFKA-16313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16313.
-
Fix Version/s: 3.8.0
Assignee: Dongnuo Lyu
Resolution: Fixed
> Offline gr
[
https://issues.apache.org/jira/browse/KAFKA-16367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16367.
-
Fix Version/s: 3.8.0
Resolution: Fixed
> Full ConsumerGroupHeartbeat response m
David Jacot created KAFKA-16374:
---
Summary: High watermark updates should have a higher priority
Key: KAFKA-16374
URL: https://issues.apache.org/jira/browse/KAFKA-16374
Project: Kafka
Issue
[
https://issues.apache.org/jira/browse/KAFKA-15997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-15997.
-
Resolution: Fixed
This issue got resolved by https://issues.apache.org/jira/browse/KAFKA-16249
[
https://issues.apache.org/jira/browse/KAFKA-16249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16249.
-
Fix Version/s: 3.8.0
Resolution: Fixed
> Improve reconciliation state mach
David Jacot created KAFKA-16367:
---
Summary: Full ConsumerGroupHeartbeat response must be sent when
full request is received
Key: KAFKA-16367
URL: https://issues.apache.org/jira/browse/KAFKA-16367
[
https://issues.apache.org/jira/browse/KAFKA-15462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-15462.
-
Fix Version/s: 3.8.0
Resolution: Fixed
> Add group type filter to the admin cli
[
https://issues.apache.org/jira/browse/KAFKA-16306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16306.
-
Fix Version/s: 3.8.0
Resolution: Fixed
> GroupCoordinatorService log
David Jacot created KAFKA-16249:
---
Summary: Improve reconciliation state machine
Key: KAFKA-16249
URL: https://issues.apache.org/jira/browse/KAFKA-16249
Project: Kafka
Issue Type: Sub-task
nt and hence this information will be
> completely missing from the Jenkins report. Have we considered including
> the flakyFailure information ourselves? I have seen that being done and it
> seems strictly better than totally ignoring it.
>
> Ismael
>
> On Mon, Feb 12, 2024 at 12:11
David Jacot created KAFKA-16244:
---
Summary: Move code style exceptions from suppressions.xml to the
code
Key: KAFKA-16244
URL: https://issues.apache.org/jira/browse/KAFKA-16244
Project: Kafka
Hi folks,
I have been playing with `reports.junitXml.mergeReruns` setting in gradle
[1]. From the gradle doc:
> When mergeReruns is enabled, if a test fails but is then retried and
succeeds, its failures will be recorded as instead of
, within one . This is effectively the reporting
produced by
[
https://issues.apache.org/jira/browse/KAFKA-16178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16178.
-
Resolution: Fixed
> AsyncKafkaConsumer doesn't retry joining the group after rediscover
> > mayanks.nar...@gmail.com> wrote:
> >
> >> Thank you all for your votes, Jun, David, and Jason!
> >>
> >> On Tue, Oct 3, 2023 at 11:44 PM Jason Gustafson
> >> wrote:
> >>
> >>> +1 Thanks for the KIP
> >>&
David Jacot created KAFKA-16227:
---
Summary: Console consumer fails with `IllegalStateException`
Key: KAFKA-16227
URL: https://issues.apache.org/jira/browse/KAFKA-16227
Project: Kafka
Issue Type
[
https://issues.apache.org/jira/browse/KAFKA-15460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-15460.
-
Fix Version/s: 3.8.0
Resolution: Fixed
> Add group type filter to ListGroups
[
https://issues.apache.org/jira/browse/KAFKA-16189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16189.
-
Fix Version/s: 3.8.0
Resolution: Fixed
> Extend admin to support ConsumerGroupDescr
[
https://issues.apache.org/jira/browse/KAFKA-16168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16168.
-
Fix Version/s: 3.8.0
Resolution: Fixed
> Implement GroupCoordinator.onPartitionsDele
[
https://issues.apache.org/jira/browse/KAFKA-16095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-16095.
-
Fix Version/s: 3.8.0
Resolution: Fixed
> Update list group state type filter to incl
[
https://issues.apache.org/jira/browse/KAFKA-14505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-14505.
-
Fix Version/s: 3.8.0
Resolution: Fixed
> Implement TnxOffsetCommit
David Jacot created KAFKA-16194:
---
Summary: KafkaConsumer.groupMetadata() should be correct when
first records are returned
Key: KAFKA-16194
URL: https://issues.apache.org/jira/browse/KAFKA-16194
1 - 100 of 926 matches
Mail list logo
