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

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

                Author: ASF GitHub Bot
            Created on: 07/Jun/18 04:01
            Start Date: 07/Jun/18 04:01
    Worklog Time Spent: 10m 
      Work Description: stale[bot] commented on issue #4119: [BEAM-867] Add 
schema update options to BigQueryIO
URL: https://github.com/apache/beam/pull/4119#issuecomment-395285705
 
 
   This pull request has been marked as stale due to 60 days of inactivity. It 
will be closed in 1 week if no further activity occurs. If you think that’s 
incorrect or this pull request requires a review, please simply write any 
comment. If closed, you can revive the PR at any time and @mention a reviewer 
or discuss it on the [email protected] list. Thank you for your 
contributions.
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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: 109624)
            Time Spent: 10m
    Remaining Estimate: 0h

> Support set/delete of timers by ID in Flink runner
> --------------------------------------------------
>
>                 Key: BEAM-867
>                 URL: https://issues.apache.org/jira/browse/BEAM-867
>             Project: Beam
>          Issue Type: New Feature
>          Components: runner-flink
>            Reporter: Kenneth Knowles
>            Assignee: Aljoscha Krettek
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> This is a prerequisite for full support of BEAM-27, and related to BEAM-35.
> My current understanding is that this might be actually removed from Flink 
> itself, and needs implementation in terms of state. It might be reasonable to 
> just remove deletion from Beam; it is just a nice-to-have for user experience 
> IMO, and perhaps a performance help for certain runners.
> (Since I am filing individual tickets for each runner, generalized discussion 
> should probably be on the dev list directly on or BEAM-35)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to