DoFn Serialization Semantics

Hey all, I'm a bit confused with the semantics around DoFn serialization. I have a model defined like this: ``` type SinkCustomAttributes map[string]string type SinkScan struct { DestinationURLQueryParams SinkCustomAttributes `beam:"destination_url_query_params" db:"destination_url_query_param

Re: Beam YAML Side Inputs?

We do not have a plan to support this yet. We are trying to package all these into some higher level APIs. For example, YAML does not surface Reshuffle but Create ( https://beam.apache.org/releases/yamldoc/current/#create) has the boolean option to add this after Create. On Thu, May 1, 2025 at 3:5

Beam YAML Side Inputs?

Are side inputs supported with Beam YAML? Is there a plan to support them if not or will they never be supported? Best, Joey -- Joey Tran | Staff Developer | AutoDesigner TL *he/him* [image: Schrödinger, Inc.]

Re: Bizzarre behavour in Apache Beam pipeline after adding a RunInference pipeline / ignoe

Apologies, operator error :( On Thu, May 1, 2025 at 4:33 PM Sofia’s World wrote: > HI all > was wondering if someone can advise here as i am puzzled on what is > happening (and perhaps it's my poor understanding of beam) > > Here's my usecase - very simplified -: > > I have 3 collections whic

Bizzarre behavour in Apache Beam pipeline after adding a RunInference pipeline

HI all was wondering if someone can advise here as i am puzzled on what is happening (and perhaps it's my poor understanding of beam) Here's my usecase - very simplified -: I have 3 collections which i want to use to populate an email combined = ({'collection1': keyed_etoro, 'collection2': ke