Home Services Partners Company

JDBC Connectors
Release Notes History

This Web page presents the latest features of the Progress DataDirect for JDBC drivers, according to data source in alphabetical order. An asterisk (*) indicates support that was added in a hotfix or software patch subsequent to a release. For release notes archives, click the appropriate data source on the sidebar to the right. For fixes information, refer to the fixes.txt file in the product installation directory.

For ODBC connector release notes, see ODBC Connectors Release Notes History.

Amazon EMR Hive

Progress DataDirect Connect XE for JDBC for Apache Hive Version 5.1.4

CERTIFICATIONS
  • Certified with Apache Hive 1.0, 1.1, and 1.2*
  • Certified with Apache Hive 0.13 and 0.14
  • Certified with the following Amazon EMR distributions:
    • Amazon AMI 3.7*
    • Amazon AMI 3.2-3.3.1
ENHANCEMENTS
  • The BatchMechanism connection property has been added to the driver. By setting BatchMechanism to multiRowInsert, you enable the driver to execute a single insert for all the rows contained in a parameter array. MultiRowInsert is the default setting and provides substantial performance gains when performing batch inserts.*
  • The driver has been enhanced to support SSL for Apache Hive 0.13.0 and higher, incorporating the addition of nine new connection properties.*
  • The driver's Kerberos functionality has been enhanced to support SASL-QOP data integrity and confidentiality. Hence, in addition to supporting the auth value, the driver now supports the auth-int and auth-conf values. SASL-QOP values are defined as follows:
    • auth: authentication only (default)
    • auth-int: authentication with integrity protection
    • auth-conf: authentication with confidentiality protection
    Note that SASL-QOP is configured on the server side as a part of HiveServer2 Kerberos configuration. When Kerberos authentication is enabled through the driver (AuthenticationMethod=kerberos), the driver automatically detects and abides by the server's SASL-QOP configuration at connection time.*
  • Support for row-level inserts has been added to the driver.
  • The driver has been enhanced to support the Char, Decimal, Date, and Varchar data types.
CHANGED BEHAVIOR
  • Added the RegisterStatementPoolMonitorMBean connection property. Note that the
    driver no longer registers the Statement Pool Monitor as a JMX MBean by default.
    You must set RegisterStatementPoolMonitorMBean to true to register the Statement
    Pool Monitor and manage statement pooling with standard JMX API calls.*

Amazon Redshift

Progress DataDirect for JDBC for Amazon Redshift Version 5.1.4

CERTIFICATIONS
  • Certified with Amazon Web Services API Version 2012-12-01
ENHANCEMENTS
  • The BatchMechanism connection property has been added to the driver. By setting BatchMechanism to multiRowInsert, you enable the driver to execute a single insert for all the rows contained in a parameter array. MultiRowInsert is the default setting and provides substantial performance gains when performing batch inserts.
  • The CryptoProtocolVersion connection property has been added to the driver. This property can be used to avoid vulnerabilities associated with SSLv3 and SSLv2, including the POODLE vulnerability.
  • Support for result set holdability has been added to the driver.
CHANGED BEHAVIOR
  • The driver no longer registers the Statement Pool Monitor as a JMX MBean by
    default. To register the Statement Pool Monitor and manage statement pooling with
    standard JMX API calls, the new RegisterStatementPoolMonitorMBean connection
    property must be set to true.*

Apache Cassandra

Progress DataDirect for JDBC for Apache Cassandra Version 6.0.0

CERTIFICATIONS
  • Certified with DataStax Enterprise 5.0*
  • Certified with DataStax Enterprise 4.8
  • Certified with DataStax Enterprise 4.7
  • Certified with Apache Cassandra 3.0 and 3.7*
  • Certified with Apache Cassandra 2.0, 2.1, and 2.2
ENHANCEMENTS
  • The driver has been enhanced to support Cassandra's tunable consistency
    functionality with the ReadConsistency and WriteConsistency connection
    properties.
  • The driver has been enhanced to improve the handling of large result sets and
    reduce the likelihood of out-of-memory errors through the introduction of the
    FetchSize, NativeFetchSize, and ResultMemorySize connection properties.

Apache Hadoop Hive

Progress DataDirect Connect XE for JDBC for Apache Hive Version 5.1.4

CERTIFICATIONS
  • Certified with Apache Hive 1.0, 1.1, and 1.2*
  • Certified with Apache Hive 0.13 and 0.14
