-
Notifications
You must be signed in to change notification settings - Fork 7k
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
Report progress from server-side to keep client connections alive #4215
Conversation
This way we make sure that 'receive_timeout' on client-side is triggered only when there is a real socket read timeout.
The |
if (options.count(#NAME)) \ | ||
{ \ | ||
context.setSetting(#NAME, options[#NAME].as<std::string>()); \ | ||
config().setString(#NAME, options[#NAME].as<std::string>()); \ |
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.
@abyss7 why do we put settings to config()
here ? Looks excessive.
Maybe you actually wanted a single setting to be in config()
, not everything?
@@ -409,7 +409,7 @@ void TCPHandler::processOrdinaryQuery() | |||
} | |||
else | |||
{ | |||
if (state.progress.rows && after_send_progress.elapsed() / 1000 >= query_context.getSettingsRef().interactive_delay) | |||
if (after_send_progress.elapsed() / 1000 >= query_context.getSettingsRef().interactive_delay) | |||
{ | |||
/// Some time passed and there is a progress. |
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.
Obsolete comment.
I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en
For changelog. Remove if this is non-significant change.
Category (leave one):
This way we make sure that 'receive_timeout' on client-side is triggered only when there is a real socket read timeout.