File: streaming_limit_pipeline_flush.test

package info (click to toggle)
duckdb 1.5.1-2
  • links: PTS, VCS
  • area: main
  • in suites:
  • size: 299,196 kB
  • sloc: cpp: 865,414; ansic: 57,292; python: 18,871; sql: 12,663; lisp: 11,751; yacc: 7,412; lex: 1,682; sh: 747; makefile: 558
file content (30 lines) | stat: -rw-r--r-- 731 bytes parent folder | download | duplicates (4)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
# name: test/sql/limit/streaming_limit_pipeline_flush.test
# description: Test that pipeline correctly flushes operators after STREAMING_LIMIT finishes
# group: [limit]

require tpch

statement ok
LOAD tpch;

statement ok
CALL dbgen(sf=0.01);

# The optimizer pushes down filters which reduces cardinality estimates, causing it to
# place STREAMING_LIMIT on the right side. We disable it to keep it on the left side, to trigger the pipeline flush bug
statement ok
PRAGMA disable_optimizer;

query I
SELECT o.o_orderkey
FROM (
    SELECT l.o_orderkey
    FROM orders l
    LEFT JOIN lineitem li ON li.l_orderkey = l.o_orderkey
    WHERE l.o_orderkey = 1
    LIMIT 1
) AS filtered
JOIN orders o ON TRUE
WHERE o.o_orderkey = 1;
----
1