[
https://issues.apache.org/jira/browse/KAFKA-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16027963#comment-16027963
]
Matthias J. Sax commented on KAFKA-4304:
----------------------------------------
Not sure how to implement it... :) Why do you think a new API would be
inefficient? We could add a new method {{ReadOnlyKeyValueStore#getKeyWithTs}}
and return a {{KeyWithTimestamp<K>}} object with method {{K key()}}, {{long
timestamp()}}.
This would still be an public API change and would require a KIP.
> Extend Interactive Queries for return latest update timestamp per key
> ---------------------------------------------------------------------
>
> Key: KAFKA-4304
> URL: https://issues.apache.org/jira/browse/KAFKA-4304
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: Matthias J. Sax
> Priority: Minor
> Labels: needs-kip
>
> Currently, when querying state store, it is not clear when the key was
> updated last. The ides of this JIRA is to make the latest update timestamp
> for each key-value-pair of the state store accessible.
> For example, this might be useful to
> * check if a value was update but did not changed (just compare the update
> TS)
> * if you want to consider only recently updated keys
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
