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

Rename variables and types in query-scheduler RequestQueue #6141

Merged
merged 6 commits into from
Oct 3, 2023

Conversation

charleskorn
Copy link
Contributor

What this PR does

This PR clarifies the names of some variables and types used in the query-scheduler's RequestQueue.

Which issue(s) this PR fixes or relates to

(none)

Checklist

  • [n/a] Tests updated
  • [n/a] Documentation added
  • [n/a] CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX]

@charleskorn charleskorn marked this pull request as ready for review September 27, 2023 05:50
@charleskorn charleskorn requested a review from a team as a code owner September 27, 2023 05:50
availableQuerierConnections: make(chan *querierConnection),
querierOperations: make(chan querierOperation),
enqueueRequests: make(chan enqueueRequest),
getNextRequestForQuerierCalls: make(chan *getNextRequestForQuerierCall),
Copy link
Member

Choose a reason for hiding this comment

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

similar naming here once we settle on the type naming

Copy link
Member

@francoposa francoposa left a comment

Choose a reason for hiding this comment

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

I'm fine to roll with this after the merge conflict is fixed.

If I were to bikeshed over one last name I'd change this setup

nextRequestForQuerierCalls chan *waitingNextRequestForQuerierCall

to just

nextRequestForQuerierCalls chan *nextRequestForQuerierCall, as the type itself doesn't necessarily indicate waiting (it could be being processed already or done), the fact that they're in a channel implies well enough that they're waiting to me.

Copy link
Member

@pstibrany pstibrany left a comment

Choose a reason for hiding this comment

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

🙈 I'm not going to start another round of naming comments 😄, approving to unblock you.

@charleskorn charleskorn merged commit 79be68d into main Oct 3, 2023
28 checks passed
@charleskorn charleskorn deleted the charleskorn/clarify-query-scheduler-names branch October 3, 2023 00:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants