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

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

                Author: ASF GitHub Bot
            Created on: 16/Apr/20 11:34
            Start Date: 16/Apr/20 11:34
    Worklog Time Spent: 10m 
      Work Description: nielm commented on issue #11438: [BEAM-9505] Remove 
spurious error message in SpannerIO when streaming.
URL: https://github.com/apache/beam/pull/11438#issuecomment-614597327
 
 
   @chamikaramj 
   @allenpradeep
    Can you review please?
   
 
----------------------------------------------------------------
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:
[email protected]


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

    Worklog Id:     (was: 423404)
    Time Spent: 20m  (was: 10m)

> SpannerIO spurious error message with empty bundles
> ---------------------------------------------------
>
>                 Key: BEAM-9505
>                 URL: https://issues.apache.org/jira/browse/BEAM-9505
>             Project: Beam
>          Issue Type: Bug
>          Components: io-java-gcp
>    Affects Versions: 2.18.0, 2.19.0, 2.20.0
>            Reporter: Niel Markwick
>            Assignee: Niel Markwick
>            Priority: Minor
>             Fix For: 2.21.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> -When using DataflowRunner in streaming mode. DoFn.StartBundle is called 
> multiple times for the same bundle.-
> -This does not occur with DirectRunner.- 
> -This breaks DoFn's which require per-bundle setup and teardown  procedures.-
> When a bundle is empty (such as in streaming if a window is empty), SpannerIO 
> will report a spurious error message:
> {{IllegalStateException: Sorter should be null here}}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to