5 Commits

Author	SHA1	Message	Date
Constantin S. Pan	cbc0f56af1	Mark all input columns in LIMIT BY as required output ... The query analyzer only marks the actual arguments of LIMIT BY as required output for the LimitBy step in the pipeline. This is fine, unless the query is distributed, in which case the first stage might remove a column that is used at the second stage (e.g. for ORDER BY) but is not part of the final select. Prevent removal of any columns in LimitBy by marking all input columns as required output.	2019-05-24 09:53:09 +01:00
proller	f1cc83ca9e	Tests: Allow use any test database (remove test. hardcode where it possible) (#5008)	2019-04-16 17:13:13 +03:00
Constantin S. Pan	df6860d5e0	Make the query planner respect LIMIT BY in remote queries	2019-03-15 15:26:21 +00:00
Nikolai Kochetov	21935dc53e	removed remote(127.0.0.1) from tests	2018-01-29 14:40:28 +03:00
proller	3219d20df8	Group all tests with 127.0.0.{1,2} into 'shard' tag	2017-01-25 17:00:08 +03:00