[ https://issues.apache.org/jira/browse/KAFKA-15107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17749589#comment-17749589 ]
Luke Chen commented on KAFKA-15107: ----------------------------------- Set as blocker for 3.6.0 since this KIP assumes it'll be released as tiered storage feature in 3.6.0 > Additional custom metadata for remote log segment > ------------------------------------------------- > > Key: KAFKA-15107 > URL: https://issues.apache.org/jira/browse/KAFKA-15107 > Project: Kafka > Issue Type: Improvement > Components: core > Reporter: Ivan Yurchenko > Assignee: Ivan Yurchenko > Priority: Blocker > Labels: tiered-storage > Fix For: 3.6.0 > > > Based on the [KIP-917: Additional custom metadata for remote log > segment|https://cwiki.apache.org/confluence/display/KAFKA/KIP-917%3A+Additional+custom+metadata+for+remote+log+segment], > the following needs to be implemented: > # {{{}RemoteLogSegmentMetadata{}}}{{{}.CustomMetadata{}}}. > # {{RemoteStorageManager.copyLogSegmentData}} needs to be updated to the new > return type (+ javadoc). > # {{RemoteLogSegmentMetadata.customMetadata}} and > {{RemoteLogSegmentMetadata.createWithCustomMetadata}} methods. Same in > {{{}RemoteLogSegmentMetadataSnapshot{}}}. > # {{RemoteLogSegmentMetadataRecord}} and > {{RemoteLogSegmentMetadataSnapshotRecord}} definitions need to be updated. > # Custom metadata should be persisted by {{RemoteLogManager}} if provided. > # The new config {{remote.log.metadata.custom.metadata.max.size}} needs to > be introduced. > # The custom metadata size limit must be applied according to the KIP. -- This message was sent by Atlassian Jira (v8.20.10#820010)