[jira] [Updated] (KAFKA-16282) Allow to get last stable offset (LSO) in kafka-get-offsets.sh
[ https://issues.apache.org/jira/browse/KAFKA-16282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Chen updated KAFKA-16282: -- Description: Currently, when using `kafka-get-offsets.sh` to get the offset by time, we have these choices: {code:java} --time / 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* was: Currently, when using `kafka-get-offsets.sh` to get the offset by time, we have these choices: {code:java} --time / 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 choice, 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* > 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 / 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)
[jira] [Updated] (KAFKA-16282) Allow to get last stable offset (LSO) in kafka-get-offsets.sh
[ https://issues.apache.org/jira/browse/KAFKA-16282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Chen updated KAFKA-16282: -- Description: Currently, when using `kafka-get-offsets.sh` to get the offset by time, we have these choices: {code:java} --time / 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 choice, 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* was: Currently, when using `kafka-get-offsets.sh` to get the offset by time, we have these choices: {code:java} --time / 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 choice, 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. > 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 >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 / 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 choice, 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)
[jira] [Updated] (KAFKA-16282) Allow to get last stable offset (LSO) in kafka-get-offsets.sh
[ https://issues.apache.org/jira/browse/KAFKA-16282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Chen updated KAFKA-16282: -- Labels: need-kip newbie newbie++ (was: ) > 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 >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 / 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 choice, 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. -- This message was sent by Atlassian Jira (v8.20.10#820010)