Details
-
Improvement
-
Status: Resolved
-
P2
-
Resolution: Fixed
-
2.16.0, 2.17.0, 2.18.0, 2.19.0
Description
The javadoc for SpannerIO.Write mentions in passing that the transform needs to know the DB schema for optimal performance. If the schema is created within the pipeline, then there is a race between the schema being created and SpannerIO reading it, leading to a potential performance penalty if SpannerIO does not know about the existence of some tables.
Javadoc needs to make this clearer and more explicit, and point the user at the Write.withSchemaReadySignal().
Pipeline needs to raise (rate limited) warnings if it sees writes being made to tables it does not know about (warnings can refer back to javadocs)
Attachments
Issue Links
- links to