ENHANCEMENTS
  • The BatchMechanism connection property has been added to the driver. By setting BatchMechanism to multiRowInsert, you enable the driver to execute a single insert for all the rows contained in a parameter array. MultiRowInsert is the default setting and provides substantial performance gains when performing batch inserts.*
  • The driver has been enhanced to support SSL for Apache Hive 0.13.0 and higher, incorporating the addition of nine new connection properties.*
  • The driver's Kerberos functionality has been enhanced to support SASL-QOP data integrity and confidentiality. Hence, in addition to supporting the auth value, the driver now supports the auth-int and auth-conf values. SASL-QOP values are defined as follows:
    • auth: authentication only (default)
    • auth-int: authentication with integrity protection
    • auth-conf: authentication with confidentiality protection
    Note that SASL-QOP is configured on the server side as a part of HiveServer2 Kerberos configuration. When Kerberos authentication is enabled through the driver (AuthenticationMethod=kerberos), the driver automatically detects and abides by the server's SASL-QOP configuration at connection time.*
  • Support for row-level inserts has been added to the driver.
  • The driver has been enhanced to support the Char, Decimal, Date, and Varchar data types.
CHANGED BEHAVIOR
  • Added the RegisterStatementPoolMonitorMBean connection property. Note that the
    driver no longer registers the Statement Pool Monitor as a JMX MBean by default.
    You must set RegisterStatementPoolMonitorMBean to true to register the Statement
    Pool Monitor and manage statement pooling with standard JMX API calls.*

Apache Spark SQL

Progress DataDirect for JDBC for Apache Spark SQL Version 6.0.1

CERTIFICATIONS
  • Certified with Apache Spark SQL 1.4 and 1.5
ENHANCEMENTS
  • The driver has been enhanced to support the Decimal and Varchar data types.
  • The ArrayFetchSize connection property has been added to the driver to improve performance and reduce out of memory errors. ArrayFetchSize can be used to increase throughput or, alternately, improve response time in Web-based applications.
CHANGED BEHAVIOR
  • The driver no longer registers the Statement Pool Monitor as a JMX MBean by
    default. To register the Statement Pool Monitor and manage statement pooling
    with standard JMX API calls, the new RegisterStatementPoolMonitorMBean
    connection property must be set to true.

Cloudera CDH Hive

Progress DataDirect Connect XE for JDBC for Apache Hive Version 5.1.4

CERTIFICATIONS
  • Certified with Apache Hive 1.0, 1.1, and 1.2*
  • Certified with Apache Hive 0.13 and 0.14
  • Certified with the following Cloudera CDH distributions:
    • Cloudera CDH 5.3, 5.4, 5.5, 5.6, and 5.7*
    • Cloudera CDH 5.0, 5.1, and 5.2
ENHANCEMENTS
  • The BatchMechanism connection property has been added to the driver. By setting BatchMechanism to multiRowInsert, you enable the driver to execute a single insert for all the rows contained in a parameter array. MultiRowInsert is the default setting and provides substantial performance gains when performing batch inserts.*
  • The driver has been enhanced to support SSL for Apache Hive 0.13.0 and higher, incorporating the addition of nine new connection properties.*
  • The driver's Kerberos functionality has been enhanced to support SASL-QOP data integrity and confidentiality. Hence, in addition to supporting the auth value, the driver now supports the auth-int and auth-conf values. SASL-QOP values are defined as follows:
    • auth: authentication only (default)
    • auth-int: authentication with integrity protection
    • auth-conf: authentication with confidentiality protection
    Note that SASL-QOP is configured on the server side as a part of HiveServer2 Kerberos configuration. When Kerberos authentication is enabled through the driver (AuthenticationMethod=kerberos), the driver automatically detects and abides by the server's SASL-QOP configuration at connection time.*
  • Support for row-level inserts has been added to the driver.
  • The driver has been enhanced to support the Char, Decimal, Date, and Varchar data types.
CHANGED BEHAVIOR
  • Added the RegisterStatementPoolMonitorMBean connection property. Note that the
    driver no longer registers the Statement Pool Monitor as a JMX MBean by default.
    You must set RegisterStatementPoolMonitorMBean to true to register the Statement
    Pool Monitor and manage statement pooling with standard JMX API calls.*

Cloudera Impala

Progress DataDirect Connect XE for JDBC for Impala Version 5.1.4

CERTIFICATIONS
  • Certified with Cloudera Impala 2.2 and 2.3*
  • Certified with Cloudera Impala 2.0 and 2.1
ENHANCEMENTS
  • The driver has been enhanced to support the Char and Vachar data type with
    Cloudera Impala 2.1 and higher.
  • Support for result set holdability has been added to the driver.
CHANGED BEHAVIOR
  • The driver no longer registers the Statement Pool Monitor as a JMX MBean by
    default. To register the Statement Pool Monitor and manage statement pooling with
    standard JMX API calls, the new RegisterStatementPoolMonitorMBean connection
    property must be set to true.*

