[
https://issues.apache.org/jira/browse/BEAM-11408?focusedWorklogId=556055&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-556055
]
ASF GitHub Bot logged work on BEAM-11408:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 22/Feb/21 22:18
Start Date: 22/Feb/21 22:18
Worklog Time Spent: 10m
Work Description: nehsyc commented on a change in pull request #14033:
URL: https://github.com/apache/beam/pull/14033#discussion_r580632678
##########
File path: sdks/python/apache_beam/io/gcp/bigquery.py
##########
@@ -1490,8 +1536,8 @@ def __init__(
schema (str,dict,ValueProvider,callable): The schema to be used if the
BigQuery table to write has to be created. This can be either specified
as a :class:`~apache_beam.io.gcp.internal.clients.bigquery.\
-bigquery_v2_messages.TableSchema`. or a `ValueProvider` that has a JSON string,
- or a python dictionary, or the string or dictionary itself,
+ bigquery_v2_messages.TableSchema`. or a `ValueProvider` that has a JSON
Review comment:
Thanks for pointing it out! Fixed and pushed a new commit.
----------------------------------------------------------------
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: 556055)
Time Spent: 8.5h (was: 8h 20m)
> GCP BigQuery sink (streaming inserts) uses runner determined sharding
> ---------------------------------------------------------------------
>
> Key: BEAM-11408
> URL: https://issues.apache.org/jira/browse/BEAM-11408
> Project: Beam
> Issue Type: Improvement
> Components: io-java-gcp
> Reporter: Siyuan Chen
> Assignee: Siyuan Chen
> Priority: P1
> Fix For: 2.28.0
>
> Time Spent: 8.5h
> Remaining Estimate: 0h
>
> Integrate BigQuery sink with shardable `GroupIntoBatches` (BEAM-10475) to
> allow runner determined dynamic sharding.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
