Mailing-List: contact commits-help@beam.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@beam.incubator.apache.org
Date: Wed, 20 Jul 2016 16:11:21 +0000 (UTC)
From: "Daniel Halperin (JIRA)" <jira@apache.org>
To: commits@beam.incubator.apache.org
Message-ID: <JIRA.12991170.1469031073000.84557.1469031081209@Atlassian.JIRA>
In-Reply-To: <JIRA.12991170.1469031073000@Atlassian.JIRA>
References: <JIRA.12991170.1469031073000@Atlassian.JIRA> <JIRA.12991170.1469031073647@arcas>
Subject: [jira] [Created] (BEAM-476) BigQueryIO.Write: schema not known at
 construction time
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 20 Jul 2016 16:11:25 -0000

Daniel Halperin created BEAM-476:
------------------------------------

             Summary: BigQueryIO.Write: schema not known at construction time
                 Key: BEAM-476
                 URL: https://issues.apache.org/jira/browse/BEAM-476
             Project: Beam
          Issue Type: New Feature
          Components: sdk-java-gcp
            Reporter: Daniel Halperin
            Priority: Minor


{{BigQueryIO.Write}} right now requires that the table schema be known at pipeline construction time. There are two feature requests:

1. It should be possible to operate in some modes (where table is not created, but only appended-to or truncated) where the schema need not be known at construction time.

2. It might be possible to operate in such a way that tables are created at runtime using a schema that is determined dynamically at runtime. We would possibly need the schema sent as a side input.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)