[
https://issues.apache.org/jira/browse/KAFKA-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16027964#comment-16027964
]
Jeyhun Karimov edited comment on KAFKA-4304 at 5/28/17 10:25 PM:
-----------------------------------------------------------------
>From the user perspective, one would query {{ReadOnlyKeyValueStore#get(key)}}
>to get the corresponding value and then she would query again for
>{{ReadOnlyKeyValueStore#getKeyWithTs}} to get key's timestamp. As a result we
>search twice. This is only for specific use-cases like this.
Maybe we can overload {{ReadOnlyKeyValueStore#get}} method to return
{{KeyWithTimestamp<K>}} and also add {{ReadOnlyKeyValueStore#get(key)}} for the
use-cases only requiring just key timestamp.
was (Author: jeyhunkarimov):
>From the user perspective, one would query {{ReadOnlyKeyValueStore#get(key)}}
>to get the corresponding value and then she would query again for
>{{ReadOnlyKeyValueStore#getKeyWithTs}} to get key's timestamp. As a result we
>search twice. This is only for specific use-cases like this.
Maybe we can overload {{ReadOnlyKeyValueStore#get}} method to return
{{KeyWithTimestamp<K>}}
> 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)
