Re: [DISCUSS] Processing time timers in "batch" (faster-than-wall-time [re]processing)

On 2/27/24 19:49, Robert Bradshaw via dev wrote: On Tue, Feb 27, 2024 at 10:39 AM Jan Lukavský wrote: On 2/27/24 19:22, Robert Bradshaw via dev wrote: On Mon, Feb 26, 2024 at 11:45 AM Kenneth Knowles wrote: Pulling out focus points: On Fri, Feb 23, 2024 at 7:21 PM Robert Bradshaw via dev

Beam High Priority Issue Report (38)

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 P0 Issues: https://github.com/apache/beam/issues/30377 [Failing Test]: 404

[GSOC] Build out Beam Use Cases

Hello! My name is Nivaldo, and I'd like to express my interest in joining this year's GSOC to add real world use cases for Beam's MLTransform/Enrichment transforms . ***About me*** I am a Senior Data Engineer from Brazil, with 6-7 YOE in helping com

Re: [GSOC] Build out Beam Use Cases

Hey Nivaldo, thanks for reaching out and for your interest in contributing to Beam in this way! I'll do my best to answer your questions below: > 1. Would I actually be eligible to apply to GSOC for this project, or do I not count as an open source beginner anymore in this case? The total number o

Re: [DISCUSS] Processing time timers in "batch" (faster-than-wall-time [re]processing)

Sounds like a different variation is either new timer types with those distinctions in mind, or additional configuration for ProcessingTime timers (defaulting to current behavior) to sort out those cases. Could potentially be extended to EventTime timers too for explicitly handling looping timer