"No schema specified on job or table." Error when writing an empty table using .saveAsTypedBigQuery #884
Assignees
Labels
bug
Something isn't working
Comments
|
@fallonchen IIRC you looked at a similar one? |
|
I think I might have made a mistake. I just ran into the same issue with saveAsBigQuery. |
|
I'm closing this issue because it seems to be a regression with Apache Beam. |
|
@Tomczik76 did you find a BEAM Jira ticket? |
|
Let's keep this open until it's resolved upstream and in Scio :) |
|
Upstream bug https://issues.apache.org/jira/browse/BEAM-3067 |
|
Just to be clear BEAM-3067 states this happens with DirectRunner. I encountered this bug using the DataFlowRunner. |
|
Verified that this has been resolved in Scio 0.4.6 / Beam 2.2.0. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I repeatedly had a failed job with:
"errors" : [ { "message" : "No schema specified on job or table.", "reason" : "invalid" } ]When writing using .saveAsTypedBigQuery on a @BigQueryType.toTable case class when writing an empty table.
@BigQueryType.toTable case class Usage(an: String)Also, I didn't encounter a failure when using
.saveAsBigQueryand giving aTableSchemaThe text was updated successfully, but these errors were encountered: