GitHub user tillrohrmann opened a pull request:

    https://github.com/apache/flink/pull/3311

    Let RpcService.scheduleRunnable return a ScheduledFuture

    This PR is based #3310.
    
    The returned ScheduledFuture instance allows to cancel a scheduled runnable 
and obtain
    the delay until the runnable will be executed. Furthermore, it allows to 
wait on the
    completion of the runnable.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/tillrohrmann/flink 
generalizeRpcServiceScheduleMethod

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/3311.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3311
    
----
commit 639edf235ffee924e0fba56313cb51f825e3a46d
Author: Till Rohrmann <[email protected]>
Date:   2017-02-14T15:50:43Z

    [FLINK-5798] [rpc] Let the RpcService provide a ScheduledExecutorService
    
    This PR adds the getScheduledExecutorService method to the RpcService 
interface. So
    henceforth all RpcService implementations have to provide a 
ScheduledExecutorService
    implementation.
    
    Currently, we only support the AkkaRpcService. The AkkaRpcService returns a
    ScheduledExecutorService proxy which forwards the schedule calls to the 
ActorSystem's
    internal scheduler.

commit 4c58378372867c43ce4d65fa51d609cbb4a95587
Author: Till Rohrmann <[email protected]>
Date:   2017-02-14T19:40:30Z

    [FLINK-5799] [rpc] Let RpcService.scheduleRunnable return a ScheduledFuture
    
    The returned ScheduledFuture instance allows to cancel a scheduled runnable 
and obtain
    the delay until the runnable will be executed. Furthermore, it allows to 
wait on the
    completion of the runnable.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to