Database.com

Progress DataDirect Connect XE for JDBC for Salesforce Version 5.1.4

CERTIFICATIONS
  • Certified with Salesforce API versions 33 and 34*
ENHANCEMENTS
  • The Salesforce driver has been updated to require a Java SE 7 or higher JVM to comply with revisions to Salesforce security standards. Beginning June 25th, 2016, Salesforce is deprecating support for the TLS 1.0 encryption protocol for inbound and outbound connections. TLS 1.0 is initially being disabled for Sandbox instances before being retired for all instances in early 2017. To maintain compatibility with Salesforce services, the driver must use a JVM that allows TLS 1.0 to be disabled independently of other encryption protocols. This functionality is available with Java SE 7 and higher. Therefore, Java SE 7 or higher must be installed on your system and the JVM must be defined on your system path to use the driver and Salesforce services. Beginning with build 5.1.4.000146, the driver will return an error if you attempt to connect using a Java SE 6 or earlier JVM. For more information on the Salesforce disablement of TLS 1.0, refer to Salesforce disabling TLS 1.0 - Salesforce Knowledge Article Number 000221207.*
  • Support for result set holdability has been added to the driver.
CHANGED BEHAVIOR
  • Added the RegisterStatementPoolMonitorMBean connection property. Note that the
    driver no longer registers the Statement Pool Monitor as a JMX MBean by default.
    You must set RegisterStatementPoolMonitorMBean to true to register the Statement
    Pool Monitor and manage statement pooling with standard JMX API calls.*

DataStax Enterprise

Progress DataDirect for JDBC for Apache Cassandra Version 6.0.0

CERTIFICATIONS
  • Certified with DataStax Enterprise 5.0*
  • Certified with DataStax Enterprise 4.8
  • Certified with DataStax Enterprise 4.7
  • Certified with Apache Cassandra 3.0 and 3.7*
  • Certified with Apache Cassandra 2.0, 2.1, and 2.2
ENHANCEMENTS
  • The driver has been enhanced to support Cassandra's tunable consistency
    functionality with the ReadConsistency and WriteConsistency connection
    properties.
  • The driver has been enhanced to improve the handling of large result sets and
    reduce the likelihood of out-of-memory errors through the introduction of the
    FetchSize, NativeFetchSize, and ResultMemorySize connection properties.

Force.com

Progress DataDirect Connect XE for JDBC for Salesforce Version 5.1.4

CERTIFICATIONS
  • Certified with Salesforce API versions 33 and 34*
ENHANCEMENTS
  • The Salesforce driver has been updated to require a Java SE 7 or higher JVM to comply with revisions to Salesforce security standards. Beginning June 25th, 2016, Salesforce is deprecating support for the TLS 1.0 encryption protocol for inbound and outbound connections. TLS 1.0 is initially being disabled for Sandbox instances before being retired for all instances in early 2017. To maintain compatibility with Salesforce services, the driver must use a JVM that allows TLS 1.0 to be disabled independently of other encryption protocols. This functionality is available with Java SE 7 and higher. Therefore, Java SE 7 or higher must be installed on your system and the JVM must be defined on your system path to use the driver and Salesforce services. Beginning with build 5.1.4.000146, the driver will return an error if you attempt to connect using a Java SE 6 or earlier JVM. For more information on the Salesforce disablement of TLS 1.0, refer to Salesforce disabling TLS 1.0 - Salesforce Knowledge Article Number 000221207.*
  • Support for result set holdability has been added to the driver.
CHANGED BEHAVIOR
  • Added the RegisterStatementPoolMonitorMBean connection property. Note that the
    driver no longer registers the Statement Pool Monitor as a JMX MBean by default.
    You must set RegisterStatementPoolMonitorMBean to true to register the Statement
    Pool Monitor and manage statement pooling with standard JMX API calls.*

Hortonworks Hive

Progress DataDirect Connect XE for JDBC for Apache Hive Version 5.1.4

CERTIFICATIONS
  • Certified with Apache Hive 1.0, 1.1, and 1.2*
  • Certified with Apache Hive 0.13 and 0.14
  • Certified with the following Hortonworks HDP distributions:
    • Hortonworks HDP 2.3 and 2.4*
    • Hortonworks HDP 2.1 and 2.2
