Hi Danny
Thanks for your reply, can you explain "Calcite only optimize based on the
field input refs, if we always keep the alias, there are many cases that
can not be promoted" a bit? In my mind, alias just field names, doesn't
affect the input refs?
Regards!
Aron Tao
Danny Chan 于2020年10月22日周
Hi community,
Where to find the current JavaCC used in Calcite? What I can tell is
Calcite core is using a JavaCC plugin [1], but after that I have lost the
track to locate the version number?
[1]:
https://github.com/apache/calcite/blob/b5a761e559ca1c1c914e388df4c6a0958dc17fc8/core/build.gradle
This seems reasonable to merge window metadata as a column (more compact
format).
Maybe Julian can comment whether there was special consideration to define
window_start and window_end as two separate columns?
-Rui
On Wed, Oct 21, 2020 at 8:20 PM Danny Chan wrote:
> Some of our fellows sugges
During planning, Calcite only optimize based on the field input refs, if we
always keep the alias, there are many cases that can not be promoted. I
collected some cases that already tracked by the JIRA issue:
[1] https://issues.apache.org/jira/browse/CALCITE-4037
[2] https://issues.apache.org/ji
Some of our fellows suggest the window table value functions to append a
structure type field:
window: ROW(start: timestamp(3), end: timestamp(3))
For example if
table T has schema: (ts: timestamp(3), b: varchar(20)), then
Tumble(TABLE T, DESCRIPTOR(T.ts), INTERVAL '5' MINUTE)
has return type
Julian Hyde created CALCITE-4349:
Summary: Support GROUP_CONCAT aggregate function for MySQL
Key: CALCITE-4349
URL: https://issues.apache.org/jira/browse/CALCITE-4349
Project: Calcite
Issue T
