[
https://issues.apache.org/jira/browse/BEAM-9602?focusedWorklogId=519914&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-519914
]
ASF GitHub Bot logged work on BEAM-9602:
----------------------------------------
Author: ASF GitHub Bot
Created on: 03/Dec/20 23:11
Start Date: 03/Dec/20 23:11
Worklog Time Spent: 10m
Work Description: 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:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 519914)
Time Spent: 50m (was: 40m)
> Support Dynamic Timer in Python SDK over FnApi
> ----------------------------------------------
>
> Key: BEAM-9602
> URL: https://issues.apache.org/jira/browse/BEAM-9602
> Project: Beam
> Issue Type: New Feature
> Components: sdk-py-harness
> Reporter: Boyuan Zhang
> Priority: P3
> Time Spent: 50m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
