[
https://issues.apache.org/jira/browse/FLINK-10117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16595795#comment-16595795
]
Eron Wright commented on FLINK-10117:
--------------------------------------
Note that the SSL feature for Queryable State (FLINK-5029) will treat the
existing endpoints as 'internal' communication, which means that the client
must possess the internal cluster keypair. That's an obvious usability issue
that might best be addressed by this enhancement (FLINK-10117).
> REST API for Queryable State
> ----------------------------
>
> Key: FLINK-10117
> URL: https://issues.apache.org/jira/browse/FLINK-10117
> Project: Flink
> Issue Type: Improvement
> Components: Queryable State, REST
> Affects Versions: 1.6.0
> Reporter: Elias Levy
> Priority: Major
>
> At the moment, queryable state requires a JVM based client that can make use
> of the Java queryable state client API in flink-queryable-state-client
> artifact. In addition, the client requires a state descriptor matching the
> queried state, which tightly couples the Flink job and query state clients.
> I propose that queryable state become accessible via a REST API. FLINK-7040
> mentions this possibility, but does not specify work towards that goal.
> I suggest that to enable queryable state over REST, users define JSON
> serializers via the state descriptors.
> This would allow queryable state clients to be developed in any language, not
> require them to use a Flink client library, and permit them to be loosely
> coupled with the job, as they could generically parse the returned JSON.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
