flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From twalthr <...@git.apache.org>
Subject [GitHub] flink pull request #4441: [FLINK-7301] [docs] Rework state documentation
Date Mon, 31 Jul 2017 18:24:59 GMT
GitHub user twalthr opened a pull request:


    [FLINK-7301] [docs] Rework state documentation

    ## What is the purpose of the change
    *This PR restructures state related documentation pages. It introduces some state introduction
page and moves some files (from `setup/` to `ops/`) according to the new documentation structure.*
    ## Brief change log
    *Documentation changes only.*
    ## Verifying this change
    *Built with built script and links checked.*
    ## Does this pull request potentially affect one of the following parts:
      - Dependencies (does it add or upgrade a dependency): no
      - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: no
      - The serializers: no
      - The runtime per-record code paths (performance sensitive): no
      - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing,
Yarn/Mesos, ZooKeeper: no
    ## Documentation
      - Does this pull request introduce a new feature? no
      - If yes, how is the feature documented? not applicable

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

    $ git pull https://github.com/twalthr/flink FLINK-7301

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


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

    This closes #4441
commit b53e758216364903f211277052dbba4ae99da7d3
Author: twalthr <twalthr@apache.org>
Date:   2017-07-31T18:14:31Z

    [FLINK-7301] [docs] Rework state documentation


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.

View raw message