You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For example, the JAR filename of the [Oracle Virtual Schema 2.0.0 release](https://github.com/exasol/oracle-virtual-schema/releases/tag/2.0.0), which is based on the [9.0.1 version of Virtual Schema JDBC](https://github.com/exasol/virtual-schema-common-jdbc/releases/tag/9.0.1), is:
24
+
For example, the JAR filename of the [Oracle Virtual Schema 2.3.0 release](https://github.com/exasol/oracle-virtual-schema/releases/tag/2.3.0), which is based on the [10.0.1 version of Virtual Schema JDBC](https://github.com/exasol/virtual-schema-common-jdbc/releases/tag/10.0.1), is:
25
25
26
-
virtual-schema-dist-9.0.1-oracle-2.0.0.jar
26
+
virtual-schema-dist-10.0.1-oracle-2.3.0.jar
27
27
28
28
The version of the Virtual Schema JDBC on which a Virtual Schema is based also tells you whether it is supported or discontinued, as shown in the following table:
29
29
30
30
Virtual Schema JDBC Version | Required Java Version | Lifecycle
Note that you can update Exasol 6.0.x and 6.1.x with script language containers version 2019-11-26 or newer in order to get Java 11 support. We recommend updating the Exasol installation to at least 6.2.3 or newer for best results.
52
+
We recommend updating the Exasol installation to at least 7.1.10 or newer for best results.
51
53
52
54
Please do not try to install language containers with lower Java versions on newer Exasol installations. This is untested.
0 commit comments