Abhishek Agarwal created CALCITE-6333:
-
Summary: Queries with distinct aggregations with filter throw NPE
when planned using joins
Key: CALCITE-6333
URL: https://issues.apache.org/jira/browse/CALCITE-6333
We (Apache Druid) would also like
https://issues.apache.org/jira/browse/CALCITE-5479 and
https://issues.apache.org/jira/browse/CALCITE-5477 to be fixed in 1.35.0.
There are PRs for both of these fixes. We are working on addressing review
comments and just need a few days of time.
On Thu, Jun 1,
Thank you, Alessandro and Stamatis, for the info. Currently, the guava
version being used in druid is 16. So simple exclusion is unlikely to work.
I will still give it a try. If it doesn't, we will shade the jars on our
end.
On Tue, Mar 29, 2022 at 3:38 PM Alessandro Solimando <
Hi,
I am trying to upgrade calcite in the druid codebase. But because of the
guava version mismatch between druid and calcite, a straightforward upgrade
is not possible. We also can't upgrade guava in druid itself since Hadoop-2
still requires old guava jars. As a workaround, I created shaded
You are right, Julian. The druid behavior was not SQL compliant with the
default settings that I was on. The simplification being done by calcite is
valid but the evaluation was wrong.
Hello,
While debugging a druid query that involves an operation such as "A <> A",
I found out that in RexSimplify, such an expression is converted to "null
&& isnull(A)". That seems wrong since it will always evaluate to null even
if A is not null in some row. The right conversion should be
Yes. Thank you. JoinCommuteRule is what I was looking for.
On Wed, Mar 3, 2021 at 3:53 PM Danny Chan wrote:
> Do you mean the join reordering ?
>
> You can take a look at LoptOptimizeJoinRule and JoinCommuteRule.
>
> Abhishek Agarwal 于2021年3月3日周三 下午5:12写道：
>
Hello everyone,
is there an existing rule that can re-write a right outer join as a left
outer join by swapping tables?