ENHANCEMENTS
  • The BatchMechanism connection property has been added to the driver. By setting BatchMechanism to multiRowInsert, you enable the driver to execute a single insert for all the rows contained in a parameter array. MultiRowInsert is the default setting and provides substantial performance gains when performing batch inserts.*
  • The driver has been enhanced to support SSL for Apache Hive 0.13.0 and higher, incorporating the addition of nine new connection properties.*
  • The driver's Kerberos functionality has been enhanced to support SASL-QOP data integrity and confidentiality. Hence, in addition to supporting the auth value, the driver now supports the auth-int and auth-conf values. SASL-QOP values are defined as follows:
    • auth: authentication only (default)
    • auth-int: authentication with integrity protection
    • auth-conf: authentication with confidentiality protection
    Note that SASL-QOP is configured on the server side as a part of HiveServer2 Kerberos configuration. When Kerberos authentication is enabled through the driver (AuthenticationMethod=kerberos), the driver automatically detects and abides by the server's SASL-QOP configuration at connection time.*
  • Support for row-level inserts has been added to the driver.
  • The driver has been enhanced to support the Char, Decimal, Date, and Varchar data types.
CHANGED BEHAVIOR
  • Added the RegisterStatementPoolMonitorMBean connection property. Note that the
    driver no longer registers the Statement Pool Monitor as a JMX MBean by default.
    You must set RegisterStatementPoolMonitorMBean to true to register the Statement
    Pool Monitor and manage statement pooling with standard JMX API calls.*

IBM BigInsights

Progress DataDirect Connect XE for JDBC for Apache Hive Version 5.1.4

CERTIFICATIONS
  • Certified with Apache Hive 1.0, 1.1, and 1.2*
  • Certified with Apache Hive 0.13 and 0.14
  • Certified with the following IBM BigInsights distributions:
    • IBM BigInsights 3.0 and 4.1*
ENHANCEMENTS
  • The BatchMechanism connection property has been added to the driver. By setting BatchMechanism to multiRowInsert, you enable the driver to execute a single insert for all the rows contained in a parameter array. MultiRowInsert is the default setting and provides substantial performance gains when performing batch inserts.*
  • The driver has been enhanced to support SSL for Apache Hive 0.13.0 and higher, incorporating the addition of nine new connection properties.*
  • The driver's Kerberos functionality has been enhanced to support SASL-QOP data integrity and confidentiality. Hence, in addition to supporting the auth value, the driver now supports the auth-int and auth-conf values. SASL-QOP values are defined as follows:
    • auth: authentication only (default)
    • auth-int: authentication with integrity protection
    • auth-conf: authentication with confidentiality protection
    Note that SASL-QOP is configured on the server side as a part of HiveServer2 Kerberos configuration. When Kerberos authentication is enabled through the driver (AuthenticationMethod=kerberos), the driver automatically detects and abides by the server's SASL-QOP configuration at connection time.*
  • Support for row-level inserts has been added to the driver.
  • The driver has been enhanced to support the Char, Decimal, Date, and Varchar data types.
CHANGED BEHAVIOR
  • Added the RegisterStatementPoolMonitorMBean connection property. Note that the
    driver no longer registers the Statement Pool Monitor as a JMX MBean by default.
    You must set RegisterStatementPoolMonitorMBean to true to register the Statement
    Pool Monitor and manage statement pooling with standard JMX API calls.*

IBM DB2

Progress DataDirect Connect for JDBC for DB2 Version 5.1.4

CERTIFICATIONS
  • Certified with DB2 V11.1 for Linux, UNIX, Windows*
  • Certified with DB2 for i 7.2
ENHANCEMENTS
  • Support for cursor type OUT parameters for DB2 for Linux, UNIX, Windows stored procedures has been added to the driver.*
  • The connection properties RandomGenerator and SecureRandomAlgorithm have been
    added to the driver.
    • RandomGenerator allows you to specify the type of random number generator (RNG) the database uses for secure seeding.
    • SecureRandomAlgorithm can be used to specify the SecureRandom number generation algorithm used for secure seeding with implementations of JDK 8 or higher when RandomGenerator is set to secureRandom.
  • The CryptoProtocolVersion connection property has been added to the driver. This property can be used to avoid vulnerabilities associated with SSLv3 and SSLv2, including the POODLE vulnerability.
  • Support for result set holdability has been added to the driver.
CHANGED BEHAVIOR
  • For DB2 for z/OS, the AlternateID connection property has been modified to set the name of the schema in the DB2 CURRENT SCHEMA special register instead of the DB2 CURRENT SQLID special register. AlternateID now sets the name of the schema in the CURRENT SCHEMA special register for DB2 for i, DB2 for Linux/UNIX/Windows, and DB2 for z/OS.*
  • Added the RegisterStatementPoolMonitorMBean connection property. Note that the
    driver no longer registers the Statement Pool Monitor as a JMX MBean by default.
    You must set RegisterStatementPoolMonitorMBean to true to register the Statement
    Pool Monitor and manage statement pooling with standard JMX API calls.*

