A projection pushdown related bug (SQLancer-TLP) #11409

/*DML*/CREATE TABLE t1(v0 BIGINT, v1 BIGINT, v2 BIGINT, v3 BOOLEAN);
/*DML*/CREATE TABLE t2(v0 DOUBLE);
/*DML*/INSERT INTO t1(v0, v2, v1) VALUES (-1229445667, -342312412, -1507138076);
/*DML*/INSERT INTO t1(v0, v1) VALUES (1541512604, -1229445667);
/*DML*/INSERT INTO t1(v1, v3, v0, v2) VALUES (-1020641465, false, -1493773377, 1751276473);
/*DML*/INSERT INTO t1(v3) VALUES (true), (true), (false);
/*DML*/INSERT INTO t2(v0) VALUES (0.28014577292925047);
SELECT t1.v2, t1.v0 FROM t2 NATURAL JOIN t1 UNION ALL SELECT t1.v2, t1.v0 FROM t2 NATURAL JOIN t1 WHERE (t1.v2 IS NULL);

ProjectionPushdown
caused by
Internal error: Not all InterleaveExec children have a consistent hash partitioning.
This was likely caused by a bug in DataFusion's code and we would welcome that you file an bug report in our issue tracker