You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/09/01 23:36:00 UTC

[jira] [Work logged] (BEAM-10486) OffsetRestrictionTracker returning invalid split on completed restriction

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

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

                Author: ASF GitHub Bot
            Created on: 01/Sep/20 23:35
            Start Date: 01/Sep/20 23:35
    Worklog Time Spent: 10m 
      Work Description: sloflash commented on pull request #12258:
URL: https://github.com/apache/beam/pull/12258#issuecomment-685188147


   while experimenting with periodic sequence generator earlier today
   i realized that the direct runner kept calling @process although i had correctly set the defer_remainder 
   it does compute the restriction correctly and the checkpoint is correct however is there some way to test this explicitly?


----------------------------------------------------------------
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:
users@infra.apache.org


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

    Worklog Id:     (was: 477522)
    Time Spent: 1h 50m  (was: 1h 40m)

> OffsetRestrictionTracker returning invalid split on completed restriction
> -------------------------------------------------------------------------
>
>                 Key: BEAM-10486
>                 URL: https://issues.apache.org/jira/browse/BEAM-10486
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-py-core
>            Reporter: Luke Cwik
>            Assignee: Luke Cwik
>            Priority: P2
>             Fix For: 2.24.0
>
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> After a failed claim attempt, it is expected that the restriction tracker is done and any splits should return None.



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