[
https://issues.apache.org/jira/browse/BEAM-12442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399848#comment-17399848
]
Beam JIRA Bot commented on BEAM-12442:
--------------------------------------
This issue is assigned but has not received an update in 30 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> RenameFields disregards renames in nested fields with DataflowRunner
> --------------------------------------------------------------------
>
> Key: BEAM-12442
> URL: https://issues.apache.org/jira/browse/BEAM-12442
> Project: Beam
> Issue Type: Bug
> Components: sdk-java-core
> Affects Versions: 2.26.0
> Reporter: Matthew Ouyang
> Assignee: Reuven Lax
> Priority: P2
> Labels: stale-assigned
> Fix For: 2.33.0
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Summary - When applying a `RenameFields` followed by
> BigQueryUtils.toTableRow(Row), renames on nested fields were not being
> applied when using DataflowRunner. DirectRunner appeared to be fine. This
> led to a failed BigQueryIO.Write.
> Expected Behaviour - (field0_1.field1_0, nestedStringField) ->
> field0_1.nestedStringField and successful BQ insert
> Actual Behaviour - (field0_1.field1_0, nestedStringField) ->
> field0_1.field1_0 and failed BQ insert because field0_1.field1_0 was not in
> the target BQ table
> Thread from Users mailing list -
> https://lists.apache.org/thread.html/rd33a6f2bd8454cf650d70795bcdbbb873f988a557133d3bdbfc56cfc%40%3Cuser.beam.apache.org%3E
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