IBM Informix

Progress DataDirect Connect for JDBC for Informix Version 5.1.4

CERTIFICATIONS
  • Certified with Informix 12.10
ENHANCEMENTS
  • Support for result set holdability has been added to the driver.
CHANGED BEHAVIOR
  • Added the RegisterStatementPoolMonitorMBean connection property. Note that the
    driver no longer registers the Statement Pool Monitor as a JMX MBean by default.
    You must set RegisterStatementPoolMonitorMBean to true to register the Statement
    Pool Monitor and manage statement pooling with standard JMX API calls.*

MapR Hive

Progress DataDirect Connect XE for JDBC for Apache Hive Version 5.1.4

CERTIFICATIONS
  • Certified with Apache Hive 1.0, 1.1, and 1.2*
  • Certified with Apache Hive 0.13 and 0.14
  • Certified with the following MapR distribution:
    • MapR 2.0
ENHANCEMENTS
  • The BatchMechanism connection property has been added to the driver. By setting BatchMechanism to multiRowInsert, you enable the driver to execute a single insert for all the rows contained in a parameter array. MultiRowInsert is the default setting and provides substantial performance gains when performing batch inserts.*
  • The driver has been enhanced to support SSL for Apache Hive 0.13.0 and higher, incorporating the addition of nine new connection properties.*
  • The driver's Kerberos functionality has been enhanced to support SASL-QOP data integrity and confidentiality. Hence, in addition to supporting the auth value, the driver now supports the auth-int and auth-conf values. SASL-QOP values are defined as follows:
    • auth: authentication only (default)
    • auth-int: authentication with integrity protection
    • auth-conf: authentication with confidentiality protection
    Note that SASL-QOP is configured on the server side as a part of HiveServer2 Kerberos configuration. When Kerberos authentication is enabled through the driver (AuthenticationMethod=kerberos), the driver automatically detects and abides by the server's SASL-QOP configuration at connection time.*
  • Support for row-level inserts has been added to the driver.
  • The driver has been enhanced to support the Char, Decimal, Date, and Varchar data types.
CHANGED BEHAVIOR
  • Added the RegisterStatementPoolMonitorMBean connection property. Note that the
    driver no longer registers the Statement Pool Monitor as a JMX MBean by default.
    You must set RegisterStatementPoolMonitorMBean to true to register the Statement
    Pool Monitor and manage statement pooling with standard JMX API calls.*

Microsoft SQL Server

Progress DataDirect Connect for JDBC for SQL Server Version 5.1.4

CERTIFICATIONS
  • Certified with Microsoft SQL Server 2016*
  • Certified with Microsoft SQL Server 2014
  • Certified with Microsoft Windows Azure SQL Database
ENHANCEMENTS
  • Support for NTLMv2 has been added to the driver. You can use the AuthenticationMethod connection property to specify that the driver use NTLMv2 authentication when establishing a connection.
  • The CryptoProtocolVersion connection property has been added to the driver. This property can be used to avoid vulnerabilities associated with SSLv3 and SSLv2, including the POODLE vulnerability.
  • Support for result set holdability has been added to the driver.
CHANGED BEHAVIOR
  • Added the RegisterStatementPoolMonitorMBean connection property. Note that the
    driver no longer registers the Statement Pool Monitor as a JMX MBean by default.
    You must set RegisterStatementPoolMonitorMBean to true to register the Statement
    Pool Monitor and manage statement pooling with standard JMX API calls.*

Microsoft Windows Azure SQL

Progress DataDirect Connect for JDBC for SQL Server Version 5.1.4

CERTIFICATIONS
  • Certified with Microsoft SQL Server 2016*
  • Certified with Microsoft SQL Server 2014
  • Certified with Microsoft Windows Azure SQL Database
ENHANCEMENTS
  • Support for NTLMv2 has been added to the driver. You can use the AuthenticationMethod connection property to specify that the driver use NTLMv2 authentication when establishing a connection.
  • The CryptoProtocolVersion connection property has been added to the driver. This property can be used to avoid vulnerabilities associated with SSLv3 and SSLv2, including the POODLE vulnerability.
  • Support for result set holdability has been added to the driver.
CHANGED BEHAVIOR
  • Added the RegisterStatementPoolMonitorMBean connection property. Note that the
    driver no longer registers the Statement Pool Monitor as a JMX MBean by default.
    You must set RegisterStatementPoolMonitorMBean to true to register the Statement
    Pool Monitor and manage statement pooling with standard JMX API calls.*

MongoDB

Progress DataDirect for JDBC for MongoDB Version 6.0.1

