Let's not deprecate SparkStatusTracker (at least not until there's a suitable replacement that's just as easy to use). Deprecating it now would leave users with an unactionable warning and that's not great for users who try to keep their build warnings clean.
If you want to be really proactive in notifying anyone who might be affected by JobProgressListener's removal we could mark JobProgressListener (and the other listener implementations made into DeveloperAPIs in https://github.com/apache/spark/pull/648) as deprecated now and mention the deprecation in the 2.2.0 release notes. 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 >
