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 E233B200D0B for ; Tue, 29 Aug 2017 02:15:08 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id E0A2E165D0C; Tue, 29 Aug 2017 00:15:08 +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 3441C165D09 for ; Tue, 29 Aug 2017 02:15:08 +0200 (CEST) Received: (qmail 66448 invoked by uid 500); 29 Aug 2017 00:15:05 -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 66439 invoked by uid 99); 29 Aug 2017 00:15:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Aug 2017 00:15:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 448761A3447 for ; Tue, 29 Aug 2017 00:15:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-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-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id XnY5cyfqvmXL for ; Tue, 29 Aug 2017 00:15:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 4DD9E5FB51 for ; Tue, 29 Aug 2017 00:15:01 +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 60ABFE018C for ; Tue, 29 Aug 2017 00:15: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 0AEE723F05 for ; Tue, 29 Aug 2017 00:15:00 +0000 (UTC) Date: Tue, 29 Aug 2017 00:15:00 +0000 (UTC) From: "Lara Schmidt (JIRA)" To: commits@beam.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (BEAM-2817) Bigquery queries should allow options to run in batch mode or not MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 29 Aug 2017 00:15:09 -0000 Lara Schmidt created BEAM-2817: ---------------------------------- Summary: Bigquery queries should allow options to run in batch mode or not Key: BEAM-2817 URL: https://issues.apache.org/jira/browse/BEAM-2817 Project: Beam Issue Type: Bug Components: sdk-java-gcp Affects Versions: 2.0.0 Reporter: Lara Schmidt Assignee: Chamikara Jayalath When bigquery read does a query it sets the mode to batch. A batch query can be very slow to schedule as it batches it with other queries. However it doesn't use batch quota which is better for some cases. However, in some cases a fast query is better (especially in timed tests). It would be a good idea to have a configuration to the bigquery source to set this per-read. -- This message was sent by Atlassian JIRA (v6.4.14#64029)