[
https://issues.apache.org/jira/browse/BEAM-8111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16927941#comment-16927941
]
Brian Hulette commented on BEAM-8111:
-------------------------------------
I think this Jira can still be considered resolved without #9454. The only
reason it's tied to this ticket is because I added that test specifically to
avoid a failure like this one in the future.
Ideally we would continue to run this test on Dataflow, because a failure there
would be a blocker. Is it possible to just skip it on the runners where it's
failing instead of removing entirely?
FYI, [~reuvenlax] and I suspect the failures on other runners may be caused by
BEAM-8146. I think that issue is fine to punt until after 2.16 is cut.
> SchemaCoder broken on DataflowRunner
> ------------------------------------
>
> Key: BEAM-8111
> URL: https://issues.apache.org/jira/browse/BEAM-8111
> Project: Beam
> Issue Type: Bug
> Components: runner-dataflow, sdk-java-core
> Affects Versions: 2.15.0
> Reporter: Brian Hulette
> Assignee: Brian Hulette
> Priority: Blocker
> Fix For: 2.16.0
>
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> https://github.com/apache/beam/commit/e65c176a9f34e45d408281e1101a2ae54cef0f6c
> broke SchemaCoder on Dataflow. When translating a schema that uses logical
> types from a cloud object dataflow encounters a runtime error.
> This means any pipelines that use SqlTransform or schema transforms will fail
> on Dataflow in 2.15.0
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
