feat: functional dependencies in JOIN#23047
Open
zyuiop wants to merge 1 commit into
Open
Conversation
This enables aggregate queries that SELECT over two tables, only one of which is in the WHERE, but for which the join condition guarantees a functional dependency.
|
Thank you for opening this pull request! Reviewer note: cargo-semver-checks reported the current version number is not SemVer-compatible with the changes in this pull request (compared against the base branch). Details |
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.
This enables aggregate queries that SELECT over two tables, only one of which is in the WHERE, but for which the join condition guarantees a functional dependency.
Rationale for this change
Currently, queries such as
don't work, because datafusion does not detect that
PaperConflict.conflictTypeuniquely depends onPaper.paperId, and therefore can be included in the SELECT clause.This PR attempts to address this problem, although the solution is a bit clunky and I am not certain it works in all cases.
What changes are included in this PR?
Extend
FunctionalDependencies::joinso that it takes as parameter a list of columns which appear in equality comparisons in the ON clause of the join.This makes it possible to extend functional dependencies across the JOIN if the source columns of a dependency appear in the list.
Alternative approach: this feature may alternatively be realized in an analyser step, but the problem is that the aggregate/project validity check is done in SqlToRel, that is before the analyser runs.
Are these changes tested?
Yes
Are there any user-facing changes?