On Fri, Mar 24, 2017 at 1:18 PM, Ryan Blue <rb...@netflix.com> wrote: > For the status tracker, I'd like to see it replaced with something better > before deprecating it. I've been looking at it for implementing better > feedback in notebooks, and it looks sufficient for that at the moment. Is > there a reason to remove it other than that it differs from the rest API?
My original thinking was to eventually replace it with a programmatic API that exposes all the REST API information. Basically the REST API without the need to have an HTTP client. That still might be worth it in the future (just to avoid having sort of duplicate APIs), but at this point I'm happy with just changing the backend of the status tracker to not use JobProgressListener. -- Marcelo --------------------------------------------------------------------- To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
