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

Make AdaptivePlanner optional in the FTE scheduler #21289

Merged
merged 2 commits into from
Mar 28, 2024

Conversation

dekimir
Copy link
Contributor

@dekimir dekimir commented Mar 27, 2024

Description

Make AdaptivePlanner optional in the FTE scheduler instead of having a separate boolean field indicating whether the planner is to be used.

Reduces potential for inadvertent erroneous use; simplifies method signatures.

Additional context and related issues

Release notes

(x) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
( ) Release notes are required, with the following suggested text:

# Section
* Fix some things. ({issue}`issuenumber`)

@cla-bot cla-bot bot added the cla-signed label Mar 27, 2024
@dekimir dekimir requested a review from losipiuk March 27, 2024 14:56
dekimir added 2 commits March 27, 2024 11:07
... instead of having a separate boolean field indicating whether the planner is to be used.

Reduces potential for inadvertent erroneous use; simplifies method signatures.
@dekimir dekimir force-pushed the optional-AdaptivePlanner-in-FTE branch from 86ff47c to 63066fa Compare March 27, 2024 15:08
@losipiuk losipiuk merged commit f578b74 into trinodb:master Mar 28, 2024
92 of 93 checks passed
@github-actions github-actions bot added this to the 444 milestone Mar 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

2 participants