[Fix] No duplicates in list_intersect #9947
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.
This PR changes the
list_intersect
rewrite fromlist_filter(l1, (x) -> list_contains(l2, x))
tolist_filter(list_distinct(l1), (x) -> list_contains(l2, x))
. As a result,list_intersect
no longer returns duplicate values.However, the drawback of this change is that
list_intersect
now requireslist_distinct
, which uses duckdb'shistogram
aggregate function internally. Thehistogram
function cannot handle nested inputs yet, as well as some maximum values for huge integers and blobs. This limits the functionality oflist_intersect
but ensures correct results according to set logic.