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

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 2.1.1, 2.2.0
• Component/s: Spark Core
• Assignee: Unassigned
• Reporter: Mark Grover
• Created: 23/Mar/17 03:29
• Updated: 23/Mar/17 16:59
• Resolved: 23/Mar/17 16:59

Description

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).

Issue Links

• links to: [Github] Pull Request #17393 (markgrover)