Yes, something like that. Although, this would be an MVP for this purpose which has minimal impacts on next releases. Moreover, I think clients are too specific to be included as API because each user will have their own way to implement a stop, start, or whatever (of course a base client is welcome :)). For instance, we have implemented one, using REST API + async(detached) job.
Also, one thing I forgot in the previous example is that abstract execute should return a JobSubmissionResult instead of JobExecutionResult. But of course, just my point of view. -- View this message in context: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Detached-execution-API-tp14366p14369.html Sent from the Apache Flink User Mailing List archive. mailing list archive at Nabble.com.
