Stamatis Zampetakis created CALCITE-6916:
Summary: Add Lint check for sub-query terms in commit messages
Key: CALCITE-6916
URL: https://issues.apache.org/jira/browse/CALCITE-6916
Project: Calci
Stamatis Zampetakis created CALCITE-6917:
Summary: Remove mention to "a list of values" from Javadoc of
IN/NOT_IN operator
Key: CALCITE-6917
URL: https://issues.apache.org/jira/browse/CALCITE-6917
Caican Cai created CALCITE-6918:
---
Summary: Nokogiri updates packaged libxslt to v1.1.43
Key: CALCITE-6918
URL: https://issues.apache.org/jira/browse/CALCITE-6918
Project: Calcite
Issue Type: Bu
Stamatis Zampetakis created CALCITE-6915:
Summary: Generalize terminology Linter to allow pattern based
checks in commit messages
Key: CALCITE-6915
URL: https://issues.apache.org/jira/browse/CALCITE-6915
Hi Juri,
it's true that the tables in the joins are fully connected via the
predicates, but order matters and the concrete order I see can't do without
cartesian products: it's joining "company_type" with other tables before
joining with "movie_companies", but the only predicate in the where clause
Silun Dong created CALCITE-6914:
---
Summary: Expand join-dependent predicates from disjuction
Key: CALCITE-6914
URL: https://issues.apache.org/jira/browse/CALCITE-6914
Project: Calcite
Issue Type
Hi,
As mentioned by Mads in a previous mail, we are working on a SQL-API in Apache
Wayang.
We are trying to set up experiments with the JOB Benchmark and see that we have
to rewrite queries to explicit INNER JOINS for them to be parsed correctly.
Since we are planning to do other benchmarks with
