Sorry, that link was for BigQuery. It might make sense to add a similar
option to BigTable.

- Cham

On Mon, Sep 25, 2017 at 11:00 AM Chamikara Jayalath <[email protected]>
wrote:

> Seems like BigTableIO.Write can be run without validation [1]. Doesn't
> that work for your use-case ?
>
> - Cham
>
>
> https://github.com/apache/beam/blob/master/sdks/java/io/google-cloud-platform/src/main/java/org/apache/beam/sdk/io/gcp/bigquery/BigQueryIO.java#L1085
>
>
>
> On Mon, Sep 25, 2017 at 10:38 AM Steve Niemitz <[email protected]>
> wrote:
>
>> Would people be open to enhancing the BigtableIO sink to avoid checking if
>> the table being written to exists in BigtableIO.Write.validate()?
>>
>> There are a couple reasons I would like to disable the check:
>> - I would like to create the destination table as part of the flow, with
>> the schema defined by data read from the source during the flow.
>> - The machine that launches the flow may not even have the access needed
>> (both network and IAM permission) to access Bigtable.
>>
>> Any thoughts?
>>
>

Reply via email to