[ 
https://issues.apache.org/jira/browse/BEAM-9268?focusedWorklogId=383607&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-383607
 ]

ASF GitHub Bot logged work on BEAM-9268:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 07/Feb/20 14:22
            Start Date: 07/Feb/20 14:22
    Worklog Time Spent: 10m 
      Work Description: nielm commented on issue #10690: [BEAM-9268] SpannerIO: 
Add more documentation and warnings for unknown tables.
URL: https://github.com/apache/beam/pull/10690#issuecomment-583409088
 
 
   > Can you please create a JIRA and mention in the CL description ?
   Done: https://issues.apache.org/jira/browse/BEAM-9268
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 383607)
    Remaining Estimate: 0h
            Time Spent: 10m

> 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: 10m
>  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)

Reply via email to