-
Notifications
You must be signed in to change notification settings - Fork 524
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
Conversation
pkg/scheduler/queue/queue.go
Outdated
availableQuerierConnections: make(chan *querierConnection), | ||
querierOperations: make(chan querierOperation), | ||
enqueueRequests: make(chan enqueueRequest), | ||
getNextRequestForQuerierCalls: make(chan *getNextRequestForQuerierCall), |
There was a problem hiding this comment.
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
There was a problem hiding this 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.
# Conflicts: # pkg/scheduler/queue/queue.go
There was a problem hiding this 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.
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
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]