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/12/03 23:11:24 UTC

[GitHub] [beam] boyuanzz commented on pull request #13421: [BEAM-9602] Add timer family support for python SDK

boyuanzz commented on pull request #13421:
URL: https://github.com/apache/beam/pull/13421#issuecomment-738437268


   > Rather than having a parallel path for TimerSpec and TimerFamilySpec throughout the whole stack, could we have only TimerParam right at the top which translates everything to a TimerFamilySpec and treat everything as timer families from there on?
   
   I was thinking about this and the more generic question for me is do we want to keep both original timer API and dynamic timer API. Overall the old static timer is a special case of dynamic timer but meanwhile we need to make sure we don't break existing usages.


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