lukecwik commented on issue #24801: URL: https://github.com/apache/beam/issues/24801#issuecomment-1371196171
> This is a good catch. It is actually a bit of a poor design. It would be preferable for an empty valuestate to throw no such element if it hasn't been written yet, since now we have the state "unwritten" and the state "written explicitly to null" that cannot be distinguished. Being able to differentiate between these two is important sometimes but I feel as though it is uncommon and users can always use bagstate to differentiate between unset and null value. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
