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

Move OptimizerConfig to planner package #11312

Merged
merged 1 commit into from
Mar 4, 2022

Conversation

martint
Copy link
Member

@martint martint commented Mar 3, 2022

Description

This class is related to the overall optimizer, not
just to the cost-based optimizations

Is this change a fix, improvement, new feature, refactoring, or other?

Simple mechanical refactoring.

Is this a change to the core query engine, a connector, client library, or the SPI interfaces? (be specific)

Core

How would you describe this change to a non-technical end user or system administrator?

N/A

Related issues, pull requests, and links

Documentation

(x) No documentation is needed.
( ) Sufficient documentation is included in this PR.
( ) Documentation PR is available with #prnumber.
( ) Documentation issue #issuenumber is filed, and can be handled later.

Release notes

(x) No release notes entries required.
( ) Release notes entries required with the following suggested text:

This class is related to the overall optimizer, not
just to the cost-based optimizations
@cla-bot cla-bot bot added the cla-signed label Mar 3, 2022
@martint martint requested review from raunaqmorarka and sopel39 March 3, 2022 17:41
Copy link
Member

@raunaqmorarka raunaqmorarka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for fixing, I missed changing the package after renaming from CboFeaturesConfig to OptimizerConfig.

@martint martint merged commit 108628b into trinodb:master Mar 4, 2022
@github-actions github-actions bot added this to the 373 milestone Mar 4, 2022
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.

3 participants