Thank you!
Julian
> On Sep 22, 2018, at 19:49, Kevin Risden wrote:
>
> I found that for Avatica it looks like we can enable deprecation checks
> once we regenerate the protobuf files (which should have happened when
> protobuf was updated to 3.6.1). I filed CALCITE-2587 to look into that. In
>
I'm not sure how to fix this error. The JDK 9 build is failing on node H22
with the following error during checkout:
Resolving deltas: 16% (23/143), completed with 1 local objects.
fatal: pack has 120 unresolved deltas
fatal: index-pack failed
at
I found that for Avatica it looks like we can enable deprecation checks
once we regenerate the protobuf files (which should have happened when
protobuf was updated to 3.6.1). I filed CALCITE-2587 to look into that. In
the meantime, fixed the JCommander deprecation warnings with commit 146d310.
The Apache Jenkins build system has built Calcite-Avatica-Master (build #105)
Status: Still Failing
Check console output at
https://builds.apache.org/job/Calcite-Avatica-Master/105/ to view the results.
The Apache Jenkins build system has built Calcite-Avatica-Master (build #104)
Status: Still Failing
Check console output at
https://builds.apache.org/job/Calcite-Avatica-Master/104/ to view the results.
The Apache Jenkins build system has built Calcite-Avatica-Master (build #103)
Status: Failure
Check console output at
https://builds.apache.org/job/Calcite-Avatica-Master/103/ to view the results.
Yes, my nightly build script looks for deprecation warnings. (It’s only active
on JDK 9 and higher, because the “suppress” annotation doesn’t work on JDK 8,
and we have some uses of deprecated APIs — such as implementing interfaces —
that we cannot remove.)
> On Sep 22, 2018, at 5:22 PM, Kevin
Kevin Risden created CALCITE-2587:
-
Summary: Avatica - Regenerate protobuf for 3.6.1
Key: CALCITE-2587
URL: https://issues.apache.org/jira/browse/CALCITE-2587
Project: Calcite
Issue Type:
I can take a look.
How did you find the warning other than reading the build output?
Not sure if there is a flag we can set during compiling that would fail the
build for issues like these.
Kevin Risden
On Sat, Sep 22, 2018, 19:54 Julian Hyde wrote:
> There is a new deprecation warning in
There is a new deprecation warning in Avatica. We try to keep these to zero.
Kevin, It was probably your CALCITE-2486 change. Can you fix please?
> [INFO] Compiling 2 source files to
> /home/jhyde/regress/calcite-avatica/standalone-server/target/classes
> [WARNING]
>
Hi Enrico,
I think a bit more context would help.
What kind of org.apache.calcite.schema.Table are you using in your Schema?
I suppose you already looked but just in case are there any kind of
statistics on these tables.
I've seen a similar case where the statistics of the table were declaring
Hi,
We found a strange behaviour in an execution plan, basially we have an
EnumerableMergeJoin which has as input two non-sorted
EnumerableTableScan
all the details are in this issue on HerdDB
https://github.com/diennea/herddb/issues/262#issuecomment-423590573
Cut and paste from the issue in
Hello,
I remember that sqlite project (https://www.sqlite.org/index.html) do
have a very serious test process (https://www.sqlite.org/testing.html)
in place.
Quote
"Sqllogictest is a program designed to verify that an SQL database
engine computes correct results by comparing the results to
13 matches
Mail list logo
