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

ASF GitHub Bot commented on FLINK-7822:
---------------------------------------

GitHub user kl0u opened a pull request:

    https://github.com/apache/flink/pull/4966

    [FLINK-7822][FLINK-7823] Adds documentation and fixes configuration of QS.

    ## What is the purpose of the change
    
    *This PR adds documentation for the new queryable state.
    
    R @aljoscha 

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/kl0u/flink qs-doc

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/4966.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #4966
    
----
commit 91c7082158e534ffc30894e9f23e6ea6c94fab07
Author: kkloudas <kklou...@gmail.com>
Date:   2017-11-06T11:43:18Z

    [FLINK-7823][QS] Update Queryable State configuration parameters.

commit 2a076d6119eb01a4b4bc48925a37dde1b439dd54
Author: kkloudas <kklou...@gmail.com>
Date:   2017-11-06T16:21:45Z

    [FLINK-7822][QS][doc] Update Queryable State docs.

----


> Add documentation for the new queryable state client.
> -----------------------------------------------------
>
>                 Key: FLINK-7822
>                 URL: https://issues.apache.org/jira/browse/FLINK-7822
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Documentation, Queryable State
>    Affects Versions: 1.4.0
>            Reporter: Kostas Kloudas
>            Assignee: Kostas Kloudas
>            Priority: Blocker
>             Fix For: 1.4.0
>
>
> This has to include:
> 1) how to enable queryable state (jars)...
> 2) configuration parameters
> 3) new APIs
> 4) Guarantees/Semantics/Limitations (e.g. memory backend)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to