[
https://issues.apache.org/jira/browse/BEAM-12442?focusedWorklogId=608121&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-608121
]
ASF GitHub Bot logged work on BEAM-12442:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 07/Jun/21 21:33
Start Date: 07/Jun/21 21:33
Worklog Time Spent: 10m
Work Description: reuvenlax commented on pull request #14960:
URL: https://github.com/apache/beam/pull/14960#issuecomment-856278435
R: @mouyang
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 608121)
Time Spent: 20m (was: 10m)
> 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
> Time Spent: 20m
> 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)
