[HOTFIX] Avoid shell evaluation of interpreter launch arguments - #5429
Draft
jongyoul wants to merge 1 commit into
Draft
[HOTFIX] Avoid shell evaluation of interpreter launch arguments#5429jongyoul wants to merge 1 commit into
jongyoul wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is this PR for?
This PR makes interpreter launch argument handling predictable across configuration and impersonation modes.
The dependency downloader command is now executed directly as an argument array instead of being evaluated as a shell command. Classpath wildcards, spaces, JVM options, and other configured values therefore remain literal process arguments.
When user impersonation is enabled,
%confand session-scoped configuration reject new environment-variable-style overrides. Existing operator-provided interpreter settings remain unchanged, and rejected updates are not partially applied.What type of PR is it?
Hot Fix
Todos
What is the Jira issue?
N/A
How should this be tested?
ZEPPELIN_LOCAL_IP=127.0.0.1 ./mvnw -pl zeppelin-server \ -Dtest=ConfInterpreterTest,SessionConfInterpreterTest,InterpreterShellScriptTest,StandardInterpreterLauncherTest test ./mvnw -pl zeppelin-server -DskipTests -Prat apache-rat:checkThe tests cover literal argument handling for classpaths, wildcards, JVM options, rejected environment overrides with impersonation enabled, allowed updates without impersonation, and preservation of existing operator configuration.
Screenshots (if appropriate)
N/A
Questions: