[
https://issues.apache.org/jira/browse/BEAM-750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15583376#comment-15583376
]
Kenneth Knowles commented on BEAM-750:
--------------------------------------
To be quite explicit - state kinds do not exist in the Beam model. Today all
state tags are "system" tags - meaning that they are used in triggers and
{{ReduceFnRunner}}. The concept of a state kind was to be sure that these are
distinct from the state that the user uses. But there is, in fact, no
model-level requirement that they exist in the same data store at all. So state
kind is actually a runner-specific technique to ensure distinctness.
> Remove StateTag
> ---------------
>
> Key: BEAM-750
> URL: https://issues.apache.org/jira/browse/BEAM-750
> Project: Beam
> Issue Type: Improvement
> Reporter: Eugene Kirpichov
> Assignee: Kenneth Knowles
>
> https://github.com/apache/incubator-beam/pull/1044 made StateTag in some
> cases ignore the state kind (user/system). This is currently harmless,
> because there is no user-facing API for defining state anyway, so conflicts
> between user/system state can't happen.
> [~kenn] says this should be solved by removing StateTag entirely (along with
> state kinds).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
