Clarify in join doc that fields can be copied from the right side without assignment #5206
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.
What's changing
A small clarification is being made to the
join
operator doc.Why
A community user recently spotted this omission.
Details
In the user's own words from the community Slack thread:
At first I toyed with updating it to
[<field>:=<right-expr>|<right-field>, ...]
, but that may give the impression that only an explicit right-side field name would be supported, but expressions such as function calls cook up field names on the fly, e.g., this change from the Inner Join example in thejoin
tutorial:So instead I've taken the approach of making the assignment portion appear optional, knowing that errors will further communicate the limitations if the user tries something unworkable, e.g.,