beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ben Sidhom (JIRA)" <>
Subject [jira] [Commented] (BEAM-3587) User reports TextIO failure in FlinkRunner on master
Date Fri, 02 Feb 2018 18:59:00 GMT


Ben Sidhom commented on BEAM-3587:

As Ken mentioned, this is strange since we have ValidatesRunner tests that should in theory
trigger this. Can we get a minimal example pipeline that hits this issue?

> User reports TextIO failure in FlinkRunner on master
> ----------------------------------------------------
>                 Key: BEAM-3587
>                 URL:
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-flink
>            Reporter: Kenneth Knowles
>            Assignee: Ben Sidhom
>            Priority: Blocker
>             Fix For: 2.3.0
> Reported here: []
> "I'm trying to run a pipeline containing just a step on a Flink cluster,
using the latest Beam git revision (ff37337). The job fails to start with the Exception:
>   {{java.lang.UnsupportedOperationException: The transform  is currently not supported.}}
> It does work with Beam 2.2.0 though. All code, logs, and reproduction steps  []"
> My initial thoughts: I have a guess that this has to do with switching to running from
a portable pipeline representation, and it looks like there's a non-composite transform with
an empty URN and it threw a bad error message. We can try to root cause but may also mitigate
short-term by removing the round-trip through pipeline proto for now.
> What is curious is that the ValidatesRunner and WordCountIT are working - they only run
on a local Flink, yet this seems to be a translation issue that would occur for local or distributed
> We need to certainly run this repro on the RC if we don't totally get to the bottom of
it quickly.

This message was sent by Atlassian JIRA

View raw message