link JobManager, two TaskManagers, and a
Beam JobServer running locally. I can execute the pipeline that's written
in Go and see the job submitted on Flink's UI, however, it quickly fails
because there are no workers to execute the Go transforms.
Thanks,
Sherif Tolba
ly replace the current Go Direct runner.
>
> See
> https://github.com/apache/beam/tree/master/sdks/go/pkg/beam/runners/prism
> for current usage instructions and restrictions.
>
> It's currently suitable for smoke testing small pipelines, but the goal is
> to have a por
xternal
> --environment_config= --endpoint= service>
>
> This `workerService` would then use whatever it likes to get containers
> onto VMs when requested by the Job service/flink.
>
> I'd be entirely delighted for such a thing to be contributed, and help
> review it. @los
can be hashed out appropriately during code review,
> once it's working for your usecase.
>
> On 2023/03/24 20:05:06 Sherif Tolba wrote:
> > Hi Robert,
> >
> > Thank you for your insightful response. The setup you described makes
> sense
> > to me and I'd
der into the "cmd"
> directory, since it would be most useful as a stand alone command for
> someone to run. That can be hashed out appropriately during code review,
> once it's working for your usecase.
>
> On 2023/03/24 20:05:06 Sherif Tolba wrote:
> > Hi Rob
I realized that my last comment doesn't make sense because, as you pointed
out earlier, LOOPBACK loops back to the submitting job process to execute
the job.
On Mon, Mar 27, 2023 at 9:34 AM Sherif Tolba
wrote:
> Oh, I might have missed the point about how the Flink portable runner
>
