spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcelo Masiero Vanzin (Jira)" <>
Subject [jira] [Created] (SPARK-29399) Remove old ExecutorPlugin API (or wrap it using new API)
Date Tue, 08 Oct 2019 19:48:00 GMT
Marcelo Masiero Vanzin created SPARK-29399:

             Summary: Remove old ExecutorPlugin API (or wrap it using new API)
                 Key: SPARK-29399
             Project: Spark
          Issue Type: Sub-task
          Components: Spark Core
    Affects Versions: 3.0.0
            Reporter: Marcelo Masiero Vanzin

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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message