This website requires JavaScript.
Explore
Help
Sign In
thevar1able
/
ClickHouse
Watch
1
Star
0
Fork
0
You've already forked ClickHouse
mirror of
https://github.com/ClickHouse/ClickHouse.git
synced
2024-11-23 16:12:01 +00:00
Code
Issues
Packages
Projects
Releases
Wiki
Activity
bfa59adbfe
ClickHouse
/
tests
/
queries
/
0_stateless
/
00409_shard_limit_by.reference
28 lines
89 B
Plaintext
Raw
Normal View
History
Unescape
Escape
add tests [#METR-23881]
2016-12-30 12:57:09 +00:00
1
1
3
3
4
4
5
7
7
1 2
3 3
4 2
5 1
7 4
1 John
3 Mary
4 Mary
fix formatting of LIMIT BY; add tests with remote() [#METR-23881]
2017-01-09 13:24:54 +00:00
0
0
0
1
Make the query planner respect LIMIT BY in remote queries
2019-03-15 15:22:22 +00:00
100
100
101
101
102
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-23 16:25:53 +00:00
1
Reference in New Issue
Copy Permalink