9 Commits

Author	SHA1	Message	Date
Nikolai Kochetov	e411916bde	Refactor Pipe [part 1].	2020-08-03 14:33:11 +03:00
Azat Khuzhin	177d699cde	Do not check *optimize_skip_unused_shards_nesting w/o *optimize_skip_unused_shards ... This will avoid supperior log message in case of *optimize_skip_unused_shards_nesting already disables it. And also it is logical.	2020-06-29 23:00:14 +03:00
alexey-milovidov	38b018fa04	Update executeQuery.cpp	2020-06-21 21:29:11 +03:00
Azat Khuzhin	fb30629ff2	Add settings to control nesting level for shards skipping optimization ... - optimize_skip_unused_shards_nesting (allows control nesting level for shards skipping optimization) - force_skip_optimize_shards_nesting (allows control nesting level for checking was shards skipped or not) - deprecates force_skip_optimize_shards_no_nested	2020-06-21 15:27:01 +03:00
Azat Khuzhin	d34e6217bc	Add logging of adjusting conditional settings for distributed queries	2020-06-18 21:49:29 +03:00
Azat Khuzhin	6507247328	optimize_skip_unused_shards=2 will disable it for nested distributed queries ... P.S. Looks like settings can be converted between SettingUInt64 and SettingBool without breaking binary protocol. FWIW maybe it is a good idea to change the semantics of the settings as follow (but I guess that changing semantic is not a good idea, better to add new settings and deprecate old ones): - optimize_skip_unused_shards -- accept nesting level on which the optimization will work - force_skip_optimize_shards_nesting -- accept nesting level on which the optimization will work	2020-06-18 21:49:29 +03:00
Alexey Milovidov	0a7edce036	Checkpoint	2020-04-22 09:01:33 +03:00
Alexey Milovidov	2987e70aab	Introduce "max_server_memory_usage" setting	2020-04-20 01:59:21 +03:00
Ivan Lezhankin	06446b4f08	dbms/ → src/	2020-04-03 18:14:31 +03:00