GitHub user chamikaramj opened a pull request:
https://github.com/apache/beam/pull/1978
[BEAM-1463] Updates BigQuery read transform to handle 'null' fields
properly for DirectRunner
Updates BigQuery read transform so that DirectRunner handles 'null' fields
properly.
Before this change, for DirectRunner, a record (dictionary) returned by
BigQuery read transform did not contain keys for fields that are 'null'. For
DataflowRunner, these fields are available with value 'None'.
I believe, retaining these fields value 'None' to be the proper behavior
here.
This change makes these two runners consistent when it comes to handling
BigQuery 'null' values.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/chamikaramj/beam
reading_null_fields_directrunner
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/beam/pull/1978.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1978
----
commit f6a94610b674760075c3c0af66b7b03da154f2bc
Author: Chamikara Jayalath <[email protected]>
Date: 2017-02-10T22:19:53Z
Updates BigQuery read transform so that DirectRunner handles 'null' fields
properly.
Before this change, for DirectRunner, a record (dictionary) returned by
BigQuery read transform will not contain keys for fields that are 'null'. For
DataflowRunner, these fields will be available with value 'None'.
I believe, retaining these fields value 'None' to be the proper behavior
here.
This change makes these two runners consistent when it comes to handling
BigQuery 'null' values.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
