According to the issue, it blocks CALCITE-2817 [1], however CALCITE-2817
was in Calcite 1.19.0, which was released before Avatica 1.14.0.
I am happy to revert CALCITE-2845 as I am pretty keen to get the ball
rolling for Avatica 1.15.0, but can someone please confirm that it's
safe to revert CALCITE-2845? We don't want to end up in a situation
where Avatica 1.15.0 is broken and ends up blocking Avatica-Go and
Calcite again.
[1] https://issues.apache.org/jira/browse/CALCITE-2817
On 8/05/2019 11:56 pm, Stamatis Zampetakis wrote:
Since nobody is actively working on CALCITE-3040 and we would like to
release 1.15.0 relatively soon, the only viable solution is to revert
CALCITE-2845, hoping that people who downloaded 1.14.0 are not making
changes to their code based on that.
On Wed, May 8, 2019 at 12:29 AM Francis Chuang <francischu...@apache.org>
wrote:
Could someone please have a look at CALCITE-3040 [1]?
CALCITE-3040 is a blocker for 1.15.0 and I can make rc0 available for
voting once it's fixed.
Francis
[1] https://issues.apache.org/jira/browse/CALCITE-3040
On 1/05/2019 10:47 am, Francis Chuang wrote:
After Avatica 1.14.0 was released, it was reported that the fix for
CALCITE-2845 [1] broke some existing clients. This is currently being
tracked in CALCITE-3040 [2].
We need to release Avatica 1.15.0 to fix this issue, so that Calcite can
upgrade its version of Avatica.
While this is a tiny release, it's also possible to include other fixes,
if required. Other than CALCITE-3040, are there any other issues you
guys would like to see fixed?
Francis
[1] https://issues.apache.org/jira/browse/CALCITE-2845
[2] https://issues.apache.org/jira/browse/CALCITE-3040
