kennknowles commented on issue #26465: URL: https://github.com/apache/beam/issues/26465#issuecomment-1775164837
Just skimming this last comment, it sounds like this is related to the impetus to https://s.apache.org/beam-triggered-side-inputs Right now we have a combination of 1. "definition is whatever happens when you run it" situation with side inputs, always precarious 2. side inputs pretty much unaware of triggers (as most of the model is) so they don't intelligently respect panes (they see two firings are just two separate elements rather than a revision to the element) 3. no clear way to really manage deltas versus full replacement values on triggering; presumably side inputs would do this intelligently transparently I am totally happy with a `View.latest()`. In my doc I propose that as the semantics for `View.asSingleton` :-) If you can implement it without runner changes, or have the bandwidth to make the necessary runner changes, I would just replace `View.asSingleton` with that. Otherwise, having it as a stopgap until `View.asSingleton` can be adjusted is great. https://s.apache.org/beam-side-inputs-1-pager -- 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]
