[
https://issues.apache.org/jira/browse/BEAM-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15976257#comment-15976257
]
ASF GitHub Bot commented on BEAM-2023:
--------------------------------------
GitHub user reuvenlax opened a pull request:
https://github.com/apache/beam/pull/2609
[BEAM-2023] Support dynamic schemas
The final step in this series of changes to BigQueryIO.
Now that we support dynamic, value-dependent tables, also add support for
per-table schemas. These can be set via a user-defined function mapping table
to schema. This function can access side inputs, so it's also possible to set
the per-table schemas using a map-valued PCollectionView.
This PR also removes direct references to BigQueryIO.Write from the public
PTransforms, as those transforms are meant to be usable without having an
instance of BigQueryIO.Write
R: @jkff
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/reuvenlax/incubator-beam per_table_schemas
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/beam/pull/2609.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 #2609
----
commit 437d5b502221ce6d3ce90a13a56419976b127a9d
Author: Reuven Lax <re...@google.com>
Date: 2017-04-19T14:56:52Z
Support dynamic schemas and remove Write reference from nexted classes.
----
> BigQueryIO.Write needs a way of dynamically specifying table schemas
> --------------------------------------------------------------------
>
> Key: BEAM-2023
> URL: https://issues.apache.org/jira/browse/BEAM-2023
> Project: Beam
> Issue Type: Bug
> Components: sdk-java-gcp
> Reporter: Reuven Lax
> Assignee: Reuven Lax
>
> BigQuery can now specify value-dependent tables, but the schema for all of
> them must be constant and set a priori. We need a way to dynamically choose
> schemas for tables.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
