[jira] [Commented] (KAFKA-4304) Extend Interactive Queries for return latest update timestamp per key

["Jeyhun Karimov (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KAFKA-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16027958#comment-16027958 ] 

Jeyhun Karimov commented on KAFKA-4304:
---------------------------------------

[~mjsax] I completely forgot this issue. Sorry for super late response. I misunderstood the issue (top-k staff). 
My question is, should we add a new public API to access tuple's update timestamp?If yes, I think this would be inefficient. 
Or (while querying with key) should we return the value  in a "package" containing its (key's) update timestamp? If yes, this would cause issues with backwards compatibility. 
Please correct me if I am wrong

> 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: newbie++
>
> 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)