On Fri, Mar 24, 2017 at 1:13 PM, Josh Rosen <joshro...@databricks.com> wrote: > 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.
I'm not planning on changing that API right now; we can look at it later if desired. > If you want to be really proactive in notifying anyone who might be affected > by JobProgressListener's removal we could mark JobProgressListener I'll make a change for that later. It will add warnings in the Spark build, but then we have a ton of those already... -- Marcelo --------------------------------------------------------------------- To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
