You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hyukjin Kwon (Jira)" <ji...@apache.org> on 2019/11/13 00:54:00 UTC
[jira] [Assigned] (SPARK-29399) Remove old ExecutorPlugin API (or
wrap it using new API)
[ https://issues.apache.org/jira/browse/SPARK-29399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hyukjin Kwon reassigned SPARK-29399:
------------------------------------
Assignee: Marcelo Masiero Vanzin
> Remove old ExecutorPlugin API (or wrap it using new API)
> --------------------------------------------------------
>
> Key: SPARK-29399
> URL: https://issues.apache.org/jira/browse/SPARK-29399
> Project: Spark
> Issue Type: Sub-task
> Components: Spark Core
> Affects Versions: 3.0.0
> Reporter: Marcelo Masiero Vanzin
> Assignee: Marcelo Masiero Vanzin
> Priority: Major
>
> The parent bug is proposing a new plugin API for Spark, so we could remove the old one since it's a developer API.
> If we can get the new API into Spark 3.0, then removal might be a better idea than deprecation. That would be my preference since then we can remove the new elements added as part of SPARK-28091 without having to deprecate them first.
> If it doesn't make it into 3.0, then we should deprecate the APIs from 3.0 and manage old plugins through the new code being added.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org