We should consider it, but I wouldn’t place too high a priority on it.
Adding a new CI configuration has a cost to us: each time there is a breakage,
one of our developers has to spend time and effort debugging and fixing it.
Also, I don’t want to reward AWS’ behavior of creating forks of open s
Amazon Corretto is Amazon's distribution of OpenJDK:
https://aws.amazon.com/blogs/opensource/amazon-corretto-no-cost-distribution-openjdk-long-term-support/
It will be generally available in Q1 2019 with support for Ubuntu and
RedHat. It will also be the default Java distribution on Amazon Linu
You’re proposing lazy consensus. We don’t do that for commits. (Yeah, we use a
mixture of CTR and RTC. But adding lazy consensus muddies things too much, I
think.)
For this change, I think you should do RTC, and require a +1 from at least one
committer. Therefore, someone please review
https:/
Thanks, all, for your input.
Following this discussion, I have prepared a PR
https://github.com/apache/calcite/pull/919
Let me know if you agree with the approach. If there are no objections /
comments, I will commit it in a couple of days.
Propagation of Statement.setFetchSize(int) into actual
Jesus Camacho Rodriguez created CALCITE-2673:
Summary: SqlDialect supports pushing of all functions by default
Key: CALCITE-2673
URL: https://issues.apache.org/jira/browse/CALCITE-2673
Proj
Julian Hyde created CALCITE-2672:
Summary: In JOIN ... USING and NATURAL JOIN, common columns should
be unambiguous
Key: CALCITE-2672
URL: https://issues.apache.org/jira/browse/CALCITE-2672
Project: C
Sandeep Chada created CALCITE-2671:
--
Summary: Use IN SET OQL predicate to improve query performance for
Geode
Key: CALCITE-2671
URL: https://issues.apache.org/jira/browse/CALCITE-2671
Project: Calcit
Hongze Zhang created CALCITE-2670:
-
Summary: Combine similar JSON aggregate functions in operator table
Key: CALCITE-2670
URL: https://issues.apache.org/jira/browse/CALCITE-2670
Project: Calcite
