For Go we *will* (and do) need to cross compile and in many cases do so
automatically, for Amd64 instances, but don't currently support Arm64
workers.
We will likely need to support platform specific containers for all the
languages, or include boot loaders for all platforms and select which one
w
Thanks for pointing this out Robert, I had somehow in my mind that it
was not official until 1.18 but I forgot to double check, for info I
was able to build the Go SDK container without any trouble so I assume
most of the things are 'ready'.
It would be great to take a look at fixing the hardcoded
Go supports ARM64 on Darwin since 1.16, which is the minimum version of Go
we currently support.
See https://go.dev/blog/ports
There are definitely some hardcoded paths we'd need to adjust to build boot
containers though.
Go 1.18 improves things, and since it has the initial run of Go Generics,
Just for your information: Thanks to that change - i will soon be adding
ARM support for Apache Airflow - including building and publishing the
images and running our tests (using self-hosted runners).
As soon as I get it I will be able to share the code/experiences with you.
J
On Tue, Feb 8, 202
For awareness with the just released Beam 2.36.0 Beam works out of the
box to develop on a Mac M1.
I tried Java and Python pipelines with success running locally on both
Flink/Spark runner.
I found one issue using zstd and created [1] that was merged today,
with this the sdks:core tests and Spark
Comment from the side - If you use Docker - experience from Airflow -
until we will get ARM images, docker experience is next to unusable
(docker filesystem slowness + emulation).
J.
On Wed, Jan 12, 2022 at 6:21 PM Daniel Collins wrote:
>
> I regularly develop on a non-m1 mac using intellij, whi
Does anyone do Beam development on an M1 Mac? Any tips to getting things up and
running?
Alternatively, does anyone have a good "workstation in the cloud" setup?
Thanks
Matt
