[jira] [Updated] (KAFKA-16380) Rename the shallowOffsetOfMaxTimestamp in LogSegment

2024-03-19 Thread Johnny Hsu (Jira)


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

Johnny Hsu updated KAFKA-16380:
---
Description: 
When working on #KAFKA-16341, we found `shallowOffsetOfMaxTimestamp` also 
appears in LogSegment, which is a confusing name since it actually represent 
the record level offset, instead of a record batch level offset. 

Thus, this variable name should be renamed as well. 

More details can be found in 
[https://github.com/apache/kafka/pull/15476.|https://github.com/apache/kafka/pull/15476]

  was:
When working on #KAFKA-16341, we found `shallowOffsetOfMaxTimestamp` also 
appears in LogSegment, which is a confusing name since it actually represent 
the record level offset, instead of a record batch level offset. 

Thus, this variable name should be renamed as well. 

More details can be found in 


> Rename the shallowOffsetOfMaxTimestamp in LogSegment
> 
>
> Key: KAFKA-16380
> URL: https://issues.apache.org/jira/browse/KAFKA-16380
> Project: Kafka
>  Issue Type: Bug
>Reporter: Johnny Hsu
>Assignee: Johnny Hsu
>Priority: Minor
>
> When working on #KAFKA-16341, we found `shallowOffsetOfMaxTimestamp` also 
> appears in LogSegment, which is a confusing name since it actually represent 
> the record level offset, instead of a record batch level offset. 
> Thus, this variable name should be renamed as well. 
> More details can be found in 
> [https://github.com/apache/kafka/pull/15476.|https://github.com/apache/kafka/pull/15476]



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


[jira] [Updated] (KAFKA-16380) Rename the shallowOffsetOfMaxTimestamp in LogSegment

2024-03-19 Thread Johnny Hsu (Jira)


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

Johnny Hsu updated KAFKA-16380:
---
Description: 
When working on #KAFKA-16341, we found `shallowOffsetOfMaxTimestamp` also 
appears in LogSegment, which is a confusing name since it actually represent 
the record level offset, instead of a record batch level offset. 

Thus, this variable name should be renamed as well. 

More details can be found in 

  was:When working on #KAFKA-16341, we found 


> Rename the shallowOffsetOfMaxTimestamp in LogSegment
> 
>
> Key: KAFKA-16380
> URL: https://issues.apache.org/jira/browse/KAFKA-16380
> Project: Kafka
>  Issue Type: Bug
>Reporter: Johnny Hsu
>Assignee: Johnny Hsu
>Priority: Minor
>
> When working on #KAFKA-16341, we found `shallowOffsetOfMaxTimestamp` also 
> appears in LogSegment, which is a confusing name since it actually represent 
> the record level offset, instead of a record batch level offset. 
> Thus, this variable name should be renamed as well. 
> More details can be found in 



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


[jira] [Updated] (KAFKA-16380) Rename the shallowOffsetOfMaxTimestamp in LogSegment

2024-03-19 Thread Johnny Hsu (Jira)


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

Johnny Hsu updated KAFKA-16380:
---
Description: When working on #KAFKA-16341, we found 

> Rename the shallowOffsetOfMaxTimestamp in LogSegment
> 
>
> Key: KAFKA-16380
> URL: https://issues.apache.org/jira/browse/KAFKA-16380
> Project: Kafka
>  Issue Type: Bug
>Reporter: Johnny Hsu
>Assignee: Johnny Hsu
>Priority: Minor
>
> When working on #KAFKA-16341, we found 



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