[jira] [Created] (KAFKA-17079) scoverage plugin not found in maven repo, version 1.9.3

kaushik srinivas created KAFKA-17079: Summary: scoverage plugin not found in maven repo, version 1.9.3 Key: KAFKA-17079 URL: https://issues.apache.org/jira/browse/KAFKA-17079 Project: Kafka

Re: [VOTE] KIP-752: Support --bootstrap-server in ReplicaVerificationTool

Okay, Ismael's opinion seems reasonable, so I will follow it. Then, could you please assign me the deprecation issue & KIP? Since I opened this KIP in the past, I hope to wrap it up. If you are okay with it, I will close this issue & KIP and file the deprecation KIP instead. Thanks, Dongjin On T

[jira] [Resolved] (KAFKA-17069) Remote copy throttle metrics

[ https://issues.apache.org/jira/browse/KAFKA-17069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Chen resolved KAFKA-17069. --- Fix Version/s: 3.9.0 Resolution: Fixed > Remote copy throttle metrics >

[jira] [Reopened] (KAFKA-10370) WorkerSinkTask: IllegalStateException cased by consumer.seek(tp, offsets) when (tp, offsets) are supplied by WorkerSinkTaskContext

[ https://issues.apache.org/jira/browse/KAFKA-10370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Harris reopened KAFKA-10370: - Assignee: (was: Ning Zhang) > WorkerSinkTask: IllegalStateException cased by consumer.seek

Jenkins build is still unstable: Kafka » Kafka Branch Builder » trunk #3073

See

[jira] [Created] (KAFKA-17078) Add SecurityManager reflective shim

Greg Harris created KAFKA-17078: --- Summary: Add SecurityManager reflective shim Key: KAFKA-17078 URL: https://issues.apache.org/jira/browse/KAFKA-17078 Project: Kafka Issue Type: Task

[jira] [Created] (KAFKA-17077) the node.id is inconsistent to broker.id when "broker.id.generation.enable=true"

Chia-Ping Tsai created KAFKA-17077: -- Summary: the node.id is inconsistent to broker.id when "broker.id.generation.enable=true" Key: KAFKA-17077 URL: https://issues.apache.org/jira/browse/KAFKA-17077

Re: [PR] test 2: trying again [kafka-merge-queue-sandbox]

mumrah closed pull request #5: test 2: trying again URL: https://github.com/apache/kafka-merge-queue-sandbox/pull/5 -- 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 unsubscri

[PR] Test 4 [kafka-merge-queue-sandbox]

mumrah opened a new pull request, #7: URL: https://github.com/apache/kafka-merge-queue-sandbox/pull/7 (no comment) -- 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 unsubs

[PR] Test 3 [kafka-merge-queue-sandbox]

mumrah opened a new pull request, #6: URL: https://github.com/apache/kafka-merge-queue-sandbox/pull/6 (no comment) -- 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 unsubs

[jira] [Created] (KAFKA-17076) logEndOffset could be lost due to log cleaning

Jun Rao created KAFKA-17076: --- Summary: logEndOffset could be lost due to log cleaning Key: KAFKA-17076 URL: https://issues.apache.org/jira/browse/KAFKA-17076 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-17075) Use health check endpoint to verify Connect worker readiness in system tests

Chris Egerton created KAFKA-17075: - Summary: Use health check endpoint to verify Connect worker readiness in system tests Key: KAFKA-17075 URL: https://issues.apache.org/jira/browse/KAFKA-17075 Projec

[jira] [Resolved] (KAFKA-10816) Connect REST API should have a resource that can be used as a readiness probe

[ https://issues.apache.org/jira/browse/KAFKA-10816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton resolved KAFKA-10816. --- Fix Version/s: 3.9.0 Resolution: Done > Connect REST API should have a resource that

Jenkins build is still unstable: Kafka » Kafka Branch Builder » trunk #3072

See

Re: [VOTE] KIP-1022 Formatting and Updating Features

Hi, David, Thanks for the reply. In the common case, there is no difference between omitting just v0 of the feature or omitting the feature completely. It's just when an old client is used, there is some difference. To me, omitting just v0 of the feature seems slightly better for the old client.

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.8 #62

See

Re: [DISCUSS] KIP-1006: Remove SecurityManager Support

Hi Ismael, Thanks for the question. > Can we not > use the SecurityManager when it's available and fallback when it's not? This is the strategy the KIP is proposing in the interim before we drop support for the SecurityManager. The KIP should be stating this idea, just more verbosely. > I'm not

Re: [DISCUSS] KIP-1006: Remove SecurityManager Support

Hi Greg, Thanks for the KIP. I'm not totally clear on why we need a KIP. Can we not use the SecurityManager when it's available and fallback when it's not? If so, then it would mean that whether SecurityManager is used or not depends on the JDK and its configuration. Ismael On Mon, Nov 20, 2023

Re: [DISCUSS] KIP-1006: Remove SecurityManager Support

Hi Frédérik, Thanks for your response! This KIP is intended to be implemented immediately after voting, so it will appear in Kafka 3.10 or 4.0 at the earliest. I'm currently working on a PR and in my opinion there is very little risk of the change slipping from a release during the implementation

Re: [VOTE] KIP-1022 Formatting and Updating Features

Hi Jun, Colin, Thanks for your replies. If the FeatureCommand relies on version 0 too, my suggestion does not work. Omitting the features for old clients as suggested by Colin seems fine for me. In practice, administrators will usually use a version of FeatureCommand matching the cluster version

[jira] [Created] (KAFKA-17074) Remove ReplicaVerificationTool

Chia-Ping Tsai created KAFKA-17074: -- Summary: Remove ReplicaVerificationTool Key: KAFKA-17074 URL: https://issues.apache.org/jira/browse/KAFKA-17074 Project: Kafka Issue Type: Improvement

[jira] [Created] (KAFKA-17073) Deprecate ReplicaVerificationTool in 3.9

Chia-Ping Tsai created KAFKA-17073: -- Summary: Deprecate ReplicaVerificationTool in 3.9 Key: KAFKA-17073 URL: https://issues.apache.org/jira/browse/KAFKA-17073 Project: Kafka Issue Type: Impr

Re: [VOTE] KIP-752: Support --bootstrap-server in ReplicaVerificationTool

see https://issues.apache.org/jira/browse/KAFKA-17073 for deprecation. On 2024/07/03 14:57:51 Chia-Ping Tsai wrote: > Agree to Juma > > > Ismael Juma 於 2024年7月3日 晚上10:41 寫道： > > > > I think we should just do a KIP to remove it in 4.0 with deprecation in > > 3.9. > > > > Ismael > > > >> On

Re: [DISCUSS] KIP-1006: Remove SecurityManager Support

Hi all, When this KIP is intended to be implemented? As KIP-1013 is deprecating Java 11 in AK 3.7 and removes its support in AK 4.0, maybe the KIP needs an update. Regards, On Mon, Jul 1, 2024 at 10:39 PM Greg Harris wrote: > Hi Mickael, > > Thanks for the pointer to that JDK ticket, I did not

Re: [DISCUSS] KIP-1059: Enable the Producer flush() method to clear the latest send() error

Hi Justine, I agree that enumerating a list of errors that should be covered by the KIP is difficult; I was thinking it might be easier if we list the errors that should _not_ be covered by the KIP, and only if we can't define a reasonable heuristic that would cover them without having to explicit

Re: [DISCUSS] KIP-1059: Enable the Producer flush() method to clear the latest send() error

Hey Chris, I think what you say makes sense. I agree that defining the behavior based on code that can possibly change is not a good idea, and I was trying to get a clearer definition from the KIP's author :) I think it can always be hard to ensure that only specific errors are handled unless the

Re: [DISCUSS] KIP-1059: Enable the Producer flush() method to clear the latest send() error

Hi Alieh, I don't love defining the changes for this KIP in terms of a catch clause in the KafkaProducer class, for two reasons. First, the set of errors that are handled by that clause may shift over time as the code base is modified, and second, it would be fairly opaque to users who want to und

Re: [VOTE] KIP-752: Support --bootstrap-server in ReplicaVerificationTool

Agree to Juma > Ismael Juma 於 2024年7月3日 晚上10:41 寫道： > > I think we should just do a KIP to remove it in 4.0 with deprecation in 3.9. > > Ismael > >> On Wed, Jul 3, 2024 at 7:38 AM Chia-Ping Tsai wrote: >> >> hi Dongjin >> >> It will be removed in 4.0 if we are able to deprecate it in 3.9.

Re: [VOTE] KIP-752: Support --bootstrap-server in ReplicaVerificationTool

I think we should just do a KIP to remove it in 4.0 with deprecation in 3.9. Ismael On Wed, Jul 3, 2024 at 7:38 AM Chia-Ping Tsai wrote: > hi Dongjin > > It will be removed in 4.0 if we are able to deprecate it in 3.9. Hence, it > seems to me enhancing it is a bit weird since the feature is act

[jira] [Resolved] (KAFKA-16991) Flaky Test org.apache.kafka.streams.integration.PurgeRepartitionTopicIntegrationTest.shouldRestoreState

[ https://issues.apache.org/jira/browse/KAFKA-16991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck resolved KAFKA-16991. - Resolution: Fixed > Flaky Test > org.apache.kafka.streams.integration.PurgeRepartitionTopicInte

Re: [VOTE] KIP-752: Support --bootstrap-server in ReplicaVerificationTool

hi Dongjin It will be removed in 4.0 if we are able to deprecate it in 3.9. Hence, it seems to me enhancing it is a bit weird since the feature is active only for one release … > > Dongjin Lee 於 2024年7月3日 晚上10:04 寫道： > > Hi Tsai, > > Sorry for being late. How about this way? > > 1. Amend

[PR] test 2: trying again [kafka-merge-queue-sandbox]

mumrah opened a new pull request, #5: URL: https://github.com/apache/kafka-merge-queue-sandbox/pull/5 (no comment) -- 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 unsubs

Re: [PR] Adding test file [kafka-merge-queue-sandbox]

mumrah closed pull request #4: Adding test file URL: https://github.com/apache/kafka-merge-queue-sandbox/pull/4 -- 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,

Re: [VOTE] KIP-752: Support --bootstrap-server in ReplicaVerificationTool

Hi Tsai, Sorry for being late. How about this way? 1. Amend mention on the deprecation plan to the original KIP. 2. You cast +1 to this voting thread. 3. Add a new KIP to remove this tool with the 4.0 release. Since this KIP already has +2 bindings with PR, this way would be slightly more swift.

[PR] Adding test file [kafka-merge-queue-sandbox]

mumrah opened a new pull request, #4: URL: https://github.com/apache/kafka-merge-queue-sandbox/pull/4 (no comment) -- 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 unsubs

Re: [PR] Adding test file [kafka-merge-queue-sandbox]

mumrah closed pull request #3: Adding test file URL: https://github.com/apache/kafka-merge-queue-sandbox/pull/3 -- 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,

Re: [PR] Adding feature A [kafka-merge-queue-sandbox]

mumrah closed pull request #1: Adding feature A URL: https://github.com/apache/kafka-merge-queue-sandbox/pull/1 -- 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,

[PR] Adding test file [kafka-merge-queue-sandbox]

mumrah opened a new pull request, #3: URL: https://github.com/apache/kafka-merge-queue-sandbox/pull/3 (no comment) -- 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 unsubs

Re: [PR] Adding TEST file [kafka-merge-queue-sandbox]

mumrah closed pull request #2: Adding TEST file URL: https://github.com/apache/kafka-merge-queue-sandbox/pull/2 -- 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,

[PR] Adding TEST file [kafka-merge-queue-sandbox]

mumrah opened a new pull request, #2: URL: https://github.com/apache/kafka-merge-queue-sandbox/pull/2 (no comment) -- 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 unsubs

[jira] [Created] (KAFKA-17072) Document broker decommissioning process with KRaft

Mickael Maison created KAFKA-17072: -- Summary: Document broker decommissioning process with KRaft Key: KAFKA-17072 URL: https://issues.apache.org/jira/browse/KAFKA-17072 Project: Kafka Issue

Re: [VOTE] KIP-1042: Support for wildcard when creating new acls

I think that if we put in a trie based system we should be able to halve the normal searhc times and still be able to locate wild card matches very quickly. Users should be warned that "head wildcard" matches are slow and to use them sparingly. I am going to see if I can work out how to do wildca

Jenkins build is unstable: Kafka » Kafka Branch Builder » trunk #3071

See

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.8 #61

See

[jira] [Created] (KAFKA-17071) SharePartition - Add more unit tests

Abhinav Dixit created KAFKA-17071: - Summary: SharePartition - Add more unit tests Key: KAFKA-17071 URL: https://issues.apache.org/jira/browse/KAFKA-17071 Project: Kafka Issue Type: Sub-task

[jira] [Resolved] (KAFKA-17026) Implement updateCacheAndOffsets functionality on LSO movement

[ https://issues.apache.org/jira/browse/KAFKA-17026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinav Dixit resolved KAFKA-17026. --- Fix Version/s: 4.0.0 3.9.0 Resolution: Fixed > Implement updateCac

[jira] [Created] (KAFKA-17070) perf: consider to use ByteBufferOutputstream to append records

Luke Chen created KAFKA-17070: - Summary: perf: consider to use ByteBufferOutputstream to append records Key: KAFKA-17070 URL: https://issues.apache.org/jira/browse/KAFKA-17070 Project: Kafka Iss

[jira] [Created] (KAFKA-17069) Remote copy throttle metrics

Abhijeet Kumar created KAFKA-17069: -- Summary: Remote copy throttle metrics Key: KAFKA-17069 URL: https://issues.apache.org/jira/browse/KAFKA-17069 Project: Kafka Issue Type: Sub-task

[jira] [Resolved] (KAFKA-17047) Refactor Consumer group and shared classes with Share to modern package

[ https://issues.apache.org/jira/browse/KAFKA-17047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-17047. - Fix Version/s: 3.9.0 Resolution: Fixed > Refactor Consumer group and shared classes with

Re: [DISCUSS] KIP-1052: Enable warmup in producer performance test

Hi, On Tue, Jul 2, 2024 at 10:38 PM Welch, Matt wrote: > > Hi Federico, > > Thanks for your response. I have a few questions. > > > You mean, no existing public interfaces right? Anyway, this content should > > be in the "Compatibility, Deprecation, and Migration Plan" > section. > Just a quest