Hi all,
During vote of 1.23.0 rc1, there are some discussions about the solution of
CALCITE-3997.
Some may think it is a matter of best practice, but in many cases it is a
matter of right or wrong.
Here is the rationale.
The original query in CALCITE-3997 is
SELECT t1.k1, t2.k1 FROM t1, t2
Hello,
Since I was among the people who raised some concerns about this during the
vote I would like to mention that it was mostly about the fact it came very
late in the release cycle.
It is better to avoid breaking changes in the RC phase since it may be
difficult for people to react or test it.
Hello Haisheng,
thanks for bringing up this discussion. I was also part of the people who
expressed concerns about CALCITE-3997 due to a backwards compatibility
issue in a very specific scenario in a downstream project. This issue was
satisfactory handled with a temporary workaround for the RC, an
