[REEF-1942] Add ability to wait for Driver to complete to REEF.NET Client

• Type: New Feature
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 0.17
• Component/s: REEF.NET
• Assignee: Markus Weimer
• Reporter: Markus Weimer
• Created: 30/Oct/17 23:54
• Updated: 06/Nov/17 18:53
• Resolved: 06/Nov/17 18:53

Description

REEF.NET's client today supports fire-and-forget semantics for Job submission with no canonical way for the client to know if and when a Driver completes. This is impractical for unit tests and other applications that need to know when the Driver exited.

We should add an API to the REEF.NET Client which allows for its users to know when the Driver is done. Such an API should be either implementable by each runtime or, ideally, have a single implementation that works across runtimes.

Issue Links

• blocks: REEF-1271 Add better test reporting APIs to REEF.NET
• contains: REEF-374 reef.net local execution does not return job completion status
• is blocked by: REEF-1943 IJobSubmissionResult.DriverUrl isn't working
• is related to: REEF-1951 Make DriverStatus more robust
• links to: #1408
• links to: The branch I am working on