Hi Robert, Thanks for the suggestion. Threading out a blocking RemoteStreamEnvironment.execute() call and polling the monitoring REST API will work for now. Once the job transitions to running I will kill the thread and monitor the job through the REST API.
As for metrics, accumulators, and other job state I think I can get away with monitoring jobs through a combination of my own metrics system and the data exposed through the Flink Monitoring REST APIs [0]. I didn't find any JIRA issues related to my original request for being able to easily submit detached jobs through an ExecutionEnvironment. Does that sound like something the Flink team would be open to discussing? Thanks! [0] https://ci.apache.org/projects/flink/flink-docs-master/internals/monitoring_rest_api.html -- View this message in context: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Executing-detached-data-stream-programs-tp7268p7291.html Sent from the Apache Flink User Mailing List archive. mailing list archive at Nabble.com.
