Yes, Rising Wave does not have built-in orchestration and scheduling capabilities like a cron job. However, you can achieve data deletion based on TTL using temporal filters and external scripts. Here is how you can define a table with TTL using temporal filters:

1. Create a source first:

create source X;

2. Create a materialized view (the table you want) with TTL:

create materialized view real_X_table as
select * from X where X.timestamp > now() - interval '1 month';

By using temporal filters and defining materialized views with TTL, you can effectively manage data deletion based on time-to-live in Rising Wave.