Hi everyone,
This is a really great discussion. Thanks for starting it Martijn and
your input Jacques! I have been fighting against forking Calcite in
Flink for years already. Even when merging forks of Flink that
transitively forked Calcite, in the end we were able to resolve
conflicts /
On Fri, Apr 24, 2020 at 1:50 AM Timo Walther wrote:
Hi everyone,
so far Apache Flink depends on this feature. We are fine with improving
the SQL compliance and eventually dropping GROUP BY TUMBLE/HOP/SESSION
in the future. However, we would like to give our users some time to
migrate
Hi everyone,
so far Apache Flink depends on this feature. We are fine with improving
the SQL compliance and eventually dropping GROUP BY TUMBLE/HOP/SESSION
in the future. However, we would like to give our users some time to
migrate their existing pipelines.
What does dropping mean for
Congratulations Sergey!
Am 23.07.18 um 13:33 schrieb Sergey Nuyanzin:
Thanks everyone for kind words!
It is a great honor for me to become a Calcite committer.
A little bit about myself
Past few months I have been focusing on Calcite and Flink. I am still
learning Calcite's and Avatica's
Hi Julian,
the Flink community is very thankful for the OpenGIS efforts done by the
Calcite community and I think both project can benefit from it. As
Xingcan mentioned, we are thinking about contributing a GeoOperatorTable
similar to SqlStdOperatorTable. We don't want to reimplement the
Timo Walther created CALCITE-1867:
-
Summary: Allow creating additional SqlGroupFunctions
Key: CALCITE-1867
URL: https://issues.apache.org/jira/browse/CALCITE-1867
Project: Calcite
Issue Type
Hi everyone,
we are very happy to support TUMBLE/HOP/SESSION in our upcoming Flink
1.3 release. However, there are some problems regarding nested window
queries that we would like to discuss with the Calcite community.
Take the following query:
SELECT
rowtime, SUM(x)
FROM (
SELECT
for that we can copy the class to Flink until the
next Calcite release. We did that with other issues in the past, too.
Am 25/04/17 um 20:12 schrieb Timo Walther:
Thanks for your quick response. Flink does not use the monotonicity
property yet and we are are also not using the STREAM keyword. Could
Timo Walther created CALCITE-1761:
-
Summary: TUMBLE/HOP/SESSION_START/END do not resolve time field
correctly
Key: CALCITE-1761
URL: https://issues.apache.org/jira/browse/CALCITE-1761
Project
e Flink. Can you start a
separate email thread when you know that timing?
On Tue, Apr 25, 2017 at 7:13 AM, Timo Walther <twal...@apache.org> wrote:
Hi all,
I'm working on integrating START and END for TUMBLE/HOP/SESSION in Flink SQL
with logical time indicator columns (e.g. rowtime, p
Hi all,
I'm working on integrating START and END for TUMBLE/HOP/SESSION in Flink
SQL with logical time indicator columns (e.g. rowtime, proctime). It
seems there is a bug in the resolution logic of SqlToRelConverter. Since
our feature freeze is next week and this feature should be part of
Hi everyone,
we (from Flink) are currently discussing how we can express
time-semantics (event-time or processing-time) in a SQL query. The
optimal solution would be to have two system attributes that are part of
every table schema/every row data type. We could then access it like
`SELECT *
Timo Walther created CALCITE-1435:
-
Summary: Wrong comparison of TIMESTAMP literals
Key: CALCITE-1435
URL: https://issues.apache.org/jira/browse/CALCITE-1435
Project: Calcite
Issue Type: Bug
13 matches
Mail list logo
