[
https://issues.apache.org/jira/browse/BEAM-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16099077#comment-16099077
]
Chamikara Jayalath commented on BEAM-2673:
------------------------------------------
I think the fix here is to add a new BQ sink (which will work for both Direct
and Dataflow runners) which will be a considerably large change. I agree that
we should prioritize this but not sure if 2.2.0 is viable.
Also, IIUC, currently the delay only gets hit at DirectRunner when using
WRITE_TRUNCATE which is not that severe.
> BigQuery Sink should use the Load API
> -------------------------------------
>
> Key: BEAM-2673
> URL: https://issues.apache.org/jira/browse/BEAM-2673
> Project: Beam
> Issue Type: Bug
> Components: sdk-py
> Reporter: Sourabh Bajaj
> Assignee: Ahmet Altay
>
> Currently the BigQuery sink is written to by using the streaming api in the
> direct runner. Instead we should just use the load api and also simplify the
> management of different create and write disposition.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
