#119: Fix joining HASHTYPE columns

.gitattributes

@@ -8,6 +8,7 @@ pk_generated_parent.pom                                          linguist-genera
 .github/workflows/release_droid_prepare_original_checksum.yml    linguist-generated=true
 .github/workflows/release_droid_print_quick_checksum.yml         linguist-generated=true
 .github/workflows/release_droid_release_on_maven_central.yml     linguist-generated=true
+.github/workflows/release_droid_upload_github_release_assets.yml linguist-generated=true
 .settings/org.eclipse.jdt.core.prefs                             linguist-generated=true
 .settings/org.eclipse.jdt.ui.prefs                               linguist-generated=true
 

.vscode/settings.json

@@ -1,9 +1,9 @@
 {
   "editor.formatOnSave": true,
   "editor.codeActionsOnSave": {
-    "source.organizeImports": true,
-    "source.generate.finalModifiers": true,
-    "source.fixAll": true
+    "source.organizeImports": "explicit",
+    "source.generate.finalModifiers": "explicit",
+    "source.fixAll": "explicit"
   },
   "java.codeGeneration.useBlocks": true,
   "java.saveActions.organizeImports": true,

doc/changes/changes_7.1.7.md

@@ -0,0 +1,27 @@
+# Exasol Virtual Schema 7.1.7, released 2024-02-09
+
+Code name: Fix data types for `IMPORT FROM EXA`
+
+## Summary
+
+This release fixes the data types reported for virtual schemas using `IMPORT FROM EXA`. The Exasol specific types `GEOMETRY`, `INTERVAL YEAR TO MONTH`, `INTERVAL DAY TO SECOND` and `HASHTYPE` were mapped to `VARCHAR` before. The virtual schema now returns these types correctly.
+
+This also fixes a bug when joining a table in a virtual schema with a normal table using a `HASHTYPE` column. This failed before in Exasol 7.1 with error message `Feature not supported: Incomparable Types: VARCHAR(32) UTF8 and HASHTYPE(16 BYTE)!`. In Exasol 8 the error message was `Adapter generated invalid pushdown query for virtual table VIRTUAL: Data type mismatch in column number 1 (1-indexed).Expected HASHTYPE(16 BYTE), but got VARCHAR(32) UTF8.`.
+
+## Bugfixes
+
+* #119: Fixed data types for `IMPORT FROM EXA`
+
+## Dependency Updates
+
+### Test Dependency Updates
+
+* Updated `com.exasol:test-db-builder-java:3.5.2` to `3.5.3`
+
+### Plugin Dependency Updates
+
+* Updated `com.exasol:project-keeper-maven-plugin:2.9.16` to `3.0.1`
+* Updated `org.apache.maven.plugins:maven-failsafe-plugin:3.2.2` to `3.2.3`
+* Updated `org.apache.maven.plugins:maven-surefire-plugin:3.2.2` to `3.2.3`
+* Added `org.apache.maven.plugins:maven-toolchains-plugin:3.1.0`
+* Updated `org.codehaus.mojo:versions-maven-plugin:2.16.1` to `2.16.2`

doc/dialects/exasol.md

@@ -17,7 +17,7 @@ The SQL statement below creates the adapter script, defines the Java class that
 ```sql
 CREATE JAVA ADAPTER SCRIPT SCHEMA_FOR_VS_SCRIPT.ADAPTER_SCRIPT_EXASOL AS
     %scriptclass com.exasol.adapter.RequestDispatcher;
-    %jar /buckets/<BFS service>/<bucket>/virtual-schema-dist-11.0.2-exasol-7.1.6.jar;
+    %jar /buckets/<BFS service>/<bucket>/virtual-schema-dist-11.0.2-exasol-7.1.7.jar;
 /
 ```