You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2022/06/03 16:15:00 UTC

[jira] [Commented] (BEAM-652) StateNamespaces.window() potentially unstable / stable encodings for windows

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

Kenneth Knowles commented on BEAM-652:
--------------------------------------

This issue has been migrated to https://github.com/apache/beam/issues/18059

> StateNamespaces.window() potentially unstable / stable encodings for windows
> ----------------------------------------------------------------------------
>
>                 Key: BEAM-652
>                 URL: https://issues.apache.org/jira/browse/BEAM-652
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-java-core
>            Reporter: Kenneth Knowles
>            Priority: P3
>              Labels: Clarified
>
> WindowNamespace#stringKey includes a base64 encoding of the window as encoded by the windowCoder. This makes the key unpredictable if we support features such as reloading a pipeline with a new SDK or bugfixed pipeline. The encoding should be stable and documented.
> And even if the SDK's window types are stable and documented, users can define their own windows with coders and these may be less stable / requiring bugfixes. This ticket is to track the issue and any new ideas.
> [1] https://github.com/apache/incubator-beam/blob/master/sdks/java/core/src/main/java/org/apache/beam/sdk/util/state/StateNamespaces.java#L113



--
This message was sent by Atlassian Jira
(v8.20.7#820007)