You are viewing a plain text version of this content. The canonical link for it is here.

Posted to github@beam.apache.org by GitBox <gi...@apache.org> on 2020/04/22 22:51:02 UTC

[GitHub] [beam] lukecwik commented on issue #11472: [BEAM-2939] Migrate from HasSize to HasProgress interface for restriction trackers and use the progress value during sizing, splitting and reporting

lukecwik commented on issue #11472:
URL: https://github.com/apache/beam/pull/11472#issuecomment-618080046


   > Yes, I believe that `restriction size` is really syntactic sugar for `work remaining`. So in fixed size restrictions, `restriction size` should be able to be used to calculate the work remaining when we start and when we finish which then allows us to compute `work completed`.
   
   Thinking about this more, it doesn't seem like we can use restriction size since we don't have access to the reduced current restriction size as the tracker is making progress. This prevents us from passing it into the get_size methods in Java/Python/Go.


----------------------------------------------------------------
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