CERTIFICATIONS
  • Certified with MongoDB 3.2*
  • Certified with MongoDB 3.0
ENHANCEMENTS
  • The driver has been enhanced to resolve naming conflicts that can occur when exposing native objects using unquoted, uppercase identifiers (the default behavior). To avoid conflicts, the driver appends an underscore separator and integer (for example, _1) to identifiers that differ only by case.
  • The DefaultVarcharSize configuration option has been enhanced to generate dynamic default lengths for VARCHAR columns when specifying a multiplier value (for example, 2x) for the option. When specifying a multiplier value, the default length for a VARCHAR column is determined by multiplying the value specified by the size of the largest value detected in that column. This results in a default length that is proportionate to the size of the data within the column, which can improve the memory efficiency within the driver and application. The default value for this option has been updated to 1.5x.
  • You can further define the default length for VARCHAR columns by tuning the new MaxVarcharSize and MinVarcharSize configuration options. These options allow you to specify maximum and minimum size limits for the default length generated by the DefaultVarcharSize configuration option. When tuned for your data, MaxVarcharSize and MinVarcharSize can improve memory efficiency and avoid the undesired truncation of VARCHAR values.
  • The KeywordConflictSuffix configuration option allows you to specify the suffix that is appended to object and field names that conflict with SQL engine keywords.
  • The driver has been enhanced to use the MongoDB aggregation framework to improve performance in the execution of SQL queries using LIMIT, ORDER BY, and TOP clauses.
  • The following SQL extensions have been added to the driver:
    • REFRESH MAP adds newly discovered objects to your relational view of native data. It also incorporates any configuration changes made to your relational view by reloading the schema definition and associated files. REFRESH MAP is an expensive query since it involves the discovery of native data.
    • RELOAD MAP reloads the schema definition and associated files. This statement allows you to update your relational view of native data while the driver is connected to the data store. RELOAD MAP does not discover changes made to the native data store.
  • The driver has been enhanced to improve the handling of large result sets and reduce the likelihood of out-of-memory errors through the modification of the FetchSize connection property and the introduction of the ResultMemorySize connection property.
  • The driver has been enhanced to further ensure data integrity when mapping native
    MongoDB data types to a relational schema. When inconsistent data types are
    detected, the driver determines which SQL type to use based on the combination
    of native types found. These combinations are handled in the following manner:
    • Bigint and Integer map to BIGINT
    • Double and Integer map to DOUBLE
    • All other combinations map to VARCHAR or LONGVARCHAR
CHANGED BEHAVIOR
  • The driver no longer registers the Statement Pool Monitor as a JMX MBean by
    default. To register the Statement Pool Monitor and manage statement pooling with
    standard JMX API calls, the new RegisterStatementPoolMonitorMBean connection
    property must be set to true.

MySQL

Progress DataDirect Connect for JDBC for MySQL Version 5.1.4

CERTIFICATIONS
  • Certified with MySQL 5.6
ENHANCEMENTS
  • The CryptoProtocolVersion connection property has been added to the driver. This property can be used to avoid vulnerabilities associated with SSLv3 and SSLv2, including the POODLE vulnerability.
  • Support for result set holdability has been added to the driver.
CHANGED BEHAVIOR
  • Added the RegisterStatementPoolMonitorMBean connection property. Note that the
    driver no longer registers the Statement Pool Monitor as a JMX MBean by default.
    You must set RegisterStatementPoolMonitorMBean to true to register the Statement
    Pool Monitor and manage statement pooling with standard JMX API calls.*

Oracle

Progress DataDirect Connect for JDBC for Oracle Version 5.1.4

CERTIFICATIONS
  • Certified with Oracle 12c
ENHANCEMENTS
  • The LOBPrefetchSize connection property has been added to the driver and is
    supported for Oracle database versions 12.1.0.1 and higher. This connection
    property allows you to specify the size of prefetch data the driver returns for
    BLOBs and CLOBs. With LOB prefetch enabled, the driver can return LOB meta-data
    and the beginning of LOB data along with the LOB locator during a fetch
    operation. This can have significant performance impact, especially for small
    LOBs which can potentially be entirely prefetched, because the data is available
    without having to go through the LOB protocol.*
  • The SDUSize connection property has been added to the driver. This connection property allows you to specify the size in bytes of the Session Data Unit (SDU) that the driver requests when connecting to the server.
  • The SupportBinaryXML connection property has been added to the driver. This connection property enables the driver to support XMLType with binary storage on servers running Oracle 12C and higher.
  • The connection properties RandomGenerator and SecureRandomAlgorithm have been added to the driver.
    • RandomGenerator allows you to specify the type of random number generator (RNG) the database uses for secure seeding.
    • SecureRandomAlgorithm can be used to specify the SecureRandom number generation algorithm used for secure seeding with implementations of JDK 8 or higher when RandomGenerator is set to secureRandom.
  • The CryptoProtocolVersion connection property has been added to the driver. This property can be used to avoid vulnerabilities associated with SSLv3 and SSLv2, including the POODLE vulnerability.
