You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Brian Hulette (Jira)" <ji...@apache.org> on 2021/01/12 16:18:00 UTC

[jira] [Updated] (BEAM-11614) sql_taxi examples fails on HEAD due to "transform unexpectedly with no env id"

     [ https://issues.apache.org/jira/browse/BEAM-11614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Hulette updated BEAM-11614:
---------------------------------
    Status: Open  (was: Triage Needed)

> sql_taxi examples fails on HEAD due to "transform unexpectedly with no env id"
> ------------------------------------------------------------------------------
>
>                 Key: BEAM-11614
>                 URL: https://issues.apache.org/jira/browse/BEAM-11614
>             Project: Beam
>          Issue Type: Bug
>          Components: cross-language
>            Reporter: Chamikara Madhusanka Jayalath
>            Assignee: Brian Hulette
>            Priority: P1
>
> For example, [https://pantheon.corp.google.com/dataflow/jobs/us-central1/2021-01-11_21_50_55-8290792779966349848?project=google.com:clouddfe]
>  
> transform unexpectedly with no env id: external_1SqlTransform(beam:external:java:sql:v1)/BeamAggregationRel_34/Group.CombineFieldsByFields/ToKvs/toRow: spec \{ } inputs \{ key: "org.apache.beam.sdk.values.PCollection.<init>:402#3d93cb799b3970be" value: "external_1SqlTransform(beam:external:java:sql:v1)/BeamCalcRel_33/ParDo(Calc)/ParMultiDo(Calc).output" } outputs \{ key: "org.apache.beam.sdk.values.PCollection.<init>:402#3d93cb799b3970be" value: "external_1SqlTransform(beam:external:java:sql:v1)/BeamCalcRel_33/ParDo(Calc)/ParMultiDo(Calc).output" } unique_name: "SqlTransform(beam:external:java:sql:v1)/BeamAggregationRel_34/Group.CombineFieldsByFields/ToKvs/toRow"
>  
> Seems like somehow Sql expansion produces a sub-transform that does not have environment ID set.
> This passes for Beam 2.27.0 so should be due to a recent change.
>  
> Brian, are you aware of any recent change that could have resulted in this breakage ?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)