support+auto-join
> > >
> > > Discussion thread link:
> > > https://lists.apache.org/thread/ko478l71jf9hqhhg328tcdr46nj2wcz9
> > >
> > > Thanks,
> > > Kevin Wu
> > >
> >
>
--
David Arthur
David Arthur created KAFKA-19347:
Summary: AclControlManager unsafe state update
Key: KAFKA-19347
URL: https://issues.apache.org/jira/browse/KAFKA-19347
Project: Kafka
Issue Type: Bug
Thanks José,
+1 binding
-David A
On Mon, May 5, 2025 at 4:47 PM Alyssa Huang
wrote:
> Hey Jose,
>
> KIP looks good to me as well!
>
> On Mon, May 5, 2025 at 10:08 AM Jun Rao wrote:
>
> > Hi, Jose,
> >
> > Thanks for the KIP. +1
> >
> > Jun
> >
> > On Fri, May 2, 2025 at 8:42 AM José Armando G
David Arthur created KAFKA-19252:
Summary: Support broker and controller restarts in testkit
Key: KAFKA-19252
URL: https://issues.apache.org/jira/browse/KAFKA-19252
Project: Kafka
Issue Type
José, thanks for the updates. I think most of my questions have been
answered. I had just two more:
DA5: Do we have a way to quantify the metadata propagation latency? In the
past, I think we have eye-balled the metadata LEO between brokers and the
active controller to approximate the lag, but may
Hey José, thanks for the KIP!
If I understand correctly, the problem at hand is that the follower may
need a new HWM, but if there is no new data waiting it can take up to
MaxWaitMs. Having the follower report its HWM in the request seems like a
good approach.
DA1. It might be more clear if we ca
cutting the first RC.
>
> I just want to point to the email on the dev list with subject: `Kafka
> tags on repo`.
>
> It seems, our release scripts have some issue. David Arthur is actively
> investigation: https://issues.apache.org/jira/browse/KAFKA-19166
>
> Apparently s
ue, Apr 15, 2025 at 10:08 AM David Arthur wrote:
> Hi Jamie,
>
> All of our release tags are published to the apache/kafka GitHub repo. You
> can find them here https://github.com/apache/kafka/tags
>
> If you have cloned the apache/kafka GitHub repo, you can do "git fetch
David Arthur created KAFKA-19166:
Summary: Release tags are orphaned
Key: KAFKA-19166
URL: https://issues.apache.org/jira/browse/KAFKA-19166
Project: Kafka
Issue Type: Bug
po.
>
> Which repo should one be looking for to pick up the code by tag?
>
> https://github.com/apache/kafka/tree/4.0.0
> https://github.com/apache/kafka/tree/3.9.0
>
> Cheers,
> Jamie
>
--
David Arthur
Congrats!!
David Arthur
On Thu, Apr 10, 2025 at 12:43 TengYao Chi wrote:
> Thank you very much everyone!!
>
> I truly appreciate all your reviews, guidance, and discussions on my code
> contributions.
> Your feedback has been invaluable and has helped me grow as a developer.
&
Congrats, Apoorv!
David Arthur
On Thu, Apr 10, 2025 at 12:36 Jhen-Yung Hsu wrote:
> Congratulations Apoorv! Well deserved.
>
> On 2025/04/10 15:55:01 "Matthias J. Sax" wrote:
> > The Project Management Committee (PMC) for Apache Kafka is pleased to
> > announ
David Arthur created KAFKA-19013:
Summary: Pre-format PR body for merge queue
Key: KAFKA-19013
URL: https://issues.apache.org/jira/browse/KAFKA-19013
Project: Kafka
Issue Type: Sub-task
rkdown
> >>>>>
> >>>>
> >>>> Discussion thread:
> >>>>
> >>>> https://emea01.safelinks.protection.outlook.com/? url=https%3A%2F%
> 2Flists.apache.org
> %2Fthread%2Fkc0kg0dxy6xdrwyv10k56k6g058ng2dw&data=05%7C02%7C%7C940186c5945340391d7a08dd6cbf46dc%7C84df9e7fe9f640afb435%7C1%7C0%7C638786290955681824%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=%2FtrIYkj5dW48vAn4V2RkYHZcJulIsnBxRcfeM8avDYI%3D&reserved=0
> >>>> <https://lists.apache.org/thread/kc0kg0dxy6xdrwyv10k56k6g058ng2dw>
> >>>>
> >>>> Regards
> >>>> Harish
> >>>>
> >>>
> >
>
>
--
David Arthur
+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 are no objections, I'll start building the release plan in
>
David Arthur created KAFKA-19089:
Summary: Gradle :test task failing unexpectedly
Key: KAFKA-19089
URL: https://issues.apache.org/jira/browse/KAFKA-19089
Project: Kafka
Issue Type: Bug
his in
> > correctly (even if we try to automate it to the best extend possible).
> >
> > What actual problem are we solving?
> >
> >
> > -Matthias
> >
> > On 3/28/25 7:25 AM, Chia-Ping Tsai wrote:
> > > hi David
> > >
> > >> D
distinctions a bit
> subjective.
> > In my opinion, distinguishing between "approved-by" and "reviewed-by" is
> as
> > far as I would go.
> > Regarding the Jira trailer, I don't have any strong opinion, but it does
> > help in the cas
the
> "Signed-off-by" header already captured by git/GitHub on merge?
>
> Thanks,
> Kirk
>
> On Tue, Mar 25, 2025, at 5:06 PM, David Arthur wrote:
> > Hello Kafka community!
> >
> > I wanted to start a discussion around our Git commits and the metadata w
helps us move towards a fully automated process
where we populate these fields from the GitHub Pull Request data.
Let me know what you think!
David Arthur
[1] https://git-scm.com/docs/git-interpret-trailers
[
https://issues.apache.org/jira/browse/KAFKA-18776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Arthur reopened KAFKA-18776:
--
The flakiness has regressed
https://develocity.apache.org/scans/tests?search.relativeStartTime
[
https://issues.apache.org/jira/browse/KAFKA-18792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Arthur resolved KAFKA-18792.
--
Resolution: Fixed
> Enforce uniform PR structure for merge qu
David Arthur created KAFKA-19000:
Summary: Flaky test report should use absolute time for links
Key: KAFKA-19000
URL: https://issues.apache.org/jira/browse/KAFKA-19000
Project: Kafka
Issue
s:
> https://github.com/apache/kafka/actions/runs/13846870683
> > System tests:
> https://confluent-open-source-kafka-branch-builder-system-test-results.s3-us-west-2.amazonaws.com/trunk/2025-03-13--001.6a14e68a-4791-44eb-a6be-24ce25bc1678--1741882266--apache--4.0--8f765a1886/report.html
>
David Arthur created KAFKA-18968:
Summary: Workflow Requested not working for pull_request_reviewed
events
Key: KAFKA-18968
URL: https://issues.apache.org/jira/browse/KAFKA-18968
Project: Kafka
David Arthur created KAFKA-18965:
Summary: Improve release validation for kafka-clients
Key: KAFKA-18965
URL: https://issues.apache.org/jira/browse/KAFKA-18965
Project: Kafka
Issue Type
[
https://issues.apache.org/jira/browse/KAFKA-18845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Arthur reopened KAFKA-18845:
--
> Fail test QuorumControllerTest#testUncleanShutdownBrokerElrEnab
o direct pushes to trunk. If so, I understand now.
>
> Ismael
>
> On Thu, Mar 6, 2025 at 9:26 AM David Arthur wrote:
>
> > Sorry, let me clarify that point.
> >
> > There are two proposed rulesets (full details in the INFRA ticket):
> >
> > 1) No force pus
; > > > > > On Sat, Mar 1, 2025 at 3:01 PM Matthias J. Sax >
> > > > wrote:
> > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > > I am totally in favor to make this happen, and I was
&g
;
> * Require all changes to trunk to flow through a PR
>
>
> That's exactly the case Chia-Ping was asking about that you said is _not_
> expected.
>
> Ismael
>
>
> On Thu, Mar 6, 2025 at 8:01 AM David Arthur wrote:
>
> > Indeed, what I was trying to achiev
David Arthur created KAFKA-18942:
Summary: Add reviewers to PR body with committer-tools
Key: KAFKA-18942
URL: https://issues.apache.org/jira/browse/KAFKA-18942
Project: Kafka
Issue Type
David Arthur created KAFKA-18933:
Summary: Extract an interface from ClusterInstance for Java 11
modules
Key: KAFKA-18933
URL: https://issues.apache.org/jira/browse/KAFKA-18933
Project: Kafka
kes a good balance between safety and convenience, and is
a definite improvement over what we have now (which is no protections).
-David
On Thu, Mar 6, 2025 at 9:06 AM David Arthur wrote:
> Hm, this wasn't my intention with this change. I was expected two things
> to change:
>
> 1) PR
b.com:apache/kafka.git
> > ...
> >
> > Does this mean we must revert code via pull requests in the future?
> >
> > Best,
> > Chia-Ping
> >
> > On 2025/03/06 04:30:22 David Arthur wrote:
> > > Ok looks like Infra’s manual GitHub config change
>> work on improving the cache, so I'm wondering if this protection conflicts
>> with cache usage.
>>
>> Best,
>> Chia-Ping
>>
>> David Arthur 於 2025年3月6日 週四 上午4:07寫道：
>>
>> > We had a hiccup today where a PR was merged due to a fal
s as much as possible.
>
> For another, It seems we also require PRs to be up-to-date, which is good.
> However, the side effect is cache misses. I recall you've done a lot of
> work on improving the cache, so I'm wondering if this protection conflicts
> with cache usage.
>
vent forced pushing
to these branches which we honestly should have done long ago.
--
David Arthur
ng]
All of that grey is time saved thanks to caching. The builds with a solid
grey bar (all cache, no tests run) are docs changes. Neat!
-David A
On Wed, Feb 26, 2025 at 1:04 PM David Arthur wrote:
> Another thing that changed this week is the addition of a PR Linter. This
> is part of the
David Arthur created KAFKA-18921:
Summary: Low CPU utilization during streams integration tests
Key: KAFKA-18921
URL: https://issues.apache.org/jira/browse/KAFKA-18921
Project: Kafka
Issue
David Arthur created KAFKA-18903:
Summary: Use curl + jq in update-cache.sh
Key: KAFKA-18903
URL: https://issues.apache.org/jira/browse/KAFKA-18903
Project: Kafka
Issue Type: Improvement
David Arthur created KAFKA-18898:
Summary: 4.0 Upgrade docs rendering below other versions
Key: KAFKA-18898
URL: https://issues.apache.org/jira/browse/KAFKA-18898
Project: Kafka
Issue Type
reviewed and tag them with a special label so that volunteers with
> free cycles can easily find them. Plus, we might introduce a soft policy
> asking assigned reviewers to respond within a week if no one else has.
>
> Thanks,
> NB
>
--
David Arthur
, but this is the most
significant.
-David A
On Wed, Feb 26, 2025 at 12:59 PM David Arthur wrote:
> Sophie,
>
> > are tests automatically sorted into these buckets or do we have to
> manually move them
>
> This part hasn't changed -- we still need to manually mark tests
gt;> >
> >> > one small question:
> >> > Can we merge the PR if only flaky or new tests fail? Sometimes, I list
> >> > tickets for flaky (or unrelated) tests before merging. However, since
> we
> >> > now have a separate test suite for stable
ky, non-new), I
> > assume the new condition is that "stable tests must pass"?
> >
> > Best,
> > Chia-Ping
> >
> >
> >
> >
> > Ismael Juma 於 2025年2月25日 週二 上午6:24寫道：
> >
> > > Thanks David - this is another important imp
own files. For ex, the below
> > > would create a plain text version of all docs for 39/ branch., which
> can be
> > > packaged with the binary distribution.
> > >
> > > find docs/ -name "*.md" -type f | while read -r file; do
> > > dir=$(
Hey everyone, just wanted to inform you all that we just merged KAFKA-18748
https://github.com/apache/kafka/pull/18770
This splits our CI workflow into more parallel jobs which run subsets of
the tests with different settings. The JUnit tests are now split into
"new", "flaky", and the remainder.
.apache.org/confluence/display/KAFKA/KIP-1133%3A+AK+Documentation+and+Website+in+Markdown
> >
> detailing
> the proposal and would like to start discussions. Please take a look.
>
> Regards,
> Harish
>
--
David Arthur
[
https://issues.apache.org/jira/browse/KAFKA-18791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Arthur resolved KAFKA-18791.
--
Resolution: Fixed
> Set default commit message to PR title + b
Hey folks, just wanted to let you all know we have made a GitHub
configuration change for our PRs.
If you’ve ever wondered why the default commit message in GitHub PRs seems
to be kind of weird and arbitrary, you are not alone! Turns out the
“default” commit message for PRs is rather unintuitive a
On Sat, Feb 15, 2025 at 4:28 AM Kamal Chandraprakash <
kamal.chandraprak...@gmail.com> wrote:
> +1 (binding), Thanks for the KIP!
>
> --
> Kamal
>
> On Fri, Feb 14, 2025 at 10:25 AM Matthias J. Sax wrote:
>
> > +1 (binding)
> >
> > On 2/13/25 8:03 AM
cwiki.apache.org/confluence/display/KAFKA/KIP-1134%3A+Virtual+Clusters+in+Kafka
>
> Thanks,
> Viktor
>
--
David Arthur
David Arthur created KAFKA-18792:
Summary: Enforce uniform PR structure for merge queue
Key: KAFKA-18792
URL: https://issues.apache.org/jira/browse/KAFKA-18792
Project: Kafka
Issue Type: Sub
David Arthur created KAFKA-18791:
Summary: Set default commit message to PR title + body
Key: KAFKA-18791
URL: https://issues.apache.org/jira/browse/KAFKA-18791
Project: Kafka
Issue Type
Good point, Chris! The vote will remain open for another 2 days. I will
resend a vote summary if any additional votes are cast
David Arthur
On Thu, Feb 13, 2025 at 10:27 Chris Egerton wrote:
> Hi David,
>
> Isn't it a requirement that we leave KIP vote threads open for a m
vote is assumed to be binding
> > > only if it is from kafka committer. Your vote is definitely important
> to
> > > Kafka community, and I just try to explain the vote rule here.
> > >
> > > Best,
> > > Chia-Ping
> > >
> > > > Ukpa Uchechi 於 2025年2月13日 下午5:19 寫道：
> > > >
> > > > Uchechi
> > >
> >
>
--
David Arthur
David Arthur created KAFKA-18789:
Summary: GitHub Merge Queue
Key: KAFKA-18789
URL: https://issues.apache.org/jira/browse/KAFKA-18789
Project: Kafka
Issue Type: New Feature
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
--
David Arthur
David Arthur created KAFKA-18748:
Summary: Run new integration tests separately in PRs
Key: KAFKA-18748
URL: https://issues.apache.org/jira/browse/KAFKA-18748
Project: Kafka
Issue Type
this
> will result in lower quality commit messages. Is there a way to configure
> where the commit message comes from (PR title/description versus
> aggregating all the commit messages in the PR)?
>
> Ismael
>
> On Mon, Feb 3, 2025, 8:02 AM David Arthur wrote:
>
> &
Happy Monday, all!
I'd like to close out this discussion at some point this week, so I wanted
to bump this up once before moving to a vote.
Did anyone have other feedback or concerns about moving towards the GitHub
Merge Queue?
Thanks!
David A
On Thu, Jan 30, 2025 at 11:11 AM David A
echi.
>
> On Fri, 24 Jan 2025 at 03:35, David Arthur wrote:
>
> > Greetings, Kafka community!
> >
> > At long last, the GitHub Merge Queue is upon us. This is a feature that
> > many of us have wanted for quite a while. After many months of
> discussion,
>
che/kafka/connect/runtime/errors/RetryWithToleranceOperator.java#L282
> >
> > >
> > > thanks,
> > > Chia-Ping
> > >
> > > On 2025/01/26 11:08:59 Gaurav Narula wrote:
> > >> Hi Everyone,
> > >>
> > >> I'd like to initiate a discussion on KIP-1129: Update ConfigException
> > constructors at https://cwiki.apache.org/confluence/x/n4pEF.
> > >>
> > >> This KIP adds a constructor to ConfigException to accept a Throwable
> as
> > a second argument following the Java convention for Throwables and
> > deprecates the existing constructor that accepts an Object as the second
> > argument.
> > >>
> > >> Looking forward to hearing the community's feedback on this!
> > >>
> > >> Regards,
> > >> Gaurav
> >
> >
>
--
David Arthur
David Arthur created KAFKA-18657:
Summary: Flaky SharePartitionManagerTest
Key: KAFKA-18657
URL: https://issues.apache.org/jira/browse/KAFKA-18657
Project: Kafka
Issue Type: Test
[
https://issues.apache.org/jira/browse/KAFKA-18643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Arthur resolved KAFKA-18643.
--
Resolution: Won't Fix
Since this is a tagged field, we can't set a terminal versi
David Arthur created KAFKA-18643:
Summary: Set terminal version for
ApiVersionsResponse#ZkMigrationReady
Key: KAFKA-18643
URL: https://issues.apache.org/jira/browse/KAFKA-18643
Project: Kafka
vijvaidy...@gmail.com>
> > >> > >>>>>>>>>>>>>>>>>>>>>> wrote:
> > >> > >>>>>>>>>>>>>>>>>>>>>>
> > >> > >
22:06 Ukpa Uchechi wrote:
> >
> > > Hey David,
> > >
> > > Is the credentials for Confluent data center different from the one
> used
> > to
> > > access Apache Kafka jira?
> > >
> > > Best Regards.
> > >
> > >
KIP.
https://cwiki.apache.org/confluence/display/KAFKA/KIP-1126%3A+Serialize+changes+to+Kafka+with+build+queue
Please let me know what you think.
--
David Arthur
David Arthur created KAFKA-18636:
Summary: Javadoc failure not caught by CI
Key: KAFKA-18636
URL: https://issues.apache.org/jira/browse/KAFKA-18636
Project: Kafka
Issue Type: Bug
touched a wider range of modules?
>
> Hope that question makes sense. Probably I'm just ignorant of how the build
> cache works and what it can/can't do, so thanks in advance for bearing with
> me here.
>
> -Sophie
>
> On Wed, Jan 22, 2025 at 4:40 PM David Arthur wrot
> -Sophie
>
> On Fri, Jan 17, 2025 at 5:16 PM David Arthur wrote:
>
> > Thanks for raising the correctness aspect, José. We currently have a
> > compromise solution since PRs are not required to be up-to-date with
> trunk
> > before merging. Basically, as long
David Arthur created KAFKA-18617:
Summary: Support ClusterInstance in BeforeEach/AfterEach fixtures
Key: KAFKA-18617
URL: https://issues.apache.org/jira/browse/KAFKA-18617
Project: Kafka
of small cleanup/removal PRs for 4.0 which are easy to review
but take time to test and build (and re-build).
-David A
On Fri, Jan 17, 2025 at 4:30 PM José Armando García Sancio
wrote:
> Thanks David.
>
> On Fri, Jan 17, 2025 at 11:55 AM David Arthur wrote:
> >
> > I have
David Arthur created KAFKA-18581:
Summary: Allow sub-modules to use ClusterTest without core
dependency
Key: KAFKA-18581
URL: https://issues.apache.org/jira/browse/KAFKA-18581
Project: Kafka
Hey folks, I have a PR up that changes which commit we build in our PRs.
Currently, our PRs are building a synthetic "merge" commit which does not
actually exist in the repo. This is done by taking the base branch and
merging the PR into it. The benefit of this approach is that you will see
the re
[
https://issues.apache.org/jira/browse/KAFKA-17479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Arthur resolved KAFKA-17479.
--
Resolution: Fixed
This has been done for a while now
> Utilize Gradle build cache on Git
ny help is required.
> >
> >
> >
> > Thanks and Regards
> > Prashant Jagtap
> >
> >
> >
> >
> >
> > From: David Arthur
> > Sent: Tuesday, January 14, 2025 7:36 PM
> > To: dev@kafka.apache.org
> > Subject: [EXTERNAL] R
; >
> > Hi Team,
> >
> > Could you please give me the required permission in git so that the
> > workflow is triggered automatically when I create my PR?
> >
> > username:pramithas
> > email:dhakalpramit...@gmail.com
> >
> > Regards,
> > Pramithas Dhakal
>
--
David Arthur
s on Kafka jira
> board are already assigned to maintainers, i wanted to ask where a
> community member may find issues to work on,
>
> Issues available to the community.
>
> Thank you,
> Best regards
>
> On Tue, 14 Jan 2025 at 15:36, David Arthur wrote:
>
> >
here
https://github.com/apache/kafka/blob/trunk/.github/workflows/README.md#pr-triage
On Wed, Nov 20, 2024 at 8:25 PM Matthias J. Sax wrote:
> Nice!
>
> On 11/20/24 10:09 AM, David Arthur wrote:
> > Hey folks,
> >
> > I have raised a PR that adds the notion of "
;> -
> >>>
> >>>Static sites generated by Hugo are server-agnostic, simplifying
> >>>deployment.
> >>>-
> >>>
> >>>Improves local testing as well as CI testing
> >>>
> >>> To demonstrate the feasibility of this transition, I created a working
> >>> prototype of the Apache Kafka documentation using Hugo and Docsy.
> Please
> >>> take a look.
> >>>
> >>> - Prototype : https://kafka-site-md-711970345036.us-central1.run.app/.
> >>>
> >>> - Source code for the website:
> https://github.com/hvishwanath/kafka-site-md
> >>> . Specifically “content/en” directory shows the markdown source with
> some
> >>> refactoring for improved maintainability.
> >>>
> >>> - I wrote some automation to help with this:
> >>> https://github.com/hvishwanath/ak2md
> >>>
> >>>
> >>> I would love to hear your thoughts on this proposal.
> >>>
> >>> Cheers
> >>>
> >>> Harish
> >
>
--
David Arthur
low to assist with this
> process, please let us know—we’re more than happy to collaborate to make
> this happen.
> Looking forward to your positive response. Thank you for your
> consideration.
>
>
> Thanks and Regards
> Prashant Jagtap
>
>
--
David Arthur
David Arthur created KAFKA-18500:
Summary: Pull Requests not fully leveraging cache
Key: KAFKA-18500
URL: https://issues.apache.org/jira/browse/KAFKA-18500
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-18444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Arthur resolved KAFKA-18444.
--
Assignee: David Arthur
Resolution: Fixed
Fixed by disallowing 4.0 branch from updating
David Arthur created KAFKA-18444:
Summary: Test catalog not always capturing everything
Key: KAFKA-18444
URL: https://issues.apache.org/jira/browse/KAFKA-18444
Project: Kafka
Issue Type: Bug
David Arthur created KAFKA-18416:
Summary: Ensure we capture all flaky/failing tests in report
Key: KAFKA-18416
URL: https://issues.apache.org/jira/browse/KAFKA-18416
Project: Kafka
Issue
[
https://issues.apache.org/jira/browse/KAFKA-18307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Arthur resolved KAFKA-18307.
--
Resolution: Fixed
> Flaky test report includes disabled or removed te
gt;>
> >> De Gao
> >>
> >> On 1 December 2024 19:36:37 GMT, De Gao wrote:
> >> >Hi All:
> >> >
> >> >I would like to start the discussion of KIP-1114 Introducing Chunk in
> >> Partition.
> >> >
> >> >
> >>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-1114%3A+Introducing+Chunk+in+Partition
> >> >This KIP is complicated so I expect discussion will take longer time.
> >> >
> >> >Thank you in advance.
> >> >
> >> >De Gao
> >>
>
--
David Arthur
[
https://issues.apache.org/jira/browse/KAFKA-18036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Arthur resolved KAFKA-18036.
--
Resolution: Fixed
> TransactionsWithTieredStoreT
[
https://issues.apache.org/jira/browse/KAFKA-15920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Arthur resolved KAFKA-15920.
--
Resolution: Fixed
> Flaky test - PlaintextConsumerTest.testCoordinatorFailo
Hey folks!
Now that the 4.0 branch has been created, I think we need some focus on
stabilizing a few flaky tests. While it is a good practice to keep our
mainline branch as green as possible, I think it is especially important
for release branches to be green.
Here is a report of the current situ
David Arthur created KAFKA-18307:
Summary: Flaky test report includes disabled or removed tests.
Key: KAFKA-18307
URL: https://issues.apache.org/jira/browse/KAFKA-18307
Project: Kafka
Issue
[
https://issues.apache.org/jira/browse/KAFKA-17767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Arthur resolved KAFKA-17767.
--
Resolution: Fixed
> Capture tests run on trunk into test cata
[
https://issues.apache.org/jira/browse/KAFKA-17712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Arthur resolved KAFKA-17712.
--
Resolution: Fixed
> Run recently added integration tests in quarant
David Arthur created KAFKA-18271:
Summary: Trigger CI when a PR is marked "ready for review"
Key: KAFKA-18271
URL: https://issues.apache.org/jira/browse/KAFKA-18271
Project: Kafka
David Arthur created KAFKA-18238:
Summary: Identify the first commit where a test became flaky
Key: KAFKA-18238
URL: https://issues.apache.org/jira/browse/KAFKA-18238
Project: Kafka
Issue
David Arthur created KAFKA-18229:
Summary: Move configs out of "kraft" directory
Key: KAFKA-18229
URL: https://issues.apache.org/jira/browse/KAFKA-18229
Project: Kafka
Issue Type
David Arthur created KAFKA-18223:
Summary: Generate report from flaky test data
Key: KAFKA-18223
URL: https://issues.apache.org/jira/browse/KAFKA-18223
Project: Kafka
Issue Type: Sub-task
ned branch or trunk). There is
actually precedent for this in Apache Airflow
https://github.com/apache/airflow/blob/main/dev/breeze/src/airflow_breeze/global_constants.py#L437
Anyways, thanks for the pointers everyone :)
-David A
On Wed, Dec 4, 2024 at 1:22 PM David Arthur wrote:
> Thanks for
1 - 100 of 825 matches
Mail list logo
