Hi,
Thanks for the KIP. A couple of comments:
1. Nit: KIPs should not "consider" things, they propose specific and well
defined changes. Given that, please update the title to match the proposal.
2. Given that we regressed in two different instances (that we found so
far), this indicates a test ga
And also https://issues.apache.org/jira/browse/KAFKA-9952
Ismael
On Wed, Apr 30, 2025 at 2:18 PM Ismael Juma wrote:
> Hi Jose,
>
> We did indeed run into a perf regression related to increased fetch
> request rate due to hw propagation to followers:
>
> https://issues.apac
Hi Jose,
We did indeed run into a perf regression related to increased fetch request
rate due to hw propagation to followers:
https://issues.apache.org/jira/browse/KAFKA-9731
Ismael
On Wed, Apr 30, 2025 at 12:34 PM José Armando García Sancio
wrote:
> Hi Alyssa,
>
> On Wed, Apr 30, 2025 at 12:
That's right. Similar approach:
https://lists.apache.org/thread/3fxqdsosm3z7xp4rr8db2qmyg5vd0v1b
Ismael
On Mon, Apr 21, 2025, 7:43 PM Matthias J. Sax wrote:
> I don't think we would need a second deprecation cycle.
>
> Instead, we could add this new config, and deprecate it right away. This
> w
4.0: Feb/7 2023
> > 3.1.0: Jan/24 2022
> >
> > It's not a huge deal, but seems undesired?
> >
> >
> > -Matthias
> >
> > On 4/16/25 9:02 AM, Ismael Juma wrote:
> > > The issue is that July 23rd is the "earliest release date" b
; 23 was close enough to mid July.
> That said I currently don't have anything planned, so I can move the
> dates 1 (or 2 weeks) earlier, if this is what people prefer.
>
> Thanks,
> Mickael
>
> On Tue, Apr 15, 2025 at 8:09 PM Ismael Juma wrote:
> >
> > Hi Mi
Hi Mickael,
Thoughts on my message below?
Ismael
On Thu, Apr 10, 2025, 7:46 AM Ismael Juma wrote:
> Hi Mickael,
>
> The release plan indicates a release in August. However, 4.0 was released
> on March 18. If we stick to the 4 months schedule, the target release
> should be mid
[
https://issues.apache.org/jira/browse/KAFKA-19043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-19043.
-
Fix Version/s: 4.1.0
Resolution: Fixed
Looks like this was done via https://github.com
;
> > Thanks Mickael.
> >
> > On Wed, Mar 19, 2025 at 9:20 AM Ismael Juma wrote:
> > >
> > > Thanks Mickael!
> > >
> > > Ismael
> > >
> > > On Wed, Mar 19, 2025, 5:54 AM David Arthur wrote:
> > >
> > >
; >
> > > >> > >1. The upgrade to slf4j2 should be postponed to Kafka 5.0 due
> > to
> > > >> > >compatibility issues.
> > > >> > >2. I will revise the motivation section of the KIP to
> emphasize
> > >
What's the burden if it's automated? I agree we should keep it simple for
anything that has to be done manually.
Ismael
On Tue, Apr 1, 2025 at 5:45 PM Matthias J. Sax wrote:
> Hi,
>
> I understand the problem of a long "Reviewers" line and line break, so
> breaking it down into multiple lines,
Hi,
Thanks for the KIP. A few comments:
1. Incompatible changes are generally not allowed in minor releases. Are
you proposing a change for a minor release (eg 4.1) or for a major release
(5.0)?
2. Given that clients in 4.0 support brokers with version 2.1 or higher,
`offsetsForTimes` should neve
Hi Josep,
To clarify, there is no subjectivity as far as I can tell. The
approved-by/reviewed-by trailers would be used if you used the PR `approve`
button. The former for committers and the latter for non committers. Anyone
else who left comments would be in the commented-by trailers. The latter
Hi David,
I am in favor of having a separate field for the people who approve the PR
vs the ones who leave some comments. I actually brought this up when I
initially joined the community (probably around a decade ago), but it
didn't resonate at the time. :) It also makes sense to use a consistent
Using an interface is less effective than making the constructor private
and the class final though.
Ismael
On Mon, Mar 24, 2025, 9:12 PM Chia-Ping Tsai wrote:
> hi All,
>
> > Matthias J. Sax 於 2025年3月5日 凌晨4:20 寫道：
> >
> > To me, the main thing is really, that currently user can call `new` wha
the KIP according to following benefit?
> >
> > > The key benefit of this KIP is that you can add new logging backends
> and
> > select it via a config. This is how most pluggable things work. But it is
> > *not* how slf4j 1.x works. slf4j 1.x requires you to *remove*
t;
Thinking about this some more, 2.1 brokers can still use the older message
format and hence we cannot assume the old message format isn't used.
Ismael
On Wed, Mar 19, 2025 at 1:45 PM Ismael Juma wrote:
> Hi,
>
> Thanks for the KIP. A few comments:
>
> 1. Incompatible chan
t JAR modifications. Furthermore, by
> managing all SLF4J and provider JARs within Kafka, we can ensure SLF4J
> version updates without compatibility concerns, as we can guarantee
> provider JAR consistency with the SLF4J version in the distribution.
>
> Best,
> Chia-Ping
>
Thanks Mickael!
Ismael
On Wed, Mar 19, 2025, 5:54 AM David Arthur wrote:
> +1 thanks Mickael!
>
> David Arthur
>
>
> On Wed, Mar 19, 2025 at 07:59 Mickael Maison
> wrote:
>
> > Hi,
> >
> > I'd like to volunteer to be the release manager for the Apache Kafka
> > 4.1.0 release.
> >
> > If there
Thanks Luke!
Ismael
On Tue, Mar 18, 2025 at 3:44 PM Luke Chen wrote:
> Hi Matthias,
>
> I can work on the 3.9.1 release if there are no objections.
>
> Thanks.
> Luke
>
> On Thu, Mar 13, 2025 at 3:06 AM Matthias J. Sax wrote:
>
> > Hello,
> >
> > with 4.0.0 slowly winding down, it seems it's t
Hi TengYao,
It's a bit difficult to review the KIP. I don't follow most of the
motivation. The only one that I follow is:
"Our current build configuration employs fragile dependency management
tricks to handle SLF4J backends. We can eliminate these brittle build
mechanisms by transitioning to exp
Divij Vaidya,
> DL1231, Dmitry Werner, donaldzhu-cc, Dongnuo Lyu, dujian0068, Edoardo
> Comar, Eric Chang, Federico Valeri, Frederik Rouleau, GangHuo,
> Gantigmaa Selenge, Gaurav Narula, Greg Harris, Guozhang Wang, Hailey
> Ni, Hongten, Hyunsang Han, Ian McDonald, Igor Soarez, Ismael Jum
Hi Stig,
Kafka 4.0 is likely to be released in a day or two. Even so, I think it
makes sense to revive the backporting thread given the lack of workaround
for Java 24.
Ismael
On Mon, Mar 17, 2025 at 7:44 AM Stig Rohde Døssing
wrote:
> Hi,
>
> Some months ago, a reflective shim was added in
> h
int#listenerName()`
>
> Best,
> Chia-Ping
>
> On 2025/03/17 07:58:47 Ismael Juma wrote:
> > To be clear, that's not the only issue. There is no way to make a
> > compatible change in signature like the one proposed by 5.0. Two major
> > releases would be
osed changes.
>
> [0] https://lists.apache.org/thread/v6s7wnmzbprs26dyd7gom0g55k0ww1o2
> [1]
>
> https://github.com/apache/kafka/blob/trunk/clients/src/main/java/org/apache/kafka/clients/admin/RaftVoterEndpoint.java
>
> Best,
> Chia-Ping
>
>
>
> Ismael Juma 於 2025年3月17日 週一
Hi,
We cannot make incompatible changes to public classes outside of major
releases. The evolving annotation was left by mistake given that these
classes have been there for a long time by now.
The general way to handle this is to have a new non deprecated method,
deprecate the old one. And then
Yes, that's the implication of this change.
Ismael
On Thu, Mar 6, 2025 at 12:38 AM Chia-Ping Tsai wrote:
> hi David
>
> It appears we can't push reverted commits to trunk from our local
> repository. See the following error message.
>
> remote: Resolving deltas: 100% (15/15), completed with 11
Thanks for updating the KIP. A comment below:
As we introduce this change in major version 4.1.0, since we provide the
> backend binding dependencies, users should be able to upgrade their backend
> dependencies.
4.1 is a minor version (not major version). So, this KIP is only
acceptable in 4.1.
Ismael Juma created KAFKA-18935:
---
Summary: Ensure brokers do not return null records in FetchResponse
Key: KAFKA-18935
URL: https://issues.apache.org/jira/browse/KAFKA-18935
Project: Kafka
Ismael Juma created KAFKA-18934:
---
Summary: Consider making records in FetchResponse not nullable
Key: KAFKA-18934
URL: https://issues.apache.org/jira/browse/KAFKA-18934
Project: Kafka
Issue
push.
>
> The UI will give us an explicit visual warning if we try to merge a PR
> without passing checks.
>
> Does this make sense?
>
> -David
>
>
>
> On Thu, Mar 6, 2025 at 11:47 AM Ismael Juma wrote:
>
> > Hi David,
> >
> > I don't follow th
rom a different repo)
>>
>> [image: image.png]
>>
>>
>> I'll get clarification from Infra about how this all works within the
>> context of asf.yaml.
>>
>> -David
>>
>> On Thu, Mar 6, 2025 at 3:48 AM Ismael Juma wrote:
>>
>>&g
library.
> > >
> > > We generate entities for the full protocol by introspecting the JSON
> > > schema definitions under _. How will the KIP change those definitions?
> > Will
> > > the dropped versions be reflected as bumps of the lower limit
> &g
I meant converged (instead of converted).
On Wed, Mar 5, 2025, 9:22 PM Ismael Juma wrote:
> Hi,
>
> The vote should remain open for 72 hours. Given that the KIP discussion
> only really converted yesterday, I think we should count the 72 hours from
> that point forward.
>
&
Hi,
The vote should remain open for 72 hours. Given that the KIP discussion
only really converted yesterday, I think we should count the 72 hours from
that point forward.
Ismael
On Wed, Mar 5, 2025, 6:40 PM Kuan Po Tseng wrote:
> Thanks everyone for voting and feedback.
>
> The vote has passed
Hi,
Thanks for the KIP. Why did we reject the alternative where the constructor
is unavailable to external users?
Ismael
On Tue, Feb 25, 2025 at 8:27 AM Paweł Szymczyk
wrote:
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-1136%3A+Make+ConsumerGroupMetadata+an+interface
>
> --
> Pozd
Hi Chia-Ping and Bruno,
Right. Matthias stated that the 3 releases rule is the source of truth and
I don't recall that being the case. The source of truth is 12 months - I
was one of the people who was part of that discussion when the Scala
consumer was removed. I also disagree that the 3 releases
t. We cannot time releases totally
> accurately, so the 3-prior-releases rule should be the "source of truth"
> IMHO, that just practically translated to "about 1 year". But as I said
> above, I also don't think we need to be dogmatic about it.
>
>
>
&
t; that is running an consumer or producer with some older versions, and
> > >> executes a rolling bounce to upgrade the app...
> > >>
> > >> But maybe such a test is not necessary for clients (compare to Kafka
> > >> Streams), and the existing
One more thing, 3.7 was released in Feb 2024 and hence it will be more than
12 months by the time 4.0 is released. Technically, it would be ok to
remove APIs deprecated in 3.7.
Ismael
On Sat, Mar 1, 2025, 8:34 AM Ismael Juma wrote:
> Hi Chia-Ping,
>
> Is this Connect removal the only
>
> Jun
>
> On Thu, Feb 27, 2025 at 7:22 PM Ismael Juma wrote:
>
> > Thanks for the testing Kirk. Can you please file an issue for the
> repeated
> > log to make sure it doesn't get lost in this thread?
> >
> > Ismael
> >
> > On Thu, Feb 27
e do effectively/implicitly test upgrading 2.0 (and older
> clients) to 4.0 using 3.9 and older brokers. These test coverage does
> not exist in a single branch so, but test from different branches
> combined, implicitly cover this. Nevertheless, is it tested.
>
> So it seems both Bruno and Is
Thanks for the testing Kirk. Can you please file an issue for the repeated
log to make sure it doesn't get lost in this thread?
Ismael
On Thu, Feb 27, 2025 at 2:54 PM Kirk True wrote:
> Hi David,
>
> I focused on testing the clients using Java 11:
>
> My steps:
>
> 1. Start the broker via the n
Hi Bruno,
A comment below.
On Thu, Feb 27, 2025, 1:20 AM Bruno Cadonna wrote:
> BC2:
> Another aspect that confuses me in the KIP is the bridge version for
> clients. If my broker version is 3.9.x, I can do a direct upgrade from
> 1.0.x to 4.0.x (let apart the Java API compatibility mentioned a
Thanks for the clarification Jose. Makes sense.
Ismael
On Wed, Feb 26, 2025 at 9:22 AM José Armando García Sancio
wrote:
> Hi Ismael,
>
> On Wed, Feb 26, 2025 at 7:51 AM Ismael Juma wrote:
> >
> > Hi Jose,
> >
> > Is it a low risk change? If not, I
Hi Jose,
Is it a low risk change? If not, I would suggest giving it a bit of
stabilization time before cherry-picking to older branches including 4.0
and 3.9. I don't think it's necessary to backport to other older branches
given that it's not a regression and I don't believe there are any cases o
Hi Jun,
When it comes to the upgrade documentation, a couple of changes landed
after the RC was generated:
*
https://github.com/apache/kafka/commit/da8f390c4599d7199c4cdf2bb85441146e859b17
*
https://github.com/apache/kafka/commit/da3b8e88dc61a1b749895866394cab68410e0eda
Regarding the message for
l? Sometimes, I list
> tickets for flaky (or unrelated) tests before merging. However, since we
> now have a separate test suite for stable tests (non-flaky, non-new), I
> assume the new condition is that "stable tests must pass"?
>
> Best,
> Chia-Ping
>
>
>
Thanks David - this is another important improvement to our CI pipeline and
is super helpful for the project and community.
Ismael
On Mon, Feb 24, 2025 at 2:15 PM David Arthur wrote:
> Hey everyone, just wanted to inform you all that we just merged KAFKA-18748
>
> https://github.com/apache/kafk
e/pages/viewpage.action?pageId=325421614#ReleasePlan4.0.0-OpenIssues
>
> Are we expecting another RC soon? Or can this vote pass and these
> Jiras are moved to 4.1.0?
>
> Thanks,
> Mickael
>
> On Sun, Feb 23, 2025 at 10:46 PM Ismael Juma wrote:
> >
> > Thanks
Thanks David! A few ideas of things to test:
1. Test clients and streams with Java 11: this is the first time we use a
different Java version for clients/streams vs the rest, so it would be good
to ensure the generated artifacts are good when it comes to this.
2. Similarly, test brokers and connec
For regular clients (producer, consumer, admin client), I think we should
describe this in the following way:
1. What's the minimum version to directly upgrade to 4.0? I suggest we go
with 2.1 - it's the same baseline set by KIP-896 and it's simpler to have
fewer version ranges to explain and worr
[
https://issues.apache.org/jira/browse/KAFKA-18601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-18601.
-
Resolution: Fixed
> Assume a baseline of 3.3 for server protocol versi
Thanks for the KIP, +1 (binding).
Ismael
On Wed, Feb 12, 2025 at 6:16 AM David Arthur wrote:
> Hey folks, I'd like to start the vote on this KIP to enable the merge queue
> for Kafka.
>
> The discussion thread is here:
> https://lists.apache.org/thread/c446mf4bg0ocjgs6do9lltoc2f13r71m
>
> --
>
Ismael Juma created KAFKA-18784:
---
Summary: Fix ConsumerWithLegacyMessageFormatIntegrationTest
Key: KAFKA-18784
URL: https://issues.apache.org/jira/browse/KAFKA-18784
Project: Kafka
Issue Type
quot;Reviewers" field before merging. It might also be possible to
> automatically set that field.
>
> I have a feeling it might be possible to alter the commit message in the
> merge queue job, but that will take some experimentation.
>
> -David A
>
> On Tue, Feb 4, 2025 at
This looks good to me.
My only comment is that merge queues have a weird limitation: you cannot
edit the commit message (unlike the traditional flow). I worry that this
will result in lower quality commit messages. Is there a way to configure
where the commit message comes from (PR title/descripti
[
https://issues.apache.org/jira/browse/KAFKA-15318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-15318.
-
Resolution: Fixed
> Update the Authorizer using AclPublis
[
https://issues.apache.org/jira/browse/KAFKA-15048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-15048.
-
Resolution: Fixed
> Improve handling of unexpected quorum controller err
[
https://issues.apache.org/jira/browse/KAFKA-15271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-15271.
-
Resolution: Fixed
> Historicalterator can exposes elements that are too
[
https://issues.apache.org/jira/browse/KAFKA-15458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-15458.
-
Resolution: Fixed
> Fully resolve endpoint information before registering controll
[
https://issues.apache.org/jira/browse/KAFKA-18663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-18663.
-
Resolution: Fixed
> Metadata v0-v3 should be undepreca
727
Ismael
[1] https://issues.apache.org/jira/browse/KAFKA-18659
On Sun, Dec 17, 2023 at 7:40 AM Ismael Juma wrote:
> Hi all,
>
> It turns out that kafka-python's protocol api versions support is worse
> than originally described - newer versions were defined but not actually
> su
Ismael Juma created KAFKA-18663:
---
Summary: Metadata v0-v3 should be undeprecated
Key: KAFKA-18663
URL: https://issues.apache.org/jira/browse/KAFKA-18663
Project: Kafka
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/KAFKA-18648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-18648.
-
Resolution: Fixed
> kafka-python requires metadata request versio
Ismael Juma created KAFKA-18648:
---
Summary: kafka-python requires metadata request version 1
Key: KAFKA-18648
URL: https://issues.apache.org/jira/browse/KAFKA-18648
Project: Kafka
Issue Type
Ismael Juma created KAFKA-18646:
---
Summary: Empty records representation regression breaks librdkafka
Key: KAFKA-18646
URL: https://issues.apache.org/jira/browse/KAFKA-18646
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-18474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-18474.
-
Resolution: Fixed
> Remove zkBroker tag
> ---
>
>
[
https://issues.apache.org/jira/browse/KAFKA-18599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-18599.
-
Resolution: Fixed
> Remove optional ForwardingManager in ApiVersionMana
[
https://issues.apache.org/jira/browse/KAFKA-14552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-14552.
-
Resolution: Fixed
> Assume a baseline of 3.0 for server protocol versi
Thanks for the KIP - one suggestion I have is to perhaps separate the long
term policy (which will naturally require a lot more debate) and what we
plan to do for 4.0.
Why is the long term policy more complicated? Because it is trying to
predict the future (Matthias made a comment regarding how 2.
[
https://issues.apache.org/jira/browse/KAFKA-18578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-18578.
-
Resolution: Fixed
> Remove UpdateMetadataRequest in MetadataCacheT
[
https://issues.apache.org/jira/browse/KAFKA-18593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-18593.
-
Resolution: Fixed
> Remove ZkCachedControllerId In MetadataCa
Ismael Juma created KAFKA-18601:
---
Summary: Assume a baseline of 3.3 for server protocol versions
Key: KAFKA-18601
URL: https://issues.apache.org/jira/browse/KAFKA-18601
Project: Kafka
Issue
[
https://issues.apache.org/jira/browse/KAFKA-18366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-18366.
-
Resolution: Duplicate
This being tackled via KAFKA-18360
> Rem
[
https://issues.apache.org/jira/browse/KAFKA-17668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-17668.
-
Fix Version/s: 4.0.0
Resolution: Fixed
> Rewrite LogCleaner#maxOverCleanerThreads
[
https://issues.apache.org/jira/browse/KAFKA-18427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-18427.
-
Fix Version/s: 4.0.0
Resolution: Fixed
> Remove ZooKeeperCli
[
https://issues.apache.org/jira/browse/KAFKA-18540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-18540.
-
Resolution: Fixed
> Remove UpdataMetadataRequest in KafkaApisT
[
https://issues.apache.org/jira/browse/KAFKA-18532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-18532.
-
Resolution: Fixed
> Clean Partition.scala zookeeper lo
[
https://issues.apache.org/jira/browse/KAFKA-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-18423.
-
Resolution: Fixed
> Remove ZkData and related unused referen
[
https://issues.apache.org/jira/browse/KAFKA-18514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-18514.
-
Resolution: Fixed
> Refactor share module to server and server-com
[
https://issues.apache.org/jira/browse/KAFKA-18431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-18431.
-
Resolution: Fixed
> Remove KafkaController
> --
>
>
[
https://issues.apache.org/jira/browse/KAFKA-18472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-18472.
-
Fix Version/s: 4.0.0
Resolution: Fixed
> Remove MetadataSupp
[
https://issues.apache.org/jira/browse/KAFKA-18552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-18552.
-
Resolution: Fixed
> Remove unnecessary version check from KafkaApisT
[
https://issues.apache.org/jira/browse/KAFKA-18331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-18331.
-
Resolution: Fixed
> Update process.roles to required configurat
[
https://issues.apache.org/jira/browse/KAFKA-7769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-7769.
Resolution: Cannot Reproduce
Very old issue and I don't think anyone has run into this for
[
https://issues.apache.org/jira/browse/KAFKA-8532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-8532.
Resolution: Won't Fix
ZK support has been removed.
> controller-event-thread deadlock
[
https://issues.apache.org/jira/browse/KAFKA-12941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-12941.
-
Resolution: Fixed
This was resolved a while back.
> Remove excluded Streams tests when runn
[
https://issues.apache.org/jira/browse/KAFKA-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-2605.
Resolution: Won't Fix
Scala is being replaced with Java, so this is unlikely to get done
[
https://issues.apache.org/jira/browse/KAFKA-7614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-7614.
Resolution: Fixed
This was done a while back.
> Fix scalac warnings and enable warnings as err
[
https://issues.apache.org/jira/browse/KAFKA-7062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-7062.
Resolution: Fixed
The old MirrorMaker has been removed.
> Simplify MirrorMaker loop after remo
[
https://issues.apache.org/jira/browse/KAFKA-6330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-6330.
Resolution: Won't Fix
ZK support is removed in 4.0.
> KafkaZkClient request queue tim
[
https://issues.apache.org/jira/browse/KAFKA-4513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-4513.
Resolution: Won't Fix
No-one uses the scala consumer at this point.
> Support migratio
[
https://issues.apache.org/jira/browse/KAFKA-5883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-5883.
Resolution: Fixed
Java changed the default, so this was effectively done.
> Run tests on Jav
[
https://issues.apache.org/jira/browse/KAFKA-4487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-4487.
Resolution: Won't Fix
Marking as "Won't fix" since it's been a long ti
[
https://issues.apache.org/jira/browse/KAFKA-9333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-9333.
Resolution: Won't Fix
We'll instead rely on the `kafka-server` module for Java code and
[
https://issues.apache.org/jira/browse/KAFKA-12942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-12942.
-
Resolution: Fixed
This was resolved a while back.
> Remove excluded Connect tests when runn
[
https://issues.apache.org/jira/browse/KAFKA-13274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-13274.
-
Resolution: Fixed
> Ensure system tests run successfully with Java
[
https://issues.apache.org/jira/browse/KAFKA-10444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-10444.
-
Resolution: Fixed
> Migrate PR jobs to new Apache Infra Jenk
Ismael Juma created KAFKA-18465:
---
Summary: Remove MetadataVersion methods for versions older than 3.0
Key: KAFKA-18465
URL: https://issues.apache.org/jira/browse/KAFKA-18465
Project: Kafka
1 - 100 of 4197 matches
Mail list logo
