You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Bryan Cutler (JIRA)" <ji...@apache.org> on 2019/01/08 19:28:00 UTC
[jira] [Resolved] (SPARK-26349) Pyspark should not accept insecure
p4yj gateways
[ https://issues.apache.org/jira/browse/SPARK-26349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bryan Cutler resolved SPARK-26349.
----------------------------------
Resolution: Fixed
Fix Version/s: 3.0.0
Issue resolved by pull request 23441
[https://github.com/apache/spark/pull/23441]
> Pyspark should not accept insecure p4yj gateways
> ------------------------------------------------
>
> Key: SPARK-26349
> URL: https://issues.apache.org/jira/browse/SPARK-26349
> Project: Spark
> Issue Type: Improvement
> Components: PySpark
> Affects Versions: 3.0.0
> Reporter: Imran Rashid
> Assignee: Imran Rashid
> Priority: Blocker
> Fix For: 3.0.0
>
>
> Pyspark normally produces a secure py4j connection between python & the jvm, but it also lets users provide their own connection. Spark should fail fast if that connection is insecure.
> Note this is breaking a public api, which is why this is targeted at 3.0.0. SPARK-26019 is about adding a warning, but still allowing the old behavior to work, in 2.x
--
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