-
Notifications
You must be signed in to change notification settings - Fork 838
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
Refactor QueryRegistry #18424
Refactor QueryRegistry #18424
Conversation
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.
will be nice if it simplify or get rid of usage QueryRegister in DatabaseFeature
@@ -819,8 +813,6 @@ RestStatus RestAqlHandler::handleFinishQuery(std::string const& idString) { | |||
TRI_ERROR_HTTP_NOT_FOUND); | |||
return {}; | |||
} | |||
|
|||
_queryRegistry->destroyQuery(_vocbase.name(), qid, errorCode); |
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 guess this extra call to destroyQuery(...)
was superfluous before, and it was intentionally removed.
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.
finishQuery
now implicitly destroys the query, that's why this call is no longer needed.
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.
LGTM
Scope & Purpose
... and cleanup killed/finished queries as soon as the last engine is closed.
Checklist