search

exasol / exasol-virtual-schema

Virtual Schema from Exasol to Exasol
MIT License
1 stars 2 forks source link

Update tests to include Exasol V8/ Update to vsjdbc 12.0.0 (VSEXA) #105

Closed ckunki closed 5 months ago

ckunki commented 1 year ago

Since 2023-10-12 for version 8.23.0 of Exasol database a Docker image is available on Dockerhub

The current ticket therefore requests to update the integration tests of VSEXA to use version 8.23.0 as latest default version.

Please note sibling-tickets for all JDBC-based virtual schemas.

ckunki commented 9 months ago

Waiting for update of VSCJDBC

pj-spoelders commented 7 months ago

support for remote UDF debugging was removed (why?) when reincluding the dependency

        <dependency>
            <groupId>com.exasol</groupId>
            <artifactId>udf-debugging-java</artifactId>
            <version>0.6.11</version>
            <scope>test</scope>
        </dependency>

javadoc then fails with the following errors when trying to build or package the project:

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.6.3:jar (attach-javadocs) on project exasol-virtual-schema: MavenReportException: Error while generating Javadoc: 
[ERROR] Exit code: 1
[ERROR] /home/pj/Downloads/v8testingrepos/exasol-virtual-schema/src/main/java/com/exasol/adapter/dialects/exasol/ExasolLocalQueryRewriter.java:4: error: package java.util.logging is not visible
[ERROR] import java.util.logging.Logger;
[ERROR]                 ^
[ERROR]   (package java.util.logging is declared in module java.logging, but module org.glassfish.jakarta.json does not read it)
[ERROR] /home/pj/Downloads/v8testingrepos/exasol-virtual-schema/src/main/java/com/exasol/adapter/dialects/exasol/ExasolSqlDialect.java:8: error: package java.sql is not visible
[ERROR] import java.sql.SQLException;
[ERROR]            ^
[ERROR]   (package java.sql is declared in module java.sql, but module org.glassfish.jakarta.json does not read it)
[ERROR] /home/pj/Downloads/v8testingrepos/exasol-virtual-schema/src/main/java/com/exasol/adapter/dialects/exasol/ExasolSqlGenerationVisitor.java:5: error: package java.util.logging is not visible
[ERROR] import java.util.logging.Logger;
[ERROR]                 ^
[ERROR]   (package java.util.logging is declared in module java.logging, but module org.glassfish.jakarta.json does not read it)
[ERROR] /home/pj/Downloads/v8testingrepos/exasol-virtual-schema/src/main/java/com/exasol/adapter/dialects/exasol/ExasolMetadataReader.java:3: error: package java.sql is not visible
[ERROR] import java.sql.Connection;
[ERROR]            ^
[ERROR]   (package java.sql is declared in module java.sql, but module org.glassfish.jakarta.json does not read it)
[ERROR] /home/pj/Downloads/v8testingrepos/exasol-virtual-schema/src/main/java/com/exasol/adapter/dialects/exasol/ExasolMetadataReader.java:20: error: cannot find symbol
[ERROR]     public ExasolMetadataReader(final Connection connection, final AdapterProperties properties) {
[ERROR]                                       ^
[ERROR]   symbol:   class Connection
[ERROR]   location: class ExasolMetadataReader
[ERROR] /home/pj/Downloads/v8testingrepos/exasol-virtual-schema/src/main/java/com/exasol/adapter/dialects/exasol/ExasolColumnMetadataReader.java:3: error: package java.sql is not visible
[ERROR] import java.sql.*;
[ERROR]            ^
[ERROR]   (package java.sql is declared in module java.sql, but module org.glassfish.jakarta.json does not read it)
[ERROR] Command line was: /home/pj/.jdks/temurin-11.0.22/bin/javadoc @options @argfile
[ERROR] 
[ERROR] Refer to the generated Javadoc files in '/home/pj/Downloads/v8testingrepos/exasol-virtual-schema/target/apidocs' dir.
ckunki commented 6 months ago

Switch GENERATE_JDBC_DATATYPE_MAPPING_FOR_EXA is only available with connection IMPORT FROM EXA, see https://github.com/exasol/exasol-virtual-schema/releases/tag/7.2.0

pj-spoelders commented 5 months ago

Waiting for response on IS_LOCAL select statement clash with strict datatype checking in case of varchar ascii or char ascii datatypes

UPDATE: we modified the behaviour to cast to UTF8 as well