Good catch. The unwrapping was not intentional on my part. Removing the
unwrapping seems like a benefit (less work for RelBuilder, therefore better
planning performance; SARGs in more places, therefore better optimization; also
the avoidance of cycles as you mention).
There’s a small risk that
Hi,
When simplification is enabled in the RelBuilder, a call to the
RelBuilder.project unwraps SARGs into their flat counterparts [1]. This is
not the case for other nodes, like Filter or Join. This behavior may lead
to an infinite loop when the ProjectReduceExpressionsRule is used with the
HepPla
Hi, Followers.
Thanks for the feedback. Yes, I have a misunderstanding about this.
when I try to simplify "a<>1 and a = 2 [a is nullable]":
checkSimplify3_(
and(ne(vInt(0), literal(1)),
eq(vInt(0), literal(2))),
"=(?0.int0, 2)",
"=(
Hi Francis,
Thanks for the reply. I missed the discussion in
https://lists.apache.org/thread/dqw6hbrpwkc9bsdhbyjv42nvrvbhwbt2. Great
work!
Francis Chuang 于2022年4月2日周六 15:44写道：
> Hey Xiong,
>
> The Github action will automatically build the javadoc and deploy it
> when a release is tagged.
Hey Xiong,
The Github action will automatically build the javadoc and deploy it
when a release is tagged. See:
https://github.com/apache/calcite/blob/master/.github/workflows/publish-website-on-release.yml#L48
Francis
On 2/04/2022 6:30 pm, xiong duan wrote:
Hi Francis,
This is good to
Hi Francis,
This is good to me. And this is very helpful.
But have a little problem, I noticed you removed the The procedure for
deploying changes to the website. If we change the Java doc(The Class or
the method) in https://calcite.apache.org/javadocAggregate/, maybe we still
need this? O
