This section describes the JDBC driver provided by Exasol to connect third party application to Exasol. If using Version 2.0.14 or later , you'll use com.mysql.jdbc.Driver as your driver class ( prior releases. 0.14 - bin.jar in my case ) is on your classpath. To use the driver, the JAR archive named postgresql.jar if you built from source, otherwise it will likely be (named with the following convention: postgresql-server version.build number.jdbcJDBC version.jar, for example postgresql-8.0-310.jdbc3.jar) needs to be included in the class path, either by putting it in the CLASSPATH environment variable, or by. Setting up the Class Path.
![]() Set Classpath For Jdbc Driver Provided By![]() Red Hat / CentOS 6, OpenJDK JVM 1.8.0 (x86/x64) Red Hat / CentOS 7, OpenJDK JVM 1.8.0 (x64) There is an automatic installation wizard for it. openSUSE Leap 42.2, OpenJDK JVM 1.8.0 (x64) SUSE Linux Enterprise Server 11 Service Pack 3, IBM's JVM 1.7.0 (x86/x64) SUSE Linux Enterprise Desktop 12, OpenJDK JVM 1.7.0 (x64) SUSE Linux Enterprise Server 12, IBM's JVM 1.7.0 (x64) Ubuntu 14.04 LTS, OpenJDK JVM 1.7.0 (x86/64) Cs5 dmgIn the Download JDBC Driver section, select the required file based on your OS, for examples: macOS Mojave (10.14), JVM 1.8.0 (64Bit) macOS Sierra (10.12), JVM 1.8.0 (64Bit) ElementThis prefix is necessary for the driver manager.Defines the servers and the port of the Exasol cluster (for example, 192.168.6.11.14:8563). Add the following repository and dependency to the build configuration of your project (for example, pom.xml for Maven)The JDBC Driver uses the following URL structure for Exasol: jdbc:exa:/.The following table explains the elements of the URL structure. The main class of the driver is com.exasol.jdbc.EXADriver Integrating JDBC Driver using MavenThe JDBC driver is also available in the Exasol Maven repository ( ). Depending on the application this archive must be added to the search path for the Java classes ( CLASSPATH).All classes of the JDBC driver belong to the Java com.exasol.jdbc package. Jar archive in the installation directory.The driver is included in the delivered. myhost1,myhost2/72975B4D331DEEB44FA41FB858A5417E163151BBFB45376574706800A8DCCE30:8563: Two servers with fingerprint /72975B4D331DEEB44FA41FB858A5417E163151BBFB45376574706800A8DCCE30 and port 8563. Or single host myhost with multiple IP addresses mapped to it, fingerprint /72975B4D331DEEB44FA41FB858A5417E163151BBFB45376574706800A8DCCE30, and port 8563. myhost/72975B4D331DEEB44FA41FB858A5417E163151BBFB45376574706800A8DCCE30:8563: Single server with name myhost and port 8563. You can also specify an IP range with a comma-separated list. If the connection fails, the driver will continue to try all other possible addresses. ![]() User-defined data types and the types Blob, Clob, Array, and Ref.If the rowcount of a query exceeds 2147483647 (2 31-1), the JDBC driver will return the value 2147483647. Support of the DatabaseMetaData and ResultSetMetaData metadata APIs.The following features are not supported: Support of more than one open ResultSet Direct execution of SQL statements as a prepared statement and in batch mode. The JVM can run out of memory if the value is too high.The same can be achieved by using the function setFetchSize().Switches on the driver's log function. If nothing is specified, the host name of the connections string will be used as defaultAmount of data in kB which should be obtained by Exasol during a fetch. If nothing is specified, the name "exasol" will be used as default.Host name of the Kerberos service. If the schema cannot be opened, the login fails with a java.sql.SQLException.Principal name of the Kerberos service. PropertyName of the schema that should be opened after login. Supported Driver PropertiesYou can transfer the following properties to the JDBC driver through the URL. Only the SYS user can set the parameter. This timeout is used to limit the login time especially in case of a large cluster with multiple reserve nodes.Defines the time (in seconds) for a statement to run before it is automatically aborted.Enables the user to execute queries even if the limit for active sessions (executing a query) has been reached. That is why you should always set the log directory in debug mode.Tells the server what the application is called.Tells the server the version of the application.Maximum time (in seconds) the driver waits for the database for a connect or disconnect request.Maximum time (in milliseconds) the driver waits to establish a TPC connection to a server. It can assist the Exasol Support in the diagnosis of problems.Due to performance reasons the logging should not be used in a productive systemDefines the directory where the JDBC debug log files should be written to (in debug mode).Example: jdbc:exa:192.168.6.11.14:8563 debug=1 logdir=/tmp/my folder/ schema=sysDefault is the application's current directory, which is not always transparent.
0 Comments
Leave a Reply. |
Details
AuthorAndrew ArchivesCategories |