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

Dedup (aka DISTINCT) support on PhysicalPlan #1914

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Conversation

mamcx
Copy link
Contributor

@mamcx mamcx commented Oct 28, 2024

Description of Changes

As the title says.

Expected complexity level and risk

1

Testing

Describe any testing you've done, and any testing you'd like your reviewers to do,
so that you're confident that all the changes work as expected!

  • Write a test you've completed here.
  • Write a test you want a reviewer to do here, so they can check it off when they're satisfied.

@mamcx mamcx self-assigned this Oct 28, 2024
@mamcx mamcx marked this pull request as ready for review November 11, 2024 15:53
@bfops
Copy link
Collaborator

bfops commented Jan 13, 2025

What's the impact/purpose of this change? Could you add more info to the PR description?

@mamcx @joshua-spacetime

@mamcx
Copy link
Contributor Author

mamcx commented Jan 13, 2025

Is not a priority for 1.0. Is to test that adding a new operator works horizontally across all the query engine

@mamcx mamcx added the release-any To be landed in any release window label Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backward-compatible release-1.0 release-any To be landed in any release window
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants