[ https://issues.apache.org/jira/browse/KAFKA-16282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17820943#comment-17820943 ]
Luke Chen commented on KAFKA-16282: ----------------------------------- [~ahmedsobeh] , thanks for the drafted KIP. I think you can refer to [KIP-1005|https://cwiki.apache.org/confluence/display/KAFKA/KIP-1005%3A+Expose+EarliestLocalOffset+and+TieredOffset] for how to write a similar KIP. Other than that, you can directly start a discuss thread in dev mailing list as Justine suggested. > Allow to get last stable offset (LSO) in kafka-get-offsets.sh > ------------------------------------------------------------- > > Key: KAFKA-16282 > URL: https://issues.apache.org/jira/browse/KAFKA-16282 > Project: Kafka > Issue Type: Improvement > Reporter: Luke Chen > Assignee: Ahmed Sobeh > Priority: Major > Labels: need-kip, newbie, newbie++ > > Currently, when using `kafka-get-offsets.sh` to get the offset by time, we > have these choices: > {code:java} > --time <String: <timestamp> / timestamp of the offsets before > that. > -1 or latest / [Note: No offset is returned, if > the > -2 or earliest / timestamp greater than recently > -3 or max-timestamp / committed record timestamp is > -4 or earliest-local / given.] (default: latest) > -5 or latest-tiered > {code} > For the "latest" option, it'll always return the "high watermark" because we > always send with the default option: *IsolationLevel.READ_UNCOMMITTED*. It > would be good if the command can support to get the last stable offset (LSO) > for transaction support. That is, sending the option with > *IsolationLevel.READ_COMMITTED* -- This message was sent by Atlassian Jira (v8.20.10#820010)