Fix!: Have Spark put CTE at front of insert #2086
Merged
Conversation
This file contains 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
eakmanrq
force-pushed
the
eakmanrq/fix_spark_ctes_insert
branch
from
3832deb to
27d1a99
Compare
eakmanrq
changed the title
georgesittas
approved these changes
Aug 17, 2023
eakmanrq
force-pushed
the
eakmanrq/fix_spark_ctes_insert
branch
from
407001e to
fedada1
Compare
georgesittas
approved these changes
Aug 17, 2023
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.
This syntax is what I have used in the past (with Spark 2.4) and confirmed that this works with Spark 3.2 and latest Databricks release. Newer releases of Databricks (and likely Spark) do support having the CTE after the INSERT but this format is more universally supported.