Divij Vaidya created KAFKA-18766:
Summary: Docs: Make usage of allow.everyone.if.no.acl.found config
clearer
Key: KAFKA-18766
URL: https://issues.apache.org/jira/browse/KAFKA-18766
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-16368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Divij Vaidya resolved KAFKA-16368.
--
Resolution: Fixed
> Change constraints and default values for various configurations - par
Divij Vaidya created KAFKA-18742:
Summary: Change constraints and default values for various
configurations - part 2
Key: KAFKA-18742
URL: https://issues.apache.org/jira/browse/KAFKA-18742
Project
[
https://issues.apache.org/jira/browse/KAFKA-18570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Divij Vaidya resolved KAFKA-18570.
--
Resolution: Fixed
> Update documemtation for log loading metrics during Kafka broker star
[
https://issues.apache.org/jira/browse/KAFKA-18570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Divij Vaidya reopened KAFKA-18570:
--
> Update documemtation for log loading metrics during Kafka broker star
[
https://issues.apache.org/jira/browse/KAFKA-18570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Divij Vaidya resolved KAFKA-18570.
--
Resolution: Won't Fix
> Add progress metric for log loading during Kafka broker
Divij Vaidya created KAFKA-18624:
Summary: Add validation for advertised listeners
Key: KAFKA-18624
URL: https://issues.apache.org/jira/browse/KAFKA-18624
Project: Kafka
Issue Type
Divij Vaidya created KAFKA-18607:
Summary: Update jfreechart dependency
Key: KAFKA-18607
URL: https://issues.apache.org/jira/browse/KAFKA-18607
Project: Kafka
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/KAFKA-18568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Divij Vaidya resolved KAFKA-18568.
--
Resolution: Fixed
> Flaky test ClientIdQuotaT
Divij Vaidya created KAFKA-18568:
Summary: Flaky test ClientIdQuota
Key: KAFKA-18568
URL: https://issues.apache.org/jira/browse/KAFKA-18568
Project: Kafka
Issue Type: Test
FYI there is also some prior attempts for converting to markdown at
https://issues.apache.org/jira/browse/KAFKA-14815
Please feel free to take over that Jira and start a KIP.
--
Divij Vaidya
On Wed, Jan 15, 2025 at 2:57 AM Luke Chen wrote:
> Hi Harish,
>
> Thanks for the proposal.
[
https://issues.apache.org/jira/browse/KAFKA-18547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Divij Vaidya resolved KAFKA-18547.
--
Resolution: Fixed
> Failing test ClientUtilsT
Divij Vaidya created KAFKA-18547:
Summary: Failing test
ClientUtilsTest#testParseAndValidateAddressesWithReverseLookup in trunk
Key: KAFKA-18547
URL: https://issues.apache.org/jira/browse/KAFKA-18547
[
https://issues.apache.org/jira/browse/KAFKA-18434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Divij Vaidya resolved KAFKA-18434.
--
Resolution: Fixed
> enrich the authorization error message of connecting to control
[
https://issues.apache.org/jira/browse/KAFKA-18358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Divij Vaidya resolved KAFKA-18358.
--
Resolution: Fixed
> Replace Deprecated $buildDir variable in build.gra
tion
since the probability of risk will increase now. This is also the reason I
do not want users to set throttling below a certain threshold (and hence,
introduce a lower bound).
--
Divij Vaidya
On Thu, Dec 26, 2024 at 3:53 PM Harry Fallows
wrote:
> Hi Kamal,
>
> Apologies for the ver
goal worth pursuing.
--
Divij Vaidya
On Fri, Jan 3, 2025 at 4:39 AM TaiJu Wu wrote:
> Hello folk,
>
> This thread is pending for a long time, I want to bump this thread and get
> more feedback.
> Any questions are welcome.
>
> Best,
> TaiJuWu
>
> TaiJu Wu 於 2024年11月
be part of canary brokers or not? How will we
test code regression in controller? Similarly how will we test code
regression in transaction coordinator and consumer coordinator?
—
Divij Vaidya
On Fri, Jan 3, 2025 at 7:41 AM Chen Zhifeng
wrote:
> Hi Everyone,
>
> Started a thread to disc
on of folks (perhaps include users@ list and have a
new subject line for the discussion).
Greg, would you be willing to kick-off that discussion? We can park this
thread until we conclude on the end of life story for 3.9.x.
--
Divij Vaidya
On Tue, Dec 17, 2024 at 4:11 AM Luke Chen wrote:
>
Divij Vaidya created KAFKA-18268:
Summary: Add metric for log cleaner thread busy percentage
Key: KAFKA-18268
URL: https://issues.apache.org/jira/browse/KAFKA-18268
Project: Kafka
Issue Type
Divij Vaidya created KAFKA-18266:
Summary: Re-order validation for TimeIndex sanity
Key: KAFKA-18266
URL: https://issues.apache.org/jira/browse/KAFKA-18266
Project: Kafka
Issue Type
--
Divij Vaidya
On Mon, Dec 16, 2024 at 9:25 AM David Jacot
wrote:
> Hi Chia-Ping,
>
> Regarding KAFKA-18225, I agree that it is an issue that we must fix in 4.0.
> I see that Colin's already commented in the Jira about the suggested way
> forward. I agree with the proposal.
>
&
There is a compatibility matrix for Zk versions available until v3.8 here -
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=240882784#KIP902:UpgradeZookeeperto3.8.2-Compatibility,Deprecation,andMigrationPlan
--
Divij Vaidya
On Tue, Dec 10, 2024 at 3:27 PM Chia-Ping Tsai
/KAFKA-17062? The former is a
good-to-have validation and the latter impacts data stored by Tiered
Storage which is not GA in 3.7. Hence, we do not need a new RC, but if we
do end up creating one for a different reason, let's backport these.
## Vote
+ 1 (binding)
--
Divij Vaidya
On Thu,
Divij Vaidya created KAFKA-18166:
Summary: Indefinite timeout when publishing events to RLMM
(RemoteLogMetadataManager)
Key: KAFKA-18166
URL: https://issues.apache.org/jira/browse/KAFKA-18166
Project
te the KIP with the above explanation.
Looking forward to hearing your thoughts.
--
Divij Vaidya
On Thu, Dec 5, 2024 at 4:01 AM Ismael Juma wrote:
> Hi Divij,
>
> The KIP didn't state this, but the usual practice is to have a deprecation
> period before we make incompati
The committer information is also publicly available in a json format at
https://whimsy.apache.org/public/public_ldap_projects.json
We can choose to parse the json to extract the committers. It won't require
any authentication to generate our file.
--
Divij Vaidya
On Wed, Dec 4, 2024
may be possible to query the API and get the information directly
from the source of truth. I haven't tried this approach but throwing out an
option out there.
--
Divij Vaidya
On Tue, Dec 3, 2024 at 9:51 PM Chia-Ping Tsai wrote:
> hi David,
>
> (I copy your response f
Hey David
Thank you for patiently waiting for KIP-1030 [1]. It is now accepted and I
have updated the release plan with the KIP.
[1]
https://cwiki.apache.org/confluence/display/KAFKA/KIP-1030%3A+Change+constraints+and+default+values+for+various+configurations
--
Divij Vaidya
On Tue, Nov 26
Thank you all for voting.
The KIP is now accepted with:
4 binding +1 (Luke, Kamal, Satish, Jun)
1 non-binding +1 (Federico)
No -1 or 0 votes
We will target 4.0 version for this KIP
--
Divij Vaidya
On Mon, Dec 2, 2024 at 6:51 PM Jun Rao wrote:
> Hi, Divij,
>
> Thanks for th
Jun
Do you have any final thoughts here? The vote thread has sufficient votes
to accept but I wanted to ensure that we don’t have any pending items to
discuss here.
—
Divij Vaidya
On Thu 28. Nov 2024 at 14:53, Divij Vaidya wrote:
> Agreed about the validation tool. I have already added
Agreed about the validation tool. I have already added it in the
"compatibility" section of the KIP. Will create a separate JIRA for it as
soon as KIP is approved.
--
Divij Vaidya
On Thu, Nov 28, 2024 at 5:35 AM Satish Duggana
wrote:
> Hi Kamal, Thanks for updating the KIP wit
Yes, Kamal, we will fix the tests that rely on low values of segment.ms as
part of the KIP implementation.
--
Divij Vaidya
On Wed, Nov 27, 2024 at 7:40 PM Jun Rao wrote:
> Hi, Kamal,
>
> Thanks for the explanation. This change sounds good to me then.
>
> Jun
>
> On We
Hello everyone
Since, I believe I have addressed all the concerns that were raised here, I
have started a vote thread for this KIP at
https://lists.apache.org/thread/39dmfkd7ktb0oo44yqrkndcn4kcqt5hc
Please participate in the vote.
--
Divij Vaidya
On Wed, Nov 27, 2024 at 12:33 PM Divij Vaidya
Corresponding discussion thread:
https://lists.apache.org/thread/kxw9kxn49kt30kwckzwp8vq3k7kmrz9m
Please vote if you agree with proceeding ahead with the proposal. Votes
from all community members are cordially invited.
--
Divij Vaidya
server.properties). Please let me know if I
have missed anything.
12. In the interest of time, I have removed the constraint proposal for rf
>= min.insync.replicas. We will circle back on it in a separate KIP.
*Luke*
10 and 12 above should align with what you suggested.
--
Divij Vaidya
On Wed, Nov
ation but based on my understanding of the Kafka code
base, I do believe that there is a path to implement this constraint. We
will cross that bridge during the implementation phase and I will ensure
that I look at the historical context you provided in the JIRA.
--
Divij Vaidya
On Sat, Nov 23,
he
thread pools based on machine size)
io threads = 2 x number of cores
network threads = number of cores
recovery threads = 2 x number of cores
If you have a strong opinion on this, I am also willing to remove these
config changes from this KIP. These are not as important as the rest of
them.
Based on initial feedback from the community, I don't anticipate
the discussion for KIP-1030 to go beyond 2 weeks. Will keep you posted.
--
Divij Vaidya
On Wed, Nov 20, 2024 at 11:03 AM David Jacot
wrote:
> Hi Divij,
>
> I think that we can make a small exception for KIP-1030
accepting more requests that brokers can handle, leading to
degradation. A constraint that network threads <= request handler threads
could prevent such scenario).
Earlier, I didn't add these since these are not dead-obvious changes
compared to the rest of the changes in the KIP, but I have no
A/KIP-1030%3A+Change+constraints+and+default+values+for+various+configurations
--
Divij Vaidya
On Wed, Nov 13, 2024 at 3:13 PM David Jacot
wrote:
> Hi all,
>
> This is a friendly reminder that the KIP freeze is on 20th November 2024,
> one week from today.
>
> Best,
> David
KT1 - That is right. We will throw a ConfigException. That is why this
change is considered backward incompatible. To be honest, given the nature
of suggested changes, I don't see any valid use case on why a user may have
a value which will be invalid after the new constraints.
--
Divij V
Hey folks
With 4.0, we have an opportunity to reset the default values and add
constraints in the configurations based on our learnings since 3.0.
Here's a KIP which modifies defaults for some properties and modifies the
constraints for a few others.
https://cwiki.apache.org/confluence/display/K
[
https://issues.apache.org/jira/browse/KAFKA-18003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Divij Vaidya resolved KAFKA-18003.
--
Resolution: Fixed
> add test to make sure `Admin#deleteRecords` can handle the corrup
[
https://issues.apache.org/jira/browse/KAFKA-17995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Divij Vaidya resolved KAFKA-17995.
--
Reviewer: Divij Vaidya
Resolution: Fixed
> Large value for `retention.ms` could prev
ix
this is 3.9.1?
--
Divij Vaidya
On Wed, Nov 13, 2024 at 2:28 PM Chia-Ping Tsai wrote:
> Thank you for your assistance, Bruno!
>
> Best,
> Chia-Ping
>
> Bruno Cadonna 於 2024年11月13日 週三 下午6:16寫道：
>
> > Hi Chia-Ping,
> >
> > I just uploaded the artifact
Divij Vaidya created KAFKA-17997:
Summary: Remove deprecated config
log.message.timestamp.difference.max.ms
Key: KAFKA-17997
URL: https://issues.apache.org/jira/browse/KAFKA-17997
Project: Kafka
Divij Vaidya created KAFKA-17995:
Summary: Large value for `retention.ms` could prevent remote data
cleanup in Tiered Storage
Key: KAFKA-17995
URL: https://issues.apache.org/jira/browse/KAFKA-17995
[
https://issues.apache.org/jira/browse/KAFKA-17924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Divij Vaidya resolved KAFKA-17924.
--
Resolution: Fixed
> Remove `bufferpool-wait-time-total`, `io-waittime-total`, and `iot
During the release process, we will document a "guidance for upgrade"
which will call out breaking changes per component.
For this proposal to be successful, all committers should be mindful of
adding the "breaking" label when closing a JIRA as resolved.
Thoughts?
--
Divij Vaidya
topic based RLMM would
continue to use the optimization you authored in the PR)
Thoughts?
--
Divij Vaidya
On Mon, Nov 4, 2024 at 3:01 PM Divij Vaidya wrote:
> Thanks for patiently addressing all the comments.
>
> I will add the vote in the other thread.
>
> --
> Divij Vai
+1
(I have participated in the review and I think we have a good solution in
the KIP)
--
Divij Vaidya
On Mon, Nov 4, 2024 at 5:41 AM Kamal Chandraprakash <
kamal.chandraprak...@gmail.com> wrote:
> Hi all,
>
> Bumping up the voting thread.
>
> On Mon, Sep 30, 2024 at 3:27
Thanks for patiently addressing all the comments.
I will add the vote in the other thread.
--
Divij Vaidya
On Mon, Nov 4, 2024 at 5:40 AM Kamal Chandraprakash <
kamal.chandraprak...@gmail.com> wrote:
> Hi all,
>
> If the review comments are addressed and KIP looks good, ple
/core/src/main/java/kafka/log/remote/RemoteLogManager.java#L1801
. Is there a case where the parameter "offset" will not be equal to the
baseOffset of a segment?
--
Divij Vaidya
On Fri, Nov 1, 2024 at 10:26 AM Kamal Chandraprakash <
kamal.chandraprak...@gmail.com> wrote:
>
of 20th Nov).
--
Divij Vaidya
On Wed, Oct 30, 2024 at 12:46 PM Tommi Vainikainen
wrote:
> Hi,
>
> I've noticed that similar to these already mentioned settings also
> segment.index.bytes has a minimum value of 4. This conflicts with
> Offse
file and storing them in memory,
when we have a non-empty index.
The other option (preferred) is to add an isEmpty() public method to the
TransactionIndex and perform a segment.txnIndex().isEmpty() check which
will internally use Files.size() java API.
On Tue, Oct 29, 2024 at 1:21 PM Divij Vaidya
.
> >> > > > >>>
> >> > > > >>> From the UnifiedLog.scala
> >> > > > >>> <
> >> > > >
> >> > >
> >> >
> >>
> https://sourcegraph.com/github.com/apache/kafka@trunk/-/blob/core/src/main
world.
I am ok with adding a note in the KIP but the note should say that it has
an elevated risk for this scenario due to increased probability of having
an aggressive local cleanup with Tiered Storage.
--
Divij Vaidya
On Wed, Jul 24, 2024 at 1:22 PM Abhijeet Kumar
wrote:
> Hi Divij,
>
gt; available anymore, the follower will eventually be able to catch up with
> the leader by resetting its fetch offset until the offset
> is available on the leader's local log. Once it catches up, replication on
> the follower can proceed.
>
> Regards,
> Abhijeet.
>
>
>
te to respond to
the follower. The amount of this data can be controlled via the configured
value Z which can be set based on how aggressive the upload/archival
process is.
--
Divij Vaidya
On Tue, Jul 2, 2024 at 12:25 PM Divij Vaidya
wrote:
> Hi folks.
>
> I am late to the party bu
OffsetMovedToTieredException
3. Follower builds aux state from [0-10] and sets the fetch offset to 11
4. But leader has already uploaded more data and now the new
last-tiered-offset is 15
5. Go back to 2
This could cause a cycle where the replica will be stuck trying to
reconcile with the leader.
--
Divij Vaidya
On Fri
+1 (binding)
I have participated in the discussion and agree with the proposal.
--
Divij Vaidya
On Thu, Jun 27, 2024 at 12:56 PM Satish Duggana
wrote:
> Thanks Federico for the KIP.
>
> +1
>
> ~Satish.
>
> On Thu, 27 Jun 2024 at 13:44, Federico Valeri
> wrote:
>
Thank you Federico for answering the questions. No more questions/concerns
from me. The KIP looks good.
--
Divij Vaidya
On Wed, Jun 26, 2024 at 11:02 AM Federico Valeri
wrote:
> Hi Divij, thanks for you questions and suggestions, much appreciated.
>
> On Tue, Jun 25, 2024 at 1:12
ecify a particular schema version?
--
Divij Vaidya
On Thu, Jun 20, 2024 at 5:57 PM Kamal Chandraprakash <
kamal.chandraprak...@gmail.com> wrote:
> Hi Federico,
>
> Thanks for the KIP! +1 from me.
>
> On Wed, Jun 19, 2024, 17:36 Luke Chen wrote:
>
> > Hi Federico,
&
ve to
iterate through the metadata for the dominant case where the partition had
no transactions at all.
--
Divij Vaidya
On Tue, Jun 25, 2024 at 11:42 AM Kamal Chandraprakash <
kamal.chandraprak...@gmail.com> wrote:
> Bump. Please review this proposal.
>
>
> On Mon, Jun 17
oposed API take "segmentId" as a parameter instead of
"topicIdPartition"? Suggesting because isTxnIdEmpty is not a property of a
partition, instead it's a property of a specific segment.
Looking forward to hearing your thoughts about the alternatives. Let's get
this f
cer buffer) but
we have started recording end-to-end latency for the steady-state messages.
I imagine this should be ok because it achieves the purpose of
removing bootstrap times, but I haven't been able to reason about it in my
head. What are your thoughts on this?
--
Divij Vaidya
On Fr
ibility will be delegated to the decoder class which the
operator can define using the flag "--value-decoder-class".
Is there a reason that you are unable to use the rejected solution (which
requires no changes) for debugging purposes?
--
Divij Vaidya
On Sat, Jun 15, 2024 at 4:43 PM Federico
approach (and other alternatives) to
solve this issue?
—
Divij Vaidya
On Thu 16. May 2024 at 22:15, Jorge Esteban Quilcate Otoya <
quilcate.jo...@gmail.com> wrote:
> Thanks Justine. I have updated the KIP with the configuration details.
>
> On Thu, 16 May 2024 at 21:14, Justine Ol
,
just to get a better aligned conventional does not seem worthwhile to me.
Is there an obvious benefit that I am missing here which would make this
proposal a good trade off with the cost?
—
Divij Vaidya
On Thu 6. Jun 2024 at 21:13, Eric Lu wrote:
> Hi,
>
> I wanted to follow-
Congratulations Greg!
--
Divij Vaidya
On Sun, Apr 14, 2024 at 6:39 AM Kamal Chandraprakash <
kamal.chandraprak...@gmail.com> wrote:
> Congratulations, Greg!
>
> On Sun, Apr 14, 2024 at 8:57 AM Yash Mayya wrote:
>
> > Congrats Greg!
> >
> > On Sun, 14 Ap
Hey Manikumar
Are we planning to add the blog entry about the 3.6.2 release at
https://kafka.apache.org/blog ? Asking because I didn't see this included
in the release announcement.
--
Divij Vaidya
On Wed, Mar 20, 2024 at 12:01 PM Manikumar
wrote:
> Hi,
>
> We have one non-bl
zstd)
Things look good to me. We don't need another RC for fixing docs.
+1 (binding) from me.
--
Divij Vaidya
On Thu, Apr 4, 2024 at 10:04 AM Manikumar wrote:
> Hi Justine,
>
> Thanks for catching this. looks like we have missed updating
> `docs/documentation.html` in kafka re
.1%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC
--
Divij Vaidya
On Thu, Mar 14, 2024 at 7:55 AM Manikumar wrote:
> Hi all,
>
> Here is the release plan for 3.6.2:
> https://cwiki.apache.org/confluence/display/KAFKA/Release+plan+3.6.2
>
> Currently there is one open non-
+1
Thank you for volunteering.
--
Divij Vaidya
On Wed, Mar 13, 2024 at 4:58 PM Justine Olshan
wrote:
> Thanks Manikumar!
> +1 from me
>
> Justine
>
> On Wed, Mar 13, 2024 at 8:52 AM Manikumar
> wrote:
>
> > Hi,
> >
> > I'd like to volunteer
adjusted. Please reply in this
thread directly.
--
Divij Vaidya
Apache Kafka PMC
On Wed, Mar 13, 2024 at 12:56 PM Divij Vaidya
wrote:
> Thanks for the discussion folks. I have started a KIP
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-1030%3A+Change+constraints+and+default+valu
once it is ready to be
published, we can start a discussion thread on it.
I am also going to start a thread to solicit feedback from users@ mailing
list as well.
--
Divij Vaidya
On Wed, Mar 13, 2024 at 12:55 PM Christopher Shannon <
christopher.l.shan...@gmail.com> wrote:
> I thi
Divij Vaidya created KAFKA-16368:
Summary: Change constraints and default values for various
configurations
Key: KAFKA-16368
URL: https://issues.apache.org/jira/browse/KAFKA-16368
Project: Kafka
t want to work
with a segment.ms of less than ~10s (number chosen arbitrary that looks
sane)
What was the historical context of setting the minimum threshold to 1ms for
this setting?
[1] https://kafka.apache.org/documentation.html#topicconfigs_segment.ms
--
Divij Vaidya
[
https://issues.apache.org/jira/browse/KAFKA-16126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Divij Vaidya resolved KAFKA-16126.
--
Resolution: Fixed
> Kcontroller dynamic configurations may fail to apply at star
. You can either create a KIP
offline and share it in the discussion email or I can create the KIP page
on your behalf and copy/paste the content that you send to me.
--
Divij Vaidya
On Thu, Mar 7, 2024 at 5:15 PM Arpit Goyal wrote:
> + @Kamal Chandraprakash @Vaidya, Divij
> Can you h
Divij Vaidya created KAFKA-16325:
Summary: Add missing producer metrics to documentation
Key: KAFKA-16325
URL: https://issues.apache.org/jira/browse/KAFKA-16325
Project: Kafka
Issue Type
ful changes in this release but the one closest to my
heart is https://issues.apache.org/jira/browse/KAFKA-15046. I am very glad
this is fixed. The P999 latency spikes were driving me crazy for a long
time now.
--
Divij Vaidya
On Wed, Feb 28, 2024 at 10:06 AM Satish Duggana
wrote:
> Thanks Sta
ntral (mvnrepository.com or maven.org)."
in the release process wiki.
--
Divij Vaidya
On Tue, Feb 27, 2024 at 4:43 PM Stanislav Kozlovski
wrote:
> Hey all,
>
> Everything site-related is merged.
>
> I have been following the final steps of the release process.
> - Docker
Thank you for volunteering Josep. +1 from me.
--
Divij Vaidya
On Tue, Feb 27, 2024 at 9:35 AM Bruno Cadonna wrote:
> Thanks Josep!
>
> +1
>
> Best,
> Bruno
>
> On 2/26/24 9:53 PM, Chris Egerton wrote:
> > Thanks Josep, I'm +1 as well.
> >
> >
Hey Vaibhav
I have provided you with contributor permission to the JIRA. You should be
able to assign the JIRA to yourself now.
--
Divij Vaidya
On Sun, Feb 25, 2024 at 12:23 AM Vaibhav Kushwaha
wrote:
> Hi team!
>
> I was going through the list of starter bugs and found one I coul
e your PRs
on kafka-site repo get merged.
4. Send a release announcement by email.
--
Divij Vaidya
On Tue, Feb 20, 2024 at 3:02 PM Stanislav Kozlovski
wrote:
> Thanks for testing the release! And thanks for the review on the
> documentation. Good catch on the license too.
>
> I have
kafka binaries.
I am +1 (binding) assuming Mickael's concerns about update notes to 3.7 are
addressed before release.
--
Divij Vaidya
On Mon, Feb 19, 2024 at 6:08 PM Mickael Maison
wrote:
> Hi,
>
> I agree with Josep, I don't think it's worth making a new RC j
Divij Vaidya created KAFKA-16278:
Summary: Missing license for scala related dependencies
Key: KAFKA-16278
URL: https://issues.apache.org/jira/browse/KAFKA-16278
Project: Kafka
Issue Type
test results
Test: Spot check the results of system tests.
Result: I have verified that the system tests are passing across different
runs.
--
Divij Vaidya
On Sun, Feb 18, 2024 at 2:50 PM Stanislav Kozlovski
wrote:
> The latest system test build completed successfully -
>
> https
[
https://issues.apache.org/jira/browse/KAFKA-16239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Divij Vaidya resolved KAFKA-16239.
--
Resolution: Fixed
> Clean up references to non-existent IntegrationTestHel
[
https://issues.apache.org/jira/browse/KAFKA-14041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Divij Vaidya resolved KAFKA-14041.
--
Resolution: Fixed
> Avoid the keyword var for a variable declaration in ConfigTransfor
Divij Vaidya created KAFKA-16239:
Summary: Clean up references to non-existent IntegrationTestHelper
Key: KAFKA-16239
URL: https://issues.apache.org/jira/browse/KAFKA-16239
Project: Kafka
Sounds good. I am onboard to start with first steps and eventually move
towards a place where compression codec settings are more generic /
pluggable.
--
Divij Vaidya
On Wed, Feb 7, 2024 at 3:40 PM Mickael Maison
wrote:
> Hi Divij,
>
> Thanks for bringing that point. After reading K
compression controls in Kafka?
It might be beneficial to have a joint proposal of these two KIPs which may
satisfy both use cases.
--
Divij Vaidya
On Wed, Feb 7, 2024 at 11:14 AM Mickael Maison
wrote:
> Hi,
>
> I'm resurrecting this old thread as this KIP would be a nice
> improve
ed+Storage+Early+Access+Release+Notes
--
Divij Vaidya
On Thu, Jan 11, 2024 at 1:03 PM Luke Chen wrote:
> Hi all,
>
> There is a bug KAFKA-16101
> <https://issues.apache.org/jira/browse/KAFKA-16101> reporting that "Kafka
> cluster will be unavailable during KRaft migrat
[
https://issues.apache.org/jira/browse/KAFKA-9693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Divij Vaidya resolved KAFKA-9693.
-
Resolution: Fixed
This performance regression where producer snapshot fsync leads to high P99
[
https://issues.apache.org/jira/browse/KAFKA-16210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Divij Vaidya resolved KAFKA-16210.
--
Resolution: Fixed
> Upgrade jose4j to 0.9.4
> ---
>
>
Divij Vaidya created KAFKA-16210:
Summary: Upgrade jose4j to 0.9.4
Key: KAFKA-16210
URL: https://issues.apache.org/jira/browse/KAFKA-16210
Project: Kafka
Issue Type: Improvement
+1 (binding)
I have participated in the discussion for this and looked at the most
recent version of this KIP. It looks good to me.
--
Divij Vaidya
On Tue, Jan 23, 2024 at 8:17 AM David Jacot
wrote:
> Hi Chris, Ziming,
>
> Thanks for the clarification. I am glad that it does not i
1 - 100 of 437 matches
Mail list logo
