Skip to content
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

Merged
merged 6 commits into from
Aug 21, 2024
Merged

Conversation

EpsilonPrime
Copy link
Member

Defines the Mark Join used by a number of engines in query rewrites.

Copy link
Member

@westonpace westonpace left a 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.

site/docs/relations/logical_relations.md Outdated Show resolved Hide resolved
westonpace
westonpace previously approved these changes Aug 19, 2024
Copy link
Contributor

@jacques-n jacques-n left a 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.

site/docs/relations/logical_relations.md Outdated Show resolved Hide resolved
site/docs/relations/logical_relations.md Outdated Show resolved Hide resolved
@jacques-n jacques-n merged commit bc1b93f into substrait-io:main Aug 21, 2024
13 checks passed
@EpsilonPrime EpsilonPrime deleted the mark_join3 branch September 15, 2024 03:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants