Fix PlanCompiler
output type for DISTINCT
+ ORDER BY
#1298
Merged
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.
Relevant Issues
PlannerCompiler
w/SELECT DISTINCT
andORDER BY
returns a bag #1277Description
The
PlanCompiler
was outputting a bag whenDISTINCT
andORDER BY
were present in a query. A list should have been outputted asEvaluatingCompiler
outputs.PlanCompiler
rewrites theDISTINCT
to use theExprFunction
filter_distinct
to preserve a collection's distinct elements. This PR changes that function to return a list when the input is a list.Other Information
Updated Unreleased Section in CHANGELOG: [YES]
Any backward-incompatible changes? [NO]
Any new external dependencies? [NO]
Do your changes comply with the Contributing Guidelines
and Code Style Guidelines? [YES]
License Information
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.