+1 for deprecating JobProgressListener and removing it eventually. Thanks for working toward a better back-end for the UI.
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? rb On Fri, Mar 24, 2017 at 1:05 PM, Marcelo Vanzin <van...@cloudera.com> wrote: > On Fri, Mar 24, 2017 at 12:07 PM, Josh Rosen <joshro...@databricks.com> > wrote: > > I think that it should be safe to remove JobProgressListener but I'd > like to > > keep the SparkStatusTracker API. > > Thanks Josh. I can work with that. My main concern would be keeping > the listener around. > > Is it worth it to add a deprecated annotation to it? > > -- > Marcelo > > --------------------------------------------------------------------- > To unsubscribe e-mail: dev-unsubscr...@spark.apache.org > > -- Ryan Blue Software Engineer Netflix
