On Thu, Jan 14, 2016 at 4:00 PM, kovas boguta <kovas.bog...@gmail.com> wrote: > > For a "real" solution, the REPL needs seem related to the WebUI, which I > haven't studied yet. One would want a fairly detailed view into the running > execution graph, possibly but not necessarily as an HTTP api. > > I haven't studied how the execution graph is instantiated yet, again I'd > rather inject this logic via composition than have it hard-coded into the > existing implementation. Will have to study more. >
Is there a way to hook into the global or 'per-job' event stream? One approach could be to allow the user to submit a listener on the event stream, which presumably contains all the relevant information about availability and location of result partitions (and other stuff of interest). Writing a little service to send that info down to a client is pretty easy from there.
