ShuMing Li created CALCITE-3153:
---
Summary: Improve testing in TpcdsTest using assertEqual instead of
printing results
Key: CALCITE-3153
URL: https://issues.apache.org/jira/browse/CALCITE-3153
Project: C
Thanks Julian, I’ve fired a JIRA and start working on this.
Best,
Danny Chan
在 2019年6月28日 +0800 AM2:44，Julian Hyde ，写道：
> Unifying in general sounds like a good idea. I haven’t thought through the
> specifics in this case.
>
> Note that each time we generate a parser using JavaCC — which we do in
Danny Chan created CALCITE-3152:
---
Summary: Unify throws in sql parser
Key: CALCITE-3152
URL: https://issues.apache.org/jira/browse/CALCITE-3152
Project: Calcite
Issue Type: Bug
Compon
That was one of the reasons I was unsure where to put the script.
src/main/scripts is fine although it isn't obvious from that location
that it's unrelated to the use of Calcite. I'm not strongly opposed to
just pasting it in the documentation.
--
Michael Mior
mm...@apache.org
Le jeu. 27 juin 2019
Unifying in general sounds like a good idea. I haven’t thought through the
specifics in this case.
Note that each time we generate a parser using JavaCC — which we do in several
places in the code — it generates a new exception class. We don’t want to use
those generated classes. We would like
src/main/scripts would be an OK location.
As this particular script is for a very limited audience - not developers, but
only for release managers - we could consider just putting the text into the
howto. I hate finding lots of scripts in projects when it is not clear what is
the audience or pu
Zhenghua Gao created CALCITE-3151:
-
Summary: RexCall's Monotonicity is not considered in determining a
Calc's collation
Key: CALCITE-3151
URL: https://issues.apache.org/jira/browse/CALCITE-3151
Projec
Mickaël Sauvée created CALCITE-3150:
---
Summary: NPE in UPPER when repeated and combine with LIKE
Key: CALCITE-3150
URL: https://issues.apache.org/jira/browse/CALCITE-3150
Project: Calcite
I
