Skip to content

[SPARK-41958][CORE][3.3] Disallow arbitrary custom classpath with proxy user in cluster mode #41428

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
degant wants to merge 3 commits into from
Closed

[SPARK-41958][CORE][3.3] Disallow arbitrary custom classpath with proxy user in cluster mode #41428

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
bfba577
Backporting fix for SPARK-41958 to 3.3 branch from #39474
peter-toth Jan 10, 2023
d8a1794
Default to true and add migration guide
degant Jun 2, 2023
dede104
Add missing newline
degant Jun 5, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Default to true and add migration guide
  • Loading branch information
@degant
degant committed Jun 2, 2023
commit d8a17941999435d4886a9b1796a0b014ad0f41ed
2 changes: 1 addition & 1 deletion core/src/main/scala/org/apache/spark/internal/config/package.scala
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2361,5 +2361,5 @@ package object config {
.internal()
.version("3.3.3")
.booleanConf
.createWithDefault(false)
.createWithDefault(true)
}
1 change: 1 addition & 0 deletions docs/core-migration-guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,7 @@ license: |
## Upgrading from Core 3.2 to 3.3

- Since Spark 3.3, Spark migrates its log4j dependency from 1.x to 2.x because log4j 1.x has reached end of life and is no longer supported by the community. Vulnerabilities reported after August 2015 against log4j 1.x were not checked and will not be fixed. Users should rewrite original log4j properties files using log4j2 syntax (XML, JSON, YAML, or properties format). Spark rewrites the `conf/log4j.properties.template` which is included in Spark distribution, to `conf/log4j2.properties.template` with log4j2 properties format.
- Since Spark 3.3.3, `spark.submit.proxyUser.allowCustomClasspathInClusterMode` allows users to disable custom class path in cluster mode by proxy users. It still defaults to `true` to maintain backward compatibility.

## Upgrading from Core 3.1 to 3.2

Expand Down