Jiatao Tao created CALCITE-4413:
---
Summary: Duplicate RAND() after optimizer
Key: CALCITE-4413
URL: https://issues.apache.org/jira/browse/CALCITE-4413
Project: Calcite
Issue Type: Bug
Alex Ramos created CALCITE-4412:
---
Summary: SqlParser MySQL mode fails to parse "INT(11)" type
Key: CALCITE-4412
URL: https://issues.apache.org/jira/browse/CALCITE-4412
Project: Calcite
Issue Ty
Jiatao Tao created CALCITE-4411:
---
Summary: Rel to SQL lost distinct when doing window
Key: CALCITE-4411
URL: https://issues.apache.org/jira/browse/CALCITE-4411
Project: Calcite
Issue Type: Bug
Will Yu created CALCITE-4410:
Summary: Expose the type of internal sql node in Planner
Key: CALCITE-4410
URL: https://issues.apache.org/jira/browse/CALCITE-4410
Project: Calcite
Issue Type: Impro
Liya Fan>is it possible to break the PR into a number of small ones?
I can split the commit in two for review-only purposes: a commit that
refactors the code, and the second commit that adds @Nullable annotations.
Here you go: https://github.com/apache/calcite/pull/2273 (see
[CALCITE-4199] Refacto
I think this is a great idea. +1 for the online meetup.
If there are slots left I can also talk about how Hive leverages Calcite to
do query optimization.
-Vineet
On Fri, Nov 6, 2020 at 7:21 AM Stamatis Zampetakis
wrote:
> Let's try to fix the date/time and tentative agenda so that we can add
Ruben Q L created CALCITE-4409:
--
Summary: Improve exception when RelBuilder tries to create a field
on a non-struct expression
Key: CALCITE-4409
URL: https://issues.apache.org/jira/browse/CALCITE-4409
Pr
Liya Fan>I believe annotations for
Liya Fan>nullability are beneficial for code readability and reasoning.
Thanks for the feedback.
Liya Fan>Intuitively, the "@Nullable" annotation does not provide much
information,
Liya Fan>and it does not make the code more readable (IMO).
I'm puzzled. First y