Skip to content

[ENHANCEMENT] Set operator limitation for data-intensive operators #3731

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

Open
LantaoJin opened this issue Jun 4, 2025 · 0 comments · May be fixed by #3749
Open

[ENHANCEMENT] Set operator limitation for data-intensive operators #3731

LantaoJin opened this issue Jun 4, 2025 · 0 comments · May be fixed by #3749
Assignees
Labels
calcite calcite migration releated enhancement New feature or request

Comments

@LantaoJin
Copy link
Member

Is your feature request related to a problem?
From 3.0.0, calcite engine provides more power to support complex operators such as join. But SQL plugin still leverage coordinator node to run all operators in memory if pushdown doesn't work. So configurable operator limitations are required for that.

What solution would you like?
Add configurable limitations for each high cost operators.

What alternatives have you considered?
Keep as-is and limit by memory monitor.

Do you have any additional context?
Add any other context or screenshots about the feature request here.

@LantaoJin LantaoJin added enhancement New feature or request untriaged calcite calcite migration releated and removed untriaged labels Jun 4, 2025
@github-project-automation github-project-automation bot moved this to Not Started in PPL 2025 Jun 6, 2025
@LantaoJin LantaoJin self-assigned this Jun 6, 2025
@LantaoJin LantaoJin changed the title [ENHANCEMENT] Set operator limitation for high cost operators [ENHANCEMENT] Set operator limitation for data-intensive operators Jun 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
calcite calcite migration releated enhancement New feature or request
Projects
Status: Not Started
Development

Successfully merging a pull request may close this issue.

1 participant