We implemented support for `SET SCHEMA` by subclassing `ServerDdlExecutor`, and
calling (in our case) `AvaticaConnection.setSchema(schema)` does indeed work.
However, we've also encountered some JDBC-based applications that will set the
explicitly set an incorrect default schema via the
ou can log a JIRA along
with the test case, so people can do the root cause analysis.
Thanks,
Haisheng Yuan
On 2022/03/12 01:26:53 "Gramana, Zachary (GE Digital)" wrote:
> Hello all!
>
> I would appreciate some help/guidance with troubleshooting a big
Hello all!
I would appreciate some help/guidance with troubleshooting a big performance
regression we saw on our UNION queries after updating our application from 1.24
to 1.29. Many of the tables in the queries are wide (> 50 columns) so we use a
custom push-down Project class. These custom
OpenJDK 13?
Note that the runtime is able to find the required classes, it just doesn’t
like what it finds.
> On Sep 30, 2020, at 11:58 AM, Gramana, Zachary (GE Digital)
wrote:
>
> Hi Everyone,
>
> Try as I might, I am unable to open a model-base
Hi Everyone,
Try as I might, I am unable to open a model-based connection with sqlline
(built via `./gradlew buildSqllineClasspath`). I have tried a number of
different release tags (calcite-1.23.0, calcite-1.24.0, and calcite-1.25.0) and
even manually bumped sqline to 1.8.0 and 1.7.0--all
I ran into the same problem. Like some others, I had to modify the sqlline
script's line 48 from:
exec java -Xmx1g $VM_OPTS $JAVA_OPTS -jar build/libs/sqllineClasspath.jar
"$@"
to:
exec java -Xmx1g $VM_OPTS $JAVA_OPTS -cp "$PWD/build/libs/*" sqlline.SqlLine
"$@"
After that, it worked
