Open
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
1 participant
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.
Title:
Fix JAVA_HOME for ARM64 (Mac M-series) architecture
Description:
This PR fixes an issue where PySpark failed to initialize on systems using ARM64 architecture (such as Mac M1/M2/M3/M4/M5 chips) due to a hardcoded JAVA_HOME path in the Dockerfile.
Changes:
Why this is needed:
Without this change, the airflow standalone services and Jupyter notebooks fail to start PySpark sessions on Mac M-series machines because the Java gateway process cannot be found at the previous hardcoded path.
Verification:
Built the image using docker compose up --build.
Verified that the IPython startup scripts (01-spark-init.py) successfully create a Spark session on an ARM64 host.
Confirmed the %%sql magic is working correctly in Jupyter Lab.