CHANGED BEHAVIOR
  • Added the RegisterStatementPoolMonitorMBean connection property. Note that the
    driver no longer registers the Statement Pool Monitor as a JMX MBean by default.
    You must set RegisterStatementPoolMonitorMBean to true to register the Statement
    Pool Monitor and manage statement pooling with standard JMX API calls.*

Oracle Service Cloud

Progress DataDirect for JDBC for Oracle Service Cloud Version 5.1.4

CERTIFICATIONS
  • Certified with Oracle RightNow CX API 1.2 against Oracle Service Cloud May 2016*
  • Certified with Oracle RightNow CX API 1.2 against Oracle Service Cloud May 2015*
ENHANCEMENTS
  • Support for result set holdability has been added to the driver.
CHANGED BEHAVIOR
  • The driver no longer registers the Statement Pool Monitor as a JMX MBean by
    default. To register the Statement Pool Monitor and manage statement pooling with
    standard JMX API calls, the new RegisterStatementPoolMonitorMBean connection
    property must be set to true.*

Pivotal Greenplum

Progress DataDirect Connect XE for JDBC for Greenplum Version 5.1.4

CERTIFICATIONS
  • Certified with Greenplum 4.3
  • Certified with Pivotal HDB (HAWQ) 2.0*
  • Certified with Pivotal HAWQ 1.2
ENHANCEMENTS
  • The CryptoProtocolVersion connection property has been added to the driver. This property can be used to avoid vulnerabilities associated with SSLv3 and SSLv2, including the POODLE vulnerability.
  • Support for result set holdability has been added to the driver.
CHANGED BEHAVIOR
  • Added the RegisterStatementPoolMonitorMBean connection property. Note that the
    driver no longer registers the Statement Pool Monitor as a JMX MBean by default.
    You must set RegisterStatementPoolMonitorMBean to true to register the Statement
    Pool Monitor and manage statement pooling with standard JMX API calls.*

Pivotal HD Hive

Progress DataDirect Connect XE for JDBC for Apache Hive Version 5.1.4

CERTIFICATIONS
  • Certified with Apache Hive 1.0, 1.1, and 1.2*
  • Certified with Apache Hive 0.13 and 0.14
  • Certified with the following Pivotal PHD distribution:
    • Pivotal PHD 2.1*
ENHANCEMENTS
  • The BatchMechanism connection property has been added to the driver. By setting BatchMechanism to multiRowInsert, you enable the driver to execute a single insert for all the rows contained in a parameter array. MultiRowInsert is the default setting and provides substantial performance gains when performing batch inserts.*
  • The driver has been enhanced to support SSL for Apache Hive 0.13.0 and higher, incorporating the addition of nine new connection properties.*
  • The driver's Kerberos functionality has been enhanced to support SASL-QOP data integrity and confidentiality. Hence, in addition to supporting the auth value, the driver now supports the auth-int and auth-conf values. SASL-QOP values are defined as follows:
    • auth: authentication only (default)
    • auth-int: authentication with integrity protection
    • auth-conf: authentication with confidentiality protection
    Note that SASL-QOP is configured on the server side as a part of HiveServer2 Kerberos configuration. When Kerberos authentication is enabled through the driver (AuthenticationMethod=kerberos), the driver automatically detects and abides by the server's SASL-QOP configuration at connection time.*
  • Support for row-level inserts has been added to the driver.
  • The driver has been enhanced to support the Char, Decimal, Date, and Varchar data types.
CHANGED BEHAVIOR
  • Added the RegisterStatementPoolMonitorMBean connection property. Note that the
    driver no longer registers the Statement Pool Monitor as a JMX MBean by default.
    You must set RegisterStatementPoolMonitorMBean to true to register the Statement
    Pool Monitor and manage statement pooling with standard JMX API calls.*

Pivotal HDB (HAWQ)

Progress DataDirect Connect XE for JDBC for Greenplum Version 5.1.4

CERTIFICATIONS
  • Certified with Greenplum 4.3
  • Certified with Pivotal HDB (HAWQ) 2.0*
  • Certified with Pivotal HAWQ 1.2
ENHANCEMENTS
  • The CryptoProtocolVersion connection property has been added to the driver. This property can be used to avoid vulnerabilities associated with SSLv3 and SSLv2, including the POODLE vulnerability.
  • Support for result set holdability has been added to the driver.
