Kafka jenkins is unable to run and view old builds.

[Luke Chen]

Hi all,

Currently, the Kafka jenkins is unable to run and view old builds.
I've filed INFRA-25824 
to infra team.

Thanks.
Luke

[jira] [Resolved] (KAFKA-16804) Replace gradle archivesBaseName with archivesName

[Greg Harris (Jira)]

 [ 
https://issues.apache.org/jira/browse/KAFKA-16804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Greg Harris resolved KAFKA-16804.
-
Fix Version/s: 3.8.0
   Resolution: Fixed

> Replace gradle archivesBaseName with archivesName
> -
>
> Key: KAFKA-16804
> URL: https://issues.apache.org/jira/browse/KAFKA-16804
> Project: Kafka
>  Issue Type: Sub-task
>Reporter: Greg Harris
>Assignee: TengYao Chi
>Priority: Major
>  Labels: newbie
> Fix For: 3.8.0
>
>
> The BasePluginExtension.archivesBaseName property has been deprecated.    
> This is scheduled to be removed in Gradle 9.0.    
> Please use the archivesName property instead.    
> [Documentation|https://docs.gradle.org/8.7/dsl/org.gradle.api.plugins.BasePluginExtension.html#org.gradle.api.plugins.BasePluginExtension:archivesName]
> 1 usage    
> Script:build.gradle
>  
> The org.gradle.api.plugins.BasePluginConvention type has been deprecated.    
> This is scheduled to be removed in Gradle 9.0.    
> [Documentation|https://docs.gradle.org/8.7/userguide/upgrading_version_8.html#base_convention_deprecation]
> 1 usage    
> Script:build.gradle



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (KAFKA-16843) Remove preAppendErrors from createPutCacheCallback

[Chia-Ping Tsai (Jira)]

Chia-Ping Tsai created KAFKA-16843:
--

 Summary: Remove preAppendErrors from createPutCacheCallback
 Key: KAFKA-16843
 URL: https://issues.apache.org/jira/browse/KAFKA-16843
 Project: Kafka
  Issue Type: Improvement
Reporter: Chia-Ping Tsai
Assignee: Chia-Ping Tsai


origin discussion: 
[https://github.com/apache/kafka/pull/16072#pullrequestreview-2077368462]

The method `createPutCacheCallback` has a input argument `preAppendErrors` [0]. 
It is used to keep the "error" happens before appending. However, the 
pre-append error is handled before by calling `responseCallback` [1]. Hence, we 
can remove `preAppendErrors`.
 
[0] 
https://github.com/apache/kafka/blob/trunk/core/src/main/scala/kafka/coordinator/group/GroupMetadataManager.scala#L387
[1] 
https://github.com/apache/kafka/blob/4f55786a8a86fe228a0b10a2f28529f5128e5d6f/core/src/main/scala/kafka/coordinator/group/GroupCoordinator.scala#L927C15-L927C84



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [VOTE] KIP 1047 - Introduce new org.apache.kafka.tools.api.Decoder to replace kafka.serializer.Decoder

[Frank Yang]

Hi everyone,

Thanks for participating in the discussion and voting! KIP-1047 has been
accepted with the following +1 votes:

- Chia-Ping Tsai (binding)
- Josep Prat (binding)
- Mickael Maison (binding)
- Luke Chen (binding)
- Andrew Schofield (non-binding)
- Kuan Po Tseng (non-binding)
- 吳岱儒 (non-binding)

The target release for this KIP is 3.8.0

Thanks and regards,
PoAn

> On May 24, 2024, at 5:30 PM, Luke Chen  wrote:
> 
> +1 (binding)
> Thanks Frank!
> 
> Luke
> 
> On Fri, May 24, 2024 at 5:21 PM Josep Prat 
> wrote:
> 
>> Hi Frank,
>> 
>> thanks for the KIP.
>> +1 (binding)
>> 
>> Best,
>> 
>> On Fri, May 24, 2024 at 11:11 AM Kuan Po Tseng 
>> wrote:
>> 
>>> +1 (non-binding)
>>> 
>>> On 2024/05/23 16:26:42 Frank Yang wrote:
 Hi all,
 
 I would like to start a vote on KIP-1047: Introduce new
 org.apache.kafka.tools.api.Decoder to replace kafka.serializer.Decoder.
 
 KIP:
>>> 
>> https://cwiki.apache.org/confluence/display/KAFKA/KIP-1047+Introduce+new+org.apache.kafka.tools.api.Decoder+to+replace+kafka.serializer.Decoder
 
 Discussion thread:
>>> https://lists.apache.org/thread/n3k6vb4vddl1s5nopcyglnddtvzp4j63
 
 Thanks and regards,
 PoAn
>>> 
>> 
>> 
>> --
>> [image: Aiven] 
>> 
>> *Josep Prat*
>> Open Source Engineering Director, *Aiven*
>> josep.p...@aiven.io   |   +491715557497
>> aiven.io    |   >> 
>>     <
>> https://twitter.com/aiven_io>
>> *Aiven Deutschland GmbH*
>> Alexanderufer 3-7, 10117 Berlin
>> Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
>> Amtsgericht Charlottenburg, HRB 209739 B
>> 

[QUESTION] Move log start offset back in time for data recovery

[bo gao]

Hi,

I have one question for tier storage, have a 3.6 cluster with some log
segments exists in the remote store with metadata, but kafka's earliest
offset is more recent, is there a way to move start log offset back in
time? I wonder if we can still serve that data to consumer. If yes, would
appreciate a few tips regarding how to do so and pointer to internal
script/tooling.

thanks!