Vineet Garg created CALCITE-3952:
Summary: Improve SortRemoveRule to remove Sort based on rowcount
Key: CALCITE-3952
URL: https://issues.apache.org/jira/browse/CALCITE-3952
Project: Calcite
Made a mistake on the example above, and update it as follows:
// Table function windowing syntax.
SELECT
product_id, count(*), window_start
FROM TABLE(TUMBLE(order, DESCRIPTOR(rowtime), INTERVAL '1' hour))
GROUP BY product_id, window_start
On Wed, Apr 22, 2020 at 2:31 PM Rui Wang
Hi community,
I want to kick off a discussion about deprecating grouped window functions
(GROUP BY TUMBLE/HOP/SESSION) as the table function windowing support
becomes a thing [1] (FROM TABLE(TUMBLE/HOP/SESSION)). The current stage of
table function windowing is TUMBLE support is checked in. HOP
I assume that by GitHub page you mean [1].
For quite some time linq4j is part of calcite [2] so I think that [1] is
not maintained anymore.
The backlog in [1] also looks a bit obsolete.
Julian can correct me if I am wrong.
In my previous email, I was talking about relational expressions (i.e.,
Ruben Q L created CALCITE-3951:
--
Summary: Support different comparison based on collation
Key: CALCITE-3951
URL: https://issues.apache.org/jira/browse/CALCITE-3951
Project: Calcite
Issue Type:
Filed a JIRA: https://issues.apache.org/jira/browse/CALCITE-3950
XING JIN 于2020年4月22日周三 下午2:51写道:
> Hi Vineet ~
> +1 on your analysis.
> Checking below case in agg.iq. We can see that the behavior of GROUPING
> function in Calcite is the same as Hive.
>
> # GROUPING in SELECT clause of CUBE
Yeah Stamatis, I know that as I can see the github page for linq4j that
lots of task is in Backlog and Link-To-SQL Provider is one of them
But the intention of the project is to make java objects as Queryable talk
to DB.
Expressions and various Statement used in linq4j is to generate the
> Is there any recommended approach to make that happen smoothly besides
coding and testing work? We need to be aware that the new planner might be
co-exist with VolcanoPlanner for 5 or more years, or even never replace
VolcanoPlanner.
If that is true, i might say the new planner is probably with
Hi Vineet ~
+1 on your analysis.
Checking below case in agg.iq. We can see that the behavior of GROUPING
function in Calcite is the same as Hive.
# GROUPING in SELECT clause of CUBE query
select deptno, job, count(*) as c, grouping(deptno) as d,
grouping(job) j, grouping(deptno, job) as x
from