-
Notifications
You must be signed in to change notification settings - Fork 158
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: define mark join #682
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't find the explanation sufficient and have proposed some alternate wording.
Co-authored-by: Weston Pace <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A minor request to be super clear on output column types and ordering.
It doesn't necessarily need to be resolved here but we should really update the text of join operations to better clarify their output column ordering and types. The current text reads:
Direct Output Order: The emit order of the left input followed by the emit order of the right input.
That is no longer true with many of these join types.
Co-authored-by: Jacques Nadeau <[email protected]>
Co-authored-by: Jacques Nadeau <[email protected]>
Defines the Mark Join used by a number of engines in query rewrites.