Hi Colin and Chia, thank you for your feedback.
Currently we have only reload4j binding dependency, and we
can continue with the same. I have updated kip with only reload4j, and
removed all other providers.
And if users have a different slf4j provider, they can continue to keep it
in the classpath
> Muralidhar Basani 於 2024年9月15日 晚上9:02 寫道：
>
> With this, I think, users don't have to make any explicit changes in their
> code, if their provider is reload4j. And if it's a different provider (like
> logback, log4j), they would have to upgrade that to match it with slf4j.
If upgrading the m
[
https://issues.apache.org/jira/browse/KAFKA-16027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
TengYao Chi resolved KAFKA-16027.
-
Assignee: TengYao Chi (was: Alexander Aghili)
Resolution: Resolved
> Refactor MetadataTes
Chia-Ping Tsai created KAFKA-17555:
--
Summary: uncomment all checks of
testCommonNameLoggingTrustManagerMixValidAndInvalidCertificates
Key: KAFKA-17555
URL: https://issues.apache.org/jira/browse/KAFKA-17555
Hello everyone,
I hope this message finds you well.
As the vote has been pending for two weeks, I would like to push it
manually.
Thank you for your attention.
Sincerely,
TengYao
Andrew Schofield 於 2024年8月27日 週二 下午10:20寫道：
> Thanks for the KIP.
>
> +1 (non-binding)
>
> Andrew
>
> > On 27 Aug 2
Bumping this thread for vote. PTAL.
On Mon, Sep 9, 2024 at 2:01 PM Kamal Chandraprakash <
kamal.chandraprak...@gmail.com> wrote:
> Hi all,
>
> I'd like to open voting for KIP-1058. This KIP improves the consumer
> reading from remote storage when READ_COMMITTED isolation level is enabled.
> PTAL.
