Docs: Clarify Spark branch write precedence over WAP branch#17007
Open
creator1999 wants to merge 1 commit into
Open
Docs: Clarify Spark branch write precedence over WAP branch#17007creator1999 wants to merge 1 commit into
creator1999 wants to merge 1 commit into
Conversation
3 tasks
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.
Closes #15916
The Spark writes docs still mention that a branch must already exist before writing, and also say that a WAP branch and branch identifier cannot both be specified.
This updates the “Writing to Branches” section for the Spark 4.1+ behavior by documenting how branch identifiers, the
branchwrite option, andspark.wap.branchare resolved.It also clarifies that
spark.wap.idandspark.wap.branchcannot be set together, and that the target branch may be created during the write.