[
https://issues.apache.org/jira/browse/KAFKA-16719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sushant Mahajan resolved KAFKA-16719.
-
Resolution: Fixed
> Add AdminClient.deleteShareGroups
>
Sanskar Jhajharia created KAFKA-19024:
-
Summary: Enhance the client behaviour when it tries to exceed the
`group.share.max.group`s
Key: KAFKA-19024
URL: https://issues.apache.org/jira/browse/KAFKA-19024
A solution that involves a warning and classpath ordering doesn't meet the
bar for me. Good clarification though.
Ismael
On Thu, Mar 20, 2025 at 8:37 AM Farid Zakaria
wrote:
> AFAIR SLF4J you don't have to remove the other backends; merely make
> sure yours is first on the CLASSPATH list :P
> (
jlprat commented on PR #678:
URL: https://github.com/apache/kafka-site/pull/678#issuecomment-2741039302
Thanks @chia7712.
This thing was annoying me too much for some time now.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHu
Sean Quah created KAFKA-19023:
-
Summary: Snapshottable timers in the coordinator runtime
Key: KAFKA-19023
URL: https://issues.apache.org/jira/browse/KAFKA-19023
Project: Kafka
Issue Type: Improve
Hey Stan,
1. You're right, most of the broker-level configs shouldn't be modified,
such as thread pools, loggers, etc.. In all honesty, I was mainly thinking
of group and topic resources here. Overall I think cluster admins should be
able to restrict VC admins through ACLs. I think we should be ab
[
https://issues.apache.org/jira/browse/KAFKA-10161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-10161.
-
Resolution: Won't Fix
> Update Documentation
>
>
> Key: KAF
[
https://issues.apache.org/jira/browse/KAFKA-14542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-14542.
-
Resolution: Duplicate
Addressed by https://issues.apache.org/jira/browse/KAFKA-14560.
> Depreca
jlprat merged PR #678:
URL: https://github.com/apache/kafka-site/pull/678
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@kafka.apache.o
jlprat opened a new pull request, #678:
URL: https://github.com/apache/kafka-site/pull/678
Before the change:
After the change:
![Screen Shot 2025-03-20 at 17 21
1
José Armando García Sancio created KAFKA-19021:
--
Summary: Broker should not be allowed to be promoted to controller
Key: KAFKA-19021
URL: https://issues.apache.org/jira/browse/KAFKA-19021
AFAIR SLF4J you don't have to remove the other backends; merely make
sure yours is first on the CLASSPATH list :P
(SLF4J pre 2.0 would always emit a warning that it found 2+ StaticBinders)
Interestingly, you could still whatever backend (i.e. Log4J) and pipe
it through to another backend via anoth
Apoorv Mittal created KAFKA-19019:
-
Summary: Verify Share Fetch with Tiered Storage
Key: KAFKA-19019
URL: https://issues.apache.org/jira/browse/KAFKA-19019
Project: Kafka
Issue Type: Sub-task
Apoorv Mittal created KAFKA-19020:
-
Summary: Handle strict max fetch records in share fetch
Key: KAFKA-19020
URL: https://issues.apache.org/jira/browse/KAFKA-19020
Project: Kafka
Issue Type:
Apoorv Mittal created KAFKA-19018:
-
Summary: Send acquisition time in Share Fetch Response
Key: KAFKA-19018
URL: https://issues.apache.org/jira/browse/KAFKA-19018
Project: Kafka
Issue Type: S
Chirag Wadhwa created KAFKA-19017:
-
Summary: Change consumer-config to command-config in
verifiable_share_consumer.py
Key: KAFKA-19017
URL: https://issues.apache.org/jira/browse/KAFKA-19017
Project: K
[
https://issues.apache.org/jira/browse/KAFKA-18768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai reopened KAFKA-18768:
> Backport KAFKA-806 to 4.0
> -
>
> Key: KAFKA-18768
>
[
https://issues.apache.org/jira/browse/KAFKA-18768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai resolved KAFKA-18768.
Resolution: Duplicate
> Backport KAFKA-806 to 4.0
> -
>
>
[
https://issues.apache.org/jira/browse/KAFKA-18768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai resolved KAFKA-18768.
Resolution: Fixed
https://github.com/apache/kafka/commit/4dd893ba212d05fb2201d884d962f0c0f
chia7712 commented on PR #676:
URL: https://github.com/apache/kafka-site/pull/676#issuecomment-2739532707
@varunprakashnkl it seems this PR can include the change of #677, right?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub
hi Ismael
thanks for all your response.
> All that said, I am not actually sure we can do what I described above
while maintaining the compatibility required by a minor release.
Excuse me, are your concerns related to version matching, as discussed in
[0]? If so, I concur that this represents a
Hi,
I would like to draft a KIP and need access to Kafka confluence page.Could
someone please grant me permission?
https://cwiki.apache.org/confluence/display/kafka
My confluence username is "lansg".
Best regards,
Nick
[
https://issues.apache.org/jira/browse/KAFKA-17045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
PoAn Yang resolved KAFKA-17045.
---
Resolution: Duplicate
This will be covered by https://issues.apache.org/jira/browse/KAFKA-15599 with
Andrew Schofield created KAFKA-19016:
Summary: Validate retention behaviour of share groups
Key: KAFKA-19016
URL: https://issues.apache.org/jira/browse/KAFKA-19016
Project: Kafka
Issue Ty
24 matches
Mail list logo
