[
https://issues.apache.org/jira/browse/KAFKA-15546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17773425#comment-17773425
]
Justine Olshan commented on KAFKA-15546:
----------------------------------------
Hey Giovanni. The API does not currently support sending two timestamps, so
this change would require a KIP to update the API. I don't think we store a txn
commit time in the metadata either. I can look into whether the last updated
time maps to this, but if it does not, I'm not sure if it makes sense to add
another field in the state for that.
See current API:
https://github.com/apache/kafka/blob/trunk/clients/src/main/resources/common/message/DescribeTransactionsResponse.json
> Transactions tool duration field confusing for completed transactions
> ---------------------------------------------------------------------
>
> Key: KAFKA-15546
> URL: https://issues.apache.org/jira/browse/KAFKA-15546
> Project: Kafka
> Issue Type: Task
> Reporter: Justine Olshan
> Assignee: Justine Olshan
> Priority: Major
>
> When using the transactions tool to describe transactions, if the transaction
> is completed, its duration will still increase based on when it started. This
> value is not correct. Instead, we can leave the duration field blank (since
> we don't have the data for the completed transaction in the describe
> response).
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)