[jira] [Updated] (BEAM-9268) SpannerIO: Better documentation and warning about creating tables in the pipeline
[ https://issues.apache.org/jira/browse/BEAM-9268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Niel Markwick updated BEAM-9268: Fix Version/s: 2.20.0 > SpannerIO: Better documentation and warning about creating tables in the > pipeline > - > > Key: BEAM-9268 > URL: https://issues.apache.org/jira/browse/BEAM-9268 > Project: Beam > Issue Type: Improvement > Components: io-go-gcp >Affects Versions: 2.16.0, 2.17.0, 2.18.0, 2.19.0 >Reporter: Niel Markwick >Assignee: Niel Markwick >Priority: Major > Labels: google-cloud-spanner, perfomance > Fix For: 2.20.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > 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) > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (BEAM-9268) SpannerIO: Better documentation and warning about creating tables in the pipeline
[ https://issues.apache.org/jira/browse/BEAM-9268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismaël Mejía updated BEAM-9268: --- Status: Open (was: Triage Needed) > SpannerIO: Better documentation and warning about creating tables in the > pipeline > - > > Key: BEAM-9268 > URL: https://issues.apache.org/jira/browse/BEAM-9268 > Project: Beam > Issue Type: Improvement > Components: io-go-gcp >Affects Versions: 2.16.0, 2.17.0, 2.18.0, 2.19.0 >Reporter: Niel Markwick >Assignee: Niel Markwick >Priority: Major > Labels: google-cloud-spanner, perfomance > Time Spent: 50m > Remaining Estimate: 0h > > 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) > -- This message was sent by Atlassian Jira (v8.3.4#803005)
