During the design of the Beam Python State API, we noticed some transactionality inconsistencies in the existing Beam Java State API (these are the unresolved bugs BEAM-2980 <https://issues.apache.org/jira/browse/BEAM-2980> and BEAM-2975 <https://issues.apache.org/jira/browse/BEAM-2975>). We are therefore having a discussion about this API which can have implications for its future development in all Beam languages: https://docs.google.com/document/d/1GadEkAmtbJQjmqiqfSzGw3b66TKerm8tyn6TK4blAys/edit#heading=h.ofyl9jspiz3b
If you have an opinion on the possible design approaches, it would be very helpful to bring up in the doc or on this thread. Thanks! Best, Charles
