You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Udi Meiri (Jira)" <ji...@apache.org> on 2021/09/10 20:45:00 UTC
[jira] [Commented] (BEAM-12442) RenameFields disregards renames in
nested fields with DataflowRunner
[ https://issues.apache.org/jira/browse/BEAM-12442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413382#comment-17413382 ]
Udi Meiri commented on BEAM-12442:
----------------------------------
I from what I can tell the fix (PR #14960) is in 2.32.0. Moving the fix version field to that version
> 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
> Priority: P2
> 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)