I don't think that should be the case. Also SchemaCoder will automatically set the UUID for such logical types.
On Mon, Jan 13, 2020 at 8:24 AM Alex Van Boxel <[email protected]> wrote: > OK, I've rechecked everything and eventually found the problem. The > problem is when you use a LogicalType backed back a Row, then the UUID > needs to be set to make it work. (this is the case for Proto based > Timestamps). I'll create a fix. > > _/ > _/ Alex Van Boxel > > > On Mon, Jan 13, 2020 at 8:36 AM Reuven Lax <[email protected]> wrote: > >> Can you elucidate? All BeamSQL pipelines use schemas and I believe those >> test are working just fine on the Dataflow runner. In addition, there are a >> number of ValidatesRunner schema-aware pipelines that are running regularly >> on the Dataflow runner. >> >> On Sun, Jan 12, 2020 at 1:43 AM Alex Van Boxel <[email protected]> wrote: >> >>> Hey all, >>> >>> anyone tried master with a *schema aware pipeline* on Dataflow? I'm >>> testing some PR's to see if the run on Dataflow (as they are working on >>> Direct) but they got: >>> >>> >>> Workflow failed. Causes: The Dataflow job appears to be stuck because no >>> worker activity has been seen in the last 1h. You can get help with Cloud >>> Dataflow at >>> >>> because I got this I wanted to see if master (without my changes) also >>> have the same behaviour. >>> >>> It's easy to simulate: Just read for BigQuery with: >>> >>> BigQueryIO.readTableRowsWithSchema() >>> >>> it works with the classic: readTableRows(). >>> >>> _/ >>> _/ Alex Van Boxel >>> >>
