Unsupported function: array(int32, int32, int32, int32) -> list

[kwannoel]

Describe the bug

Frontend tests for sqlsmith fail. These tests call the respective components entrypoints: parser, binder, planner's, to test the frontend parts of query handling.

Seems to fail at main@ d583594
The commit before: 09a1dcb passes.

@wangrunji0408 could you PTAL? Is this expected after the expr refactor?

The query still works for me e2e.

(Perhaps we should just remove the sqlsmith frontend tests as the e2e tests should cover it)

Error message/log

thread 'main' panicked at src/tests/sqlsmith/tests/frontend/mod.rs:280:52:
called `Result::unwrap()` on an `Err` value: Failed { msg: Some("Error Reason:\nExpr error: Unsupported function: array(int32, int32, int32, int32) -> list") }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

To Reproduce

NEXTEST_PROFILE=ci cargo nextest run --package risingwave_sqlsmith --features "enable_sqlsmith_unit_test"

query:

CREATE TABLE alltypes1 (
    c1 boolean,
    c2 smallint,
    c3 integer,
    c4 bigint,
    c5 real,
    c6 double precision,
    c7 numeric,
    c8 date,
    c9 varchar,
    c10 time without time zone,
    c11 timestamp without time zone,
    -- TODO(Noel): Many timestamptz expressions are unsupported in RW, leave this out for now.
    -- c12 timestamp with time zone,
    c13 interval,
    c14 struct < a integer >,
    c15 integer [],
    c16 varchar []
);


CREATE MATERIALIZED VIEW m4 AS SELECT t_4.c5 AS col_0, (ARRAY[(INT '850'), (INT '0'), (INT '34'), (INT '-2147483648')]) AS col_1, t_4.c15 AS col_2 FROM alltypes1 AS t_4 GROUP BY t_4.c10, t_4.c7, t_4.c13, t_4.c11, t_4.c3, t_4.c9, t_4.c5, t_4.c15 HAVING false ORDER BY t_4.c15 NULLS LAST;

Expected behavior

No response

How did you deploy RisingWave?

No response

The version of RisingWave

No response

Additional context

No response

[kwannoel]

Worked around in #12592 . But still wonder why this can't be handled by frontend anymore. Is it expected?

[wangrunji0408]

This is a bug, as explained in #12660. Sorry for the trouble.