[beam-starter-typescript]: Missing place to create issue

Hi Beam community, I am David and new to the community. After tried to tweak some code from beam-starter-ts, I have found some issues and want to raise. But there is no way I can create an Github issue in the same project apache/beam-starter-typescript: Apache beam

Re: [Proposal] Kaskada DSL and FnHarness for Temporal Queries

Hey Daniel -- Great question! Kaskada was designed to be similar to SQL but with a few differences. The most significant is the assumption of both ordering and grouping. Kaskada uses this to automatically merge multiple input collections, and to allow data-dependent windows that identify a range

Re: [Proposal] Kaskada DSL and FnHarness for Temporal Queries

How does this mechanism differ from beam SQL which already offers windowing via SQL over PCollections? https://beam.apache.org/documentation/dsls/sql/extensions/windowing-and-triggering/ -Daniel On Mon, Jun 12, 2023 at 3:11 PM Ryan Michael wrote: > Hello, Beam (also)! > > Just introducing

Re: [Proposal] Kaskada DSL and FnHarness for Temporal Queries

Hello, Beam (also)! Just introducing myself - I'm Ryan and I've been working with Ben on the Kaskada project for the past few years. As Ben mentioned, I think there's a great opportunity to bring together some of the work we've done to make time-based computation easier to reason about with the

Re: Ensuring a task does not get executed concurrently

If you absolutely cannot tolerate concurrency an external locking mechanism is required. While a distributed system often waits for a work item to fail before trying it, this is not always the case (e.g. backup workers may be scheduled and whoever finishes first is determined to be the successful

[Proposal] Kaskada DSL and FnHarness for Temporal Queries

Hello Beam! Kaskada has created a query language for expressing temporal queries, making it easy to work with multiple streams and perform temporally correct joins. We’re looking at taking our native, columnar execution engine and making it available as a PTransform and FnHarness for use with

Re: Ensuring a task does not get executed concurrently

Hi Stephan, I am not sure if this is the best way to achieve this, but I've seen parallelism being limited by using state / KV and limiting the number of keys. In your case, you could have the same key for both non concurrency-safe operations and when using state, the Beam model will guarantee

Ensuring a task does not get executed concurrently

Can the Beam data model (specifically the Python SDK) support executing functions that are idempotent but not concurrency-safe? I am thinking of a task like setting up a database (or in my case, a Zarr store in Xarray-Beam ) where it is

Tour of Beam - an interactive Apache Beam learning guide

Hi Beam community! We invite you to try the Tour Of Beam [1] - an interactive Apache Beam learning guide. Please share your feedback [2] ! Key

Beam High Priority Issue Report (37)

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/27019 [Failing Test]: