[
https://issues.apache.org/jira/browse/FLINK-5510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15848778#comment-15848778
]
Dawid Wysakowicz commented on FLINK-5510:
-----------------------------------------
Just had a look into the code and been wondering how much of the futures do we
want to replace. Just the return values in {{QueryableStateClient}} or every
usage in QueryableStateClient/KvStateLookupService? If the former there is
{{Future#recoverWith}} alternative missing in {{FlinkFuture}}.
> Replace Scala Future with FlinkFuture in QueryableStateClient
> -------------------------------------------------------------
>
> Key: FLINK-5510
> URL: https://issues.apache.org/jira/browse/FLINK-5510
> Project: Flink
> Issue Type: Improvement
> Components: Queryable State
> Reporter: Ufuk Celebi
> Assignee: Dawid Wysakowicz
> Priority: Minor
>
> The entry point for queryable state users is the {{QueryableStateClient}}
> which returns query results via Scala Futures. Since merging the initial
> version of QueryableState we have introduced the FlinkFuture wrapper type in
> order to not expose our Scala dependency via the API.
> Since APIs tend to stick around longer than expected, it might be worthwhile
> to port the exposed QueryableStateClient interface to use the FlinkFuture.
> Early users can still get the Scala Future via FlinkFuture#getScalaFuture().
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
