Add support for open-source Spark. #257
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
YuryChebiryak
changed the title
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.
Goal: Add support for open-source Spark as a platform for on-premise spark clusters.
Changes: Most macros works the same way as for the Databricks or Snowflake platform. Main change is for hub, satellite and link macros where QUALIFY keyword was being used in the default implementation, which is currently not supported by open-source Spark (see this Jira which is open since 2020 https://issues.apache.org/jira/browse/SPARK-31561 ). As a work-around, we define a CTE named qualify_workaround to perform the windowing functions first (ROW_NUMBER, LAG) and then perform the select.
Testing:
Has been tested for Spark 3.5.0.
Next steps:
Once
qualifykeyword is supported by open-source Spark (eg if Databricks contributes back to the open-source community), the macros can be simplified greatly by invoking default implementations.