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

Fix config property name to match semantics #23585

Conversation

losipiuk
Copy link
Member

@losipiuk losipiuk commented Sep 26, 2024

Description

Additional context and related issues

Release notes

( ) 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.
(x) Release notes are required, with the following suggested text:

# General
* Rename config property `max-tasks-waiting-for-execution-per-stage` to `max-tasks-waiting-for-execution-per-query` 
  and session property `max_tasks_waiting_for_node_per_stage` to `max_tasks_waiting_for_node_per_query` to actually match implemented semantics. ({issue}`issuenumber`)

@cla-bot cla-bot bot added the cla-signed label Sep 26, 2024
@github-actions github-actions bot added the docs label Sep 26, 2024
@losipiuk losipiuk requested review from wweiss-starburst and removed request for walterddr September 26, 2024 16:14
}

@Config("max-tasks-waiting-for-node-per-stage")
@ConfigDescription("Maximum possible number of tasks waiting for node allocation per stage before scheduling of new tasks for stage is paused")
public QueryManagerConfig setMaxTasksWaitingForNodePerStage(int maxTasksWaitingForNodePerStage)
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we need to add @LegacyConfig for existing user? or User will have to change the configuration?

Copy link
Member Author

Choose a reason for hiding this comment

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

I could add that - not sure if should given property name is just plain wrong - but maybe the way to go still.

Copy link
Contributor

@krvikash krvikash left a comment

Choose a reason for hiding this comment

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

In the release note, there is typo i guess.

It should be max-tasks-waiting-for-node-per-stage and max-tasks-waiting-for-node-per-query

@losipiuk losipiuk force-pushed the lukaszos/fix-config-property-name-to-match-semantics-615c79 branch from 3dc0069 to faf694b Compare October 3, 2024 12:06
@losipiuk losipiuk merged commit b5d46e3 into trinodb:master Oct 4, 2024
96 checks passed
@github-actions github-actions bot added this to the 461 milestone Oct 4, 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.

3 participants