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

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

                Author: ASF GitHub Bot
            Created on: 09/Apr/20 06:55
            Start Date: 09/Apr/20 06:55
    Worklog Time Spent: 10m 
      Work Description: boyuanzz commented on issue #11314: [BEAM-9562] Send 
Timers over Data Channel as Elements
URL: https://github.com/apache/beam/pull/11314#issuecomment-611363247
 
 
   The 
[test_pardo_timers_clear](https://github.com/apache/beam/blob/master/sdks/python/apache_beam/runners/portability/fn_api_runner/fn_runner_test.py#L351-L389)
 fails with streaming Flink. The python sdk sends all 
timers(hold_timestamp=-INF with python default behavior) but only gets the 
timer with timestamp=20 back. Given the test only fails when streaming, it 
seems like something not correct with watermark(?). @lukecwik 
 
----------------------------------------------------------------
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: 419166)
    Time Spent: 16.5h  (was: 16h 20m)

> Remove timer from PCollection and treat timers as Elements 
> -----------------------------------------------------------
>
>                 Key: BEAM-9562
>                 URL: https://issues.apache.org/jira/browse/BEAM-9562
>             Project: Beam
>          Issue Type: New Feature
>          Components: sdk-java-harness, sdk-py-harness
>            Reporter: Boyuan Zhang
>            Assignee: Boyuan Zhang
>            Priority: Major
>             Fix For: 2.21.0
>
>          Time Spent: 16.5h
>  Remaining Estimate: 0h
>




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

Reply via email to