Using the now() function in the materialized view will cause the compute node to crash #21949

XiaoGerGer · 2025-05-22T03:32:26Z

Describe the bug

Using the now() function in the materialized view will cause the compute node to crash

I want to record the processing time of each row of data in the materialized view

Error message/log

To Reproduce

create table test.abc(
    id numeric,
    v numeric,
    primary key(id)
);
insert into test.abc values(1,1);

create materialized view test.abcd as
select
    id,
    sum(v) as v,
    now() as stat_time 
from test.abc
group by id
;

Expected behavior

No response

How did you deploy RisingWave?

No response

The version of RisingWave

2.2.3

Additional context

No response

The text was updated successfully, but these errors were encountered:

pjpringlenom · 2025-05-25T02:13:36Z

believe proctime() should be used

BugenZhao · 2025-05-26T07:52:57Z

Hi. You may use proctime() for this case: https://docs.risingwave.com/sql/functions/datetime#proctime

However, I'm not able to reproduce the crash with v2.2.3. It should gracefully display an error message upon failure.

ERROR:  Failed to run the query

Caused by these errors (recent errors listed first):
  1: Failed to bind expression: now()
  2: Invalid input syntax: For streaming queries, `NOW()` function is only allowed in `WHERE`, `HAVING`, `ON` and `FROM`. Found in clause: None. Please please refer to https://www.risingwave.dev/docs/current/sql-pattern-temporal-filters/ for more information

XiaoGerGer added the type/bug Type: Bug. Only for issues. label May 22, 2025

github-actions bot added this to the release-2.5 milestone May 22, 2025

stdrc self-assigned this May 22, 2025

stdrc added the A-expr Area: Scalar function, operator, expression framework. label May 27, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Using the now() function in the materialized view will cause the compute node to crash #21949

Using the now() function in the materialized view will cause the compute node to crash #21949

Uh oh!

Uh oh!