Yes (if I understand correctly what you aim for).
On 01/19/2016 05:57 PM, Saiph Kappa wrote:
> Thanks for your reply Mattias. So it is not possible to open a socket
> server in the JobGraph and having it open during the lifetime of the
> job, is that what you are saying? And it is required to have
Thanks for your reply Mattias. So it is not possible to open a socket
server in the JobGraph and having it open during the lifetime of the job,
is that what you are saying? And it is required to have an external process
to open that socket server.
On Tue, Jan 19, 2016 at 5:38 PM, Matthias J. Sax
Your "SocketWriter-Thread" code will run on your client. All code in
"main" runs on the client.
execute() itself runs on the client, too. Of course, it triggers the job
submission to the cluster. In this step, the assembled job from the
previous calls is translated into the JobGraph which is submi
Hi,
This is a simple example that I found using Flink Stream. I changed it so
the flink client can be executed on a remote cluster, and so that it can
open a socket server to ship its results for any other consumer machine. It
seems to me that the socket server is not being open in the remote clus
