Re: [Proposal] Beam Newsletter

2017-09-25 Thread Reuven Lax
+1 On Thu, Sep 21, 2017 at 6:31 PM, Griselda Cuevas wrote: > Hi Beam Community, > > I have a proposal to start sending *monthly newsletters* to our dev and > user mailing lists. The idea is to summarize what's happening in the > project and keep everyone informed of what's happening, specially n

Re: BigTableIO table existence validation on write

2017-09-25 Thread Chamikara Jayalath
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 wrote: > Seems like BigTableIO.Write can be run without validation [1]. Doesn't > that work for your use-case ? > > - Cham > > > https://github.

Re: BigTableIO table existence validation on write

2017-09-25 Thread Chamikara Jayalath
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 Ste

BigTableIO table existence validation on write

2017-09-25 Thread Steve Niemitz
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

Re: Understanding BigQueryIO.Read performance and options

2017-09-25 Thread Steve Niemitz
Heh maybe we can merge our merge requests :P I just posted mine here as well: https://github.com/apache/beam/pull/3894 On Mon, Sep 25, 2017 at 11:30 AM, Eugene Kirpichov < kirpic...@google.com.invalid> wrote: > Hi, > I actually also made a PR for this myself the other day, but forgot to > update

Re: Understanding BigQueryIO.Read performance and options

2017-09-25 Thread Eugene Kirpichov
Hi, I actually also made a PR for this myself the other day, but forgot to update this thread, sorry :-| https://github.com/apache/beam/pull/3891 I also hit this conversion issue, and it is intended behavior because TableRow is the JSON representation of the data, and it matches what BigQuery does

Re: [Proposal] Beam Newsletter

2017-09-25 Thread Griselda Cuevas
Excellent -- I'll do the call for items this week so we have it ready in time for October. On 25 September 2017 at 07:36, Tyler Akidau wrote: > +1, would be great to get highlights of what's going on in the community. > Thank, Gris! > > On Fri, Sep 22, 2017 at 4:02 AM Steve Anderson wrote: > >

Re: [Proposal] Beam Newsletter

2017-09-25 Thread Tyler Akidau
+1, would be great to get highlights of what's going on in the community. Thank, Gris! On Fri, Sep 22, 2017 at 4:02 AM Steve Anderson wrote: > +1 would love this. Our team (maestro.io, we do livestreams for brands > like the Grammys and Playstation and use dataflow to collect massive > amounts o

Re: Understanding BigQueryIO.Read performance and options

2017-09-25 Thread Steve Niemitz
I've just about got something to send for a PR, I'll push it shortly. One thing I noticed though while running the BigQueryIO unit tests that I found strange. It looks like currently the TableRow / Avro / TableRowJsonCoder interaction changes BigQuery INTEGERs to strings in the public interface.