[jira] [Assigned] (SPARK-20066) Add explicit SecurityManager(SparkConf) constructor for backwards compatibility with Java

["Apache Spark (JIRA)" <ji...@apache.org>]

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

Apache Spark reassigned SPARK-20066:
------------------------------------

    Assignee:     (was: Apache Spark)

> Add explicit SecurityManager(SparkConf) constructor for backwards compatibility with Java
> -----------------------------------------------------------------------------------------
>
>                 Key: SPARK-20066
>                 URL: https://issues.apache.org/jira/browse/SPARK-20066
>             Project: Spark
>          Issue Type: Bug
>          Components: Spark Core
>    Affects Versions: 2.1.1, 2.2.0
>            Reporter: Mark Grover
>
> SPARK-19520 added an optional argument (ioEncryptionKey) to Security Manager class. And, it has a default value, so life is great.
> However, that's not enough when invoking the class from Java. We didn't see this before because the SecurityManager class is private to the spark package and all the code that uses it is Scala.
> However, I have some code that was extending it, in Java, and that code breaks because Java can't access that default value (more details [here|http://stackoverflow.com/questions/13059528/instantiate-a-scala-class-from-java-and-use-the-default-parameters-of-the-const]).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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