[
https://issues.apache.org/jira/browse/BEAM-867?focusedWorklogId=127156&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-127156
]
ASF GitHub Bot logged work on BEAM-867:
---------------------------------------
Author: ASF GitHub Bot
Created on: 25/Jul/18 08:42
Start Date: 25/Jul/18 08:42
Worklog Time Spent: 10m
Work Description: oskoi commented on issue #4119: [BEAM-867] Add schema
update options to BigQueryIO
URL: https://github.com/apache/beam/pull/4119#issuecomment-407680150
@aaltay @reuvenlax what's the status of this issue BEAM-876
(https://issues.apache.org/jira/browse/BEAM-876)? Does anyone do it?
----------------------------------------------------------------
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: 127156)
Time Spent: 20m (was: 10m)
> 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: 20m
> 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)
