beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kennknowles <>
Subject [GitHub] beam-site pull request #154: Clarify state further in capability matrix
Date Wed, 15 Feb 2017 03:28:46 GMT
GitHub user kennknowles opened a pull request:

    Clarify state further in capability matrix

    Some feedback after the blog post was that the term "Keyed State" in the capability matrix
is lacking a referent. Basically I got more queries like [this one](
but actually in response to a whole blog post describing it!
    I had thought this term came from Millwheel so there might be some use in tying the two
together. But it is actually [not in the paper](
I think it is used a bit in Flink. A more general terminology seems appropriate for the capability
matrix here.
    In this PR I have suggested a general terminology, but there may be better options.

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

    $ git pull state-capabilities

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 #154
commit 50b61f8132cdf847255746df8a480c3c0224ff8a
Author: Kenneth Knowles <>
Date:   2017-02-15T03:14:32Z

    Clarify state further in capability matrix


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 or file a JIRA ticket
with INFRA.

View raw message