[Bug]: BQ TableRow does not accept column named 'f'

[RustedBones]

What happened?

When working with a BQ table with a column named 'f', construction of a TableRow object fails with

java.lang.IllegalArgumentException: Can not set java.util.List field com.google.api.services.bigquery.model.TableRow.f to java.lang.String

This happens because TableRow is a GenericJson and has a key field named f expecting a List<TableCell>.

When reading the javadoc for TableRow, it seems to me that this model is supposed to represent a BQ resultset in the form

{
  "f": [{"v":  1}, {"v": "value"}]
}

beam abuses the GenericJson capability and relies on the unknown fields to encode the result in the form

{
   "column1": 1,
   "column2": "value"
}

Issue Priority

Priority: 2 (default / most bugs should be filed as P2)

Issue Components

• Component: Python SDK
• Component: Java SDK
• Component: Go SDK
• Component: Typescript SDK
• Component: IO connector
• Component: Beam YAML
• Component: Beam examples
• Component: Beam playground
• Component: Beam katas
• Component: Website
• Component: Infrastructure
• Component: Spark Runner
• Component: Flink Runner
• Component: Samza Runner
• Component: Twister2 Runner
• Component: Hazelcast Jet Runner
• Component: Google Cloud Dataflow Runner

[Abacn]

This is a longstanding issue - similar fix made on #16872 (still has edge case left there). Which write method are you using (FILE_LOAD or STORAGE_WRITE_API) ?

[RustedBones]

This is not related to any BQ method.

The problem lies on the model itself where the following fails

new TableRow().set("f", data);

So any BQ code attempting to set a field named f fails. This can happen for any BQ method

[github-actions]

This issue has been marked as stale due to 150 days of inactivity. It will be closed in 30 days if no further activity occurs. If you think that’s incorrect or this issue still needs to be addressed, please simply write any comment. If closed, you can reopen the issue at any time. Thank you for your contributions.

[github-actions]

This issue has been closed due to lack of activity. If you think that is incorrect, you can reopen the issue at any time.