[ 
https://issues.apache.org/jira/browse/BEAM-11648?focusedWorklogId=572272&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-572272
 ]

ASF GitHub Bot logged work on BEAM-11648:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 25/Mar/21 20:08
            Start Date: 25/Mar/21 20:08
    Worklog Time Spent: 10m 
      Work Description: nehsyc commented on a change in pull request #11767:
URL: https://github.com/apache/beam/pull/11767#discussion_r601805276



##########
File path: 
sdks/java/io/google-cloud-platform/src/main/java/org/apache/beam/sdk/io/gcp/bigquery/BigQueryIO.java
##########
@@ -2285,6 +2292,19 @@ static String getExtractDestinationUri(String 
extractDestinationDir) {
       return toBuilder().setNumFileShards(numFileShards).build();
     }
 
+    /**
+     * Control how many parallel streams are used when using Storage API 
writes. Applicable only
+     * when also setting {@link #withTriggeringFrequency}. To let runner 
determine the sharding at
+     * runtime, set {@link #withAutoSharding()} instead.

Review comment:
       Drive-by comment: Would this be misleading? Since auto-sharding is not 
yet integrated.




-- 
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: 572272)
    Time Spent: 44h  (was: 43h 50m)

> Implement new BigQuery sink (Vortex)
> ------------------------------------
>
>                 Key: BEAM-11648
>                 URL: https://issues.apache.org/jira/browse/BEAM-11648
>             Project: Beam
>          Issue Type: New Feature
>          Components: extensions-java-gcp
>            Reporter: Reuven Lax
>            Assignee: Reuven Lax
>            Priority: P2
>          Time Spent: 44h
>  Remaining Estimate: 0h
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to