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/01/12 03:50:05 UTC
[jira] [Updated] (BEAM-2975) Results of ReadableState.read() should be snapshots of the underlying state
[ https://issues.apache.org/jira/browse/BEAM-2975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kenneth Knowles updated BEAM-2975:
----------------------------------
This Jira ticket has a pull request attached to it, but is still open. Did the pull request resolve the issue? If so, could you please mark it resolved? This will help the project have a clear view of its open issues.
> Results of ReadableState.read() should be snapshots of the underlying state
> ---------------------------------------------------------------------------
>
> Key: BEAM-2975
> URL: https://issues.apache.org/jira/browse/BEAM-2975
> Project: Beam
> Issue Type: Bug
> Components: sdk-java-core
> Reporter: Daniel Mills
> Priority: P3
> Labels: Clarified
>
> Future modification of state should not be reflected in previous calls to read(). For example:
> @StateId("tag") BagState<Integer> state;
> Iterable<Integer> ints = state.read();
> state.add(17);
> // ints should still be empty here.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)