Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id B8FF0200CCF for ; Mon, 24 Jul 2017 22:46:03 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id B7CFC165BCD; Mon, 24 Jul 2017 20:46:03 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 090B8165BCC for ; Mon, 24 Jul 2017 22:46:02 +0200 (CEST) Received: (qmail 85551 invoked by uid 500); 24 Jul 2017 20:46:02 -0000 Mailing-List: contact commits-help@beam.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@beam.apache.org Delivered-To: mailing list commits@beam.apache.org Received: (qmail 85542 invoked by uid 99); 24 Jul 2017 20:46:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Jul 2017 20:46:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id CC7B6C1584 for ; Mon, 24 Jul 2017 20:46:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id w3R64hCtU7zZ for ; Mon, 24 Jul 2017 20:46:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id D4EA55FD3D for ; Mon, 24 Jul 2017 20:46:00 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 5DA73E00A7 for ; Mon, 24 Jul 2017 20:46:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 1CE6C21EE3 for ; Mon, 24 Jul 2017 20:46:00 +0000 (UTC) Date: Mon, 24 Jul 2017 20:46:00 +0000 (UTC) From: "Ahmet Altay (JIRA)" To: commits@beam.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (BEAM-2673) BigQuery Sink should use the Load API MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 24 Jul 2017 20:46:03 -0000 [ https://issues.apache.org/jira/browse/BEAM-2673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16099098#comment-16099098 ] Ahmet Altay commented on BEAM-2673: ----------------------------------- Is not it also hit when python streaming is used with DataflowRunner ? > 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)