I noticed that DuckDB implemented such an optimization recently. Can you please log a jira case to remove redundant ORDER BY keys from OVER? Yes, it would be either a planner rule or a rewrite by RelBuilder.
Julian > On Feb 21, 2024, at 11:43 PM, key lou <louke...@gmail.com> wrote: > > HI ALL : > I have the following sql: > select name, row_number() over(partition by id, age order by id, age) rn > from t; In fact, it can be optimized into > select name ,row_number() over(partition by id,age) rn from t; > Remove order by because order by and partition by are repeated. Since they > are grouped according to the partition by field, the sorting is > meaningless. Is there such a solution in calcite? Optimize rules? > thanks.
