Docs: document the Transaction write API (#1008) - #3809
Open
iSparshP wants to merge 1 commit into
Open
Conversation
Author
|
@kevinjqliu this picks up #1008 after the handoff from @pramila-bishnoi. It's a small docs-only change: adds the Transaction write API (which was missing from this section) and a Delete subsection so each operation has its own heading. Would appreciate a review when you get a chance. Thanks! |
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.
Addresses #1008. The write docs already cover append / overwrite /
overwrite_filter/ delete /dynamic_partition_overwrite/ upsert, but the Transaction API was undocumented in this section. This adds a "Write API modes:TableandTransaction" subsection explaining both modes, the single-atomic-commit guarantee, and combining schema + data changes in one commit. It also adds a### Deleteheading so each operation is its own subsection, per the issue.Builds on the direction from the earlier #2770 and #3647 (both closed by the stale bot). Handed off by @pramila-bishnoi on the issue thread.
Closes #1008