You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@beam.apache.org by "Ahmet Altay (JIRA)" <ji...@apache.org> on 2017/07/24 20:22:00 UTC

[jira] [Commented] (BEAM-2673) BigQuery Sink should use the Load API

    [ https://issues.apache.org/jira/browse/BEAM-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16099069#comment-16099069 ] 

Ahmet Altay commented on BEAM-2673:
-----------------------------------

[~chamikara]] Given the added delay in https://github.com/apache/beam/pull/3630, should we work on fixing this issue for the 2.2.0 release?

> 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)