CHANGED BEHAVIOR
  • Added the RegisterStatementPoolMonitorMBean connection property. Note that the
    driver no longer registers the Statement Pool Monitor as a JMX MBean by default.
    You must set RegisterStatementPoolMonitorMBean to true to register the Statement
    Pool Monitor and manage statement pooling with standard JMX API calls.*

PostgreSQL

Progress DataDirect Connect for JDBC for PostgreSQL Version 5.1.4

CERTIFICATIONS
  • Certified with PostgreSQL 9.5 and 9.6*
  • Certified with PostgreSQL 9.3 and 9.4
ENHANCEMENTS
  • The ExtendedColumnMetadata connection property has been added to the driver.
    This property determines how the driver returns column metadata when retrieving
    results with ResultSetMetaData methods.*
  • The CryptoProtocolVersion connection property has been added to the driver. This property can be used to avoid vulnerabilities associated with SSLv3 and SSLv2, including the POODLE vulnerability.
  • Support for result set holdability has been added to the driver.
CHANGED BEHAVIOR
  • Added the RegisterStatementPoolMonitorMBean connection property. Note that the
    driver no longer registers the Statement Pool Monitor as a JMX MBean by default.
    You must set RegisterStatementPoolMonitorMBean to true to register the Statement
    Pool Monitor and manage statement pooling with standard JMX API calls.*

Progress OpenEdge

Progress DataDirect Connect for JDBC for Progress OpenEdge Version 5.1.4

CERTIFICATIONS
  • Certified with with Progress OpenEdge 11.6*
  • Certified with with Progress OpenEdge 11.4 and 11.5
ENHANCEMENTS
  • The CryptoProtocolVersion connection property has been added to the driver. This property can be used to avoid vulnerabilities associated with SSLv3 and SSLv2, including the POODLE vulnerability.
  • Support for result set holdability has been added to the driver.
CHANGED BEHAVIOR
  • Added the RegisterStatementPoolMonitorMBean connection property. Note that the
    driver no longer registers the Statement Pool Monitor as a JMX MBean by default.
    You must set RegisterStatementPoolMonitorMBean to true to register the Statement
    Pool Monitor and manage statement pooling with standard JMX API calls.*

Salesforce

Progress DataDirect Connect XE for JDBC for Salesforce Version 5.1.4

CERTIFICATIONS
  • Certified with Salesforce API versions 33 and 34*
ENHANCEMENTS
  • The Salesforce driver has been updated to require a Java SE 7 or higher JVM to comply with revisions to Salesforce security standards. Beginning June 25th, 2016, Salesforce is deprecating support for the TLS 1.0 encryption protocol for inbound and outbound connections. TLS 1.0 is initially being disabled for Sandbox instances before being retired for all instances in early 2017. To maintain compatibility with Salesforce services, the driver must use a JVM that allows TLS 1.0 to be disabled independently of other encryption protocols. This functionality is available with Java SE 7 and higher. Therefore, Java SE 7 or higher must be installed on your system and the JVM must be defined on your system path to use the driver and Salesforce services. Beginning with build 5.1.4.000146, the driver will return an error if you attempt to connect using a Java SE 6 or earlier JVM. For more information on the Salesforce disablement of TLS 1.0, refer to Salesforce disabling TLS 1.0 - Salesforce Knowledge Article Number 000221207.*
  • Support for result set holdability has been added to the driver.
CHANGED BEHAVIOR
  • Added the RegisterStatementPoolMonitorMBean connection property. Note that the
    driver no longer registers the Statement Pool Monitor as a JMX MBean by default.
    You must set RegisterStatementPoolMonitorMBean to true to register the Statement
    Pool Monitor and manage statement pooling with standard JMX API calls.*

SAP Sybase Adaptive Server Enterprise

Progress DataDirect Connect for JDBC for Sybase Version 5.1.4

CERTIFICATIONS
  • Certified with SAP Sybase Adaptive Server Enterprise 16.0
ENHANCEMENTS
  • The CryptoProtocolVersion connection property has been added to the driver. This property can be used to avoid vulnerabilities associated with SSLv3 and SSLv2, including the POODLE vulnerability.
  • Support for result set holdability has been added to the driver.
CHANGED BEHAVIOR
  • Added the RegisterStatementPoolMonitorMBean connection property. Note that the
    driver no longer registers the Statement Pool Monitor as a JMX MBean by default.
    You must set RegisterStatementPoolMonitorMBean to true to register the Statement
    Pool Monitor and manage statement pooling with standard JMX API calls.*
patch-whats-new

Read Next

What's new