Re: tox issues in dev container

2024-04-10 Thread Austin Bennett
based on 'devcontainer', I assume running in/via: https://containers.dev/ ? On Fri, Apr 5, 2024 at 3:46 PM XQ Hu via dev wrote: > always pin the versions as well. > > On Fri, Apr 5, 2024 at 5:24 PM Valentyn Tymofieiev via dev < > dev@beam.apache.org> wrote: > >> Could you please provide more in

Re: PCollection#applyWindowingStrategyInternal

2024-04-10 Thread Reuven Lax via dev
Are you familiar with the "sink triggers" proposal? Essentially while windowing is usually a property of the data, and therefore flows downwards through the graph, triggering is usually a property of output (i.e. sink) latency - how much are you willing to wait to see data, and what semantics do y

Beam High Priority Issue Report (62)

2024-04-10 Thread beamactions
This is your daily summary of Beam's current high priority issues that may need attention. See https://beam.apache.org/contribute/issue-priorities for the meaning and expectations around issue priorities. Unassigned P1 Issues: https://github.com/apache/beam/issues/30904 The PostCommit XVR

Re: PCollection#applyWindowingStrategyInternal

2024-04-10 Thread Jan Lukavský
On 4/9/24 18:33, Kenneth Knowles wrote: At a top level `setWindowingStrategyInternal` exists to set up the metadata without actually assigning windows. If we were more clever we might have found a way for it to not be public... it is something that can easily lead to an invalid pipeline. Yes,