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/05/21 05:35:40 UTC

[jira] [Updated] (SPARK-6359) Expose IMain binding as part of ILoop Developer API

     [ https://issues.apache.org/jira/browse/SPARK-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hyukjin Kwon updated SPARK-6359:
--------------------------------
    Labels: bulk-closed  (was: )

> Expose IMain binding as part of ILoop Developer API
> ---------------------------------------------------
>
>                 Key: SPARK-6359
>                 URL: https://issues.apache.org/jira/browse/SPARK-6359
>             Project: Spark
>          Issue Type: Improvement
>          Components: Spark Shell
>    Affects Versions: 1.3.0
>            Reporter: Dan McClary
>            Priority: Minor
>              Labels: bulk-closed
>
> In 1.2, some projects (e.g. Apache Zeppelin) rely on the ILoop exposing its IMain object for the purpose of binding UI variables to the underlying repl.  The privatization of these methods in 1.3.0 breaks projects which rely on this.
> The simplest resolution would be to provide a method to pass binds to the underlying IMain.  This maintains the privatization of the IMain, but allows 3rd parties to work around.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org