We discovered a regression on CombineFn.from_callable() started in 2.26.0.
Even though it's not a regression in 2.27.0, I strongly prefer we fix it in
2.27.0 as it leads to buggy behavior, so I vote -1.
The fix to release branch is in flight:
https://github.com/apache/beam/pull/13613.
On Wed, D
-1 (non-binding)
Good news: I validated a dataframe pipeline on Dataflow which looked good
(with expected performance improvements!)
Bad news: I also tried to run the sql_taxi example pipeline (streaming SQL
in python) on Dataflow and ran into PubSub IO related issues. The example
fails in the same
Thanks for the answer Robert. Producing a combiner with two lists as
outputs was one idea I was considering too but I was afraid of
OutOfMemory issues. I had not thought much about the consequences on
combining state, thanks for pointing that. For the particular sampling
use case it might be not an
HI all
i was wondering how is it possible to force Beam to run 4 separate
processes for this pipeline
Currently i have this setup
with beam.Pipeline(options=pipeline_options) as p:
source = (p | 'Startup' >> beam.Create([1,2,3,4])
)
lines = run_my_pipeline(source)
Now, a
+1 (non-binding) Validated wordcount with Python source + Flink and Spark
job server jars. Also checked that the ...:sql:udf jar was added and
includes our cherry-picks. Thanks Pablo :)
On Wed, Dec 23, 2020 at 12:02 PM Ahmet Altay wrote:
> +1 (binding).
>
> I validated python quickstarts. Thank
+1 (binding).
I validated python quickstarts. Thank you Pablo.
On Tue, Dec 22, 2020 at 10:04 PM Jean-Baptiste Onofre
wrote:
> +1 (binding)
>
> Regards
> JB
>
> Le 23 déc. 2020 à 06:46, Pablo Estrada a écrit :
>
> Hi everyone,
> Please review and vote on the release candidate #1 for the version
