Merge pull request #2569 from EnterpriseDB/release/2022-04-20

Release: 2022-04-20
EnterpriseDB · Apr 20, 2022 · 01ff6fa · 01ff6fa
2 parents fa6e604 + f4d23f7
commit 01ff6fa
Show file tree

Hide file tree

Showing 68 changed files with 40 additions and 32 deletions.
diff --git a/...s/docs/jdbc_connector/42.3.3.1/01_jdbc_rel_notes/08_jdbc_42.3.3.1_rel_notes.mdx b/...s/docs/jdbc_connector/42.3.3.1/01_jdbc_rel_notes/08_jdbc_42.3.3.1_rel_notes.mdx
@@ -0,0 +1,17 @@
+---
+title: "Version 42.3.3.1"
+
+---
+
+The EDB JDBC connector provides connectivity between a Java application and an EDB Postgres Advanced Server database.
+
+New features, enhancements, bug fixes, and other changes in the EDB JDBC Connector `42.3.3.1` include:
+
+| Type           | Description                                                                                                                                                                                                                                                                                                                |
+| -------------- | ------------------------------------------------------------------------------- |
+| Upstream Merge | Merged with the upstream community driver version `42.3.3`. See the community [JDBC documentation](https://jdbc.postgresql.org/documentation/changelog.html#version_42.3.3) for details.                                                                                                                        |
+| Security Fix   |  [GHSA-673j-qm5f-xpv8](https://github.com/advisories/GHSA-673j-qm5f-xpv8): Removed the loggerFile and loggerLevel configuration properties as part of this fix. While the properties still exist, they can no longer be used to configure the driver logging. Instead use java.util.logging configuration mechanisms such as `logging.properties`. |
+| Change         | As part of security fix GHSA-673j-qm5f-xpv, the ability to enable logging using the connection properties is no longer available as of version 42.3.3. |                                                                                                                                                                                                                                                                    |
+
+
+
diff --git a/..._rel_notes/09_jdbc_42.3.2.1_rel_notes.mdx → ..._rel_notes/09_jdbc_42.3.2.1_rel_notes.mdx b/..._rel_notes/09_jdbc_42.3.2.1_rel_notes.mdx → ..._rel_notes/09_jdbc_42.3.2.1_rel_notes.mdx
diff --git a/...rel_notes/10_jdbc_42.2.24.1_rel_notes.mdx → ...rel_notes/10_jdbc_42.2.24.1_rel_notes.mdx b/...rel_notes/10_jdbc_42.2.24.1_rel_notes.mdx → ...rel_notes/10_jdbc_42.2.24.1_rel_notes.mdx
diff --git a/...rel_notes/12_jdbc_42.2.19.1_rel_notes.mdx → ...rel_notes/12_jdbc_42.2.19.1_rel_notes.mdx b/...rel_notes/12_jdbc_42.2.19.1_rel_notes.mdx → ...rel_notes/12_jdbc_42.2.19.1_rel_notes.mdx
diff --git a/...rel_notes/14_jdbc_42.2.12.3_rel_notes.mdx → ...rel_notes/14_jdbc_42.2.12.3_rel_notes.mdx b/...rel_notes/14_jdbc_42.2.12.3_rel_notes.mdx → ...rel_notes/14_jdbc_42.2.12.3_rel_notes.mdx
diff --git a/..._rel_notes/16_jdbc_42.2.9.1_rel_notes.mdx → ..._rel_notes/16_jdbc_42.2.9.1_rel_notes.mdx b/..._rel_notes/16_jdbc_42.2.9.1_rel_notes.mdx → ..._rel_notes/16_jdbc_42.2.9.1_rel_notes.mdx
diff --git a/..._rel_notes/18_jdbc_42.2.8.1_rel_notes.mdx → ..._rel_notes/18_jdbc_42.2.8.1_rel_notes.mdx b/..._rel_notes/18_jdbc_42.2.8.1_rel_notes.mdx → ..._rel_notes/18_jdbc_42.2.8.1_rel_notes.mdx
diff --git a/...ctor/42.3.2.1/01_jdbc_rel_notes/index.mdx → ...ctor/42.3.3.1/01_jdbc_rel_notes/index.mdx b/...ctor/42.3.2.1/01_jdbc_rel_notes/index.mdx → ...ctor/42.3.3.1/01_jdbc_rel_notes/index.mdx
@@ -8,6 +8,7 @@ These release notes describe what's new in each release. When a minor or patch r
 
 | Version                                  | Release Date | 
 | ---------------------------------------- | ------------ | 
+| [42.3.3.1](08_jdbc_42.3.3.1_rel_notes)   | 2022 Apr 20  |
 | [42.3.2.1](09_jdbc_42.3.2.1_rel_notes)   | 2022 Feb 15  |
 | [42.2.24.1](10_jdbc_42.2.24.1_rel_notes) | 2021 Nov 5   |
 | [42.2.19.1](12_jdbc_42.2.19.1_rel_notes) | 2021 Apr 15  |

diff --git a/...tor/42.3.2.1/02_requirements_overview.mdx → ...tor/42.3.3.1/02_requirements_overview.mdx b/...tor/42.3.2.1/02_requirements_overview.mdx → ...tor/42.3.3.1/02_requirements_overview.mdx
diff --git a/...vanced_server_jdbc_connector_overview.mdx → ...vanced_server_jdbc_connector_overview.mdx b/...vanced_server_jdbc_connector_overview.mdx → ...vanced_server_jdbc_connector_overview.mdx
diff --git a/...th_an_rpm_package/01_jdbc42_rhel8_x86.mdx → ...th_an_rpm_package/01_jdbc42_rhel8_x86.mdx b/...th_an_rpm_package/01_jdbc42_rhel8_x86.mdx → ...th_an_rpm_package/01_jdbc42_rhel8_x86.mdx
diff --git a/...pm_package/02_jdbc42_other_linux8_x86.mdx → ...pm_package/02_jdbc42_other_linux8_x86.mdx b/...pm_package/02_jdbc42_other_linux8_x86.mdx → ...pm_package/02_jdbc42_other_linux8_x86.mdx
diff --git a/...th_an_rpm_package/03_jdbc42_rhel7_x86.mdx → ...th_an_rpm_package/03_jdbc42_rhel7_x86.mdx b/...th_an_rpm_package/03_jdbc42_rhel7_x86.mdx → ...th_an_rpm_package/03_jdbc42_rhel7_x86.mdx
diff --git a/..._an_rpm_package/04_jdbc42_centos7_x86.mdx → ..._an_rpm_package/04_jdbc42_centos7_x86.mdx b/..._an_rpm_package/04_jdbc42_centos7_x86.mdx → ..._an_rpm_package/04_jdbc42_centos7_x86.mdx
diff --git a/...h_an_rpm_package/05_jdbc42_sles15_x86.mdx → ...h_an_rpm_package/05_jdbc42_sles15_x86.mdx b/...h_an_rpm_package/05_jdbc42_sles15_x86.mdx → ...h_an_rpm_package/05_jdbc42_sles15_x86.mdx
diff --git a/...h_an_rpm_package/06_jdbc42_sles12_x86.mdx → ...h_an_rpm_package/06_jdbc42_sles12_x86.mdx b/...h_an_rpm_package/06_jdbc42_sles12_x86.mdx → ...h_an_rpm_package/06_jdbc42_sles12_x86.mdx
diff --git a/..._package/07_jdbc42_ubuntu20_deb10_x86.mdx → ..._package/07_jdbc42_ubuntu20_deb10_x86.mdx b/..._package/07_jdbc42_ubuntu20_deb10_x86.mdx → ..._package/07_jdbc42_ubuntu20_deb10_x86.mdx
diff --git a/...m_package/08_jdbc42_ubuntu18_deb9_x86.mdx → ...m_package/08_jdbc42_ubuntu18_deb9_x86.mdx b/...m_package/08_jdbc42_ubuntu18_deb9_x86.mdx → ...m_package/08_jdbc42_ubuntu18_deb9_x86.mdx
diff --git a/..._an_rpm_package/09_jdbc42_rhel8_ppcle.mdx → ..._an_rpm_package/09_jdbc42_rhel8_ppcle.mdx b/..._an_rpm_package/09_jdbc42_rhel8_ppcle.mdx → ..._an_rpm_package/09_jdbc42_rhel8_ppcle.mdx
diff --git a/...an_rpm_package/11_jdbc42_sles15_ppcle.mdx → ...an_rpm_package/11_jdbc42_sles15_ppcle.mdx b/...an_rpm_package/11_jdbc42_sles15_ppcle.mdx → ...an_rpm_package/11_jdbc42_sles15_ppcle.mdx
diff --git a/...an_rpm_package/12_jdbc42_sles12_ppcle.mdx → ...an_rpm_package/12_jdbc42_sles12_ppcle.mdx b/...an_rpm_package/12_jdbc42_sles12_ppcle.mdx → ...an_rpm_package/12_jdbc42_sles12_ppcle.mdx
diff --git a/..._rpm_package/13_upgrading_rpm_install.mdx → ..._rpm_package/13_upgrading_rpm_install.mdx b/..._rpm_package/13_upgrading_rpm_install.mdx → ..._rpm_package/13_upgrading_rpm_install.mdx
diff --git a/...e_connector_with_an_rpm_package/index.mdx → ...e_connector_with_an_rpm_package/index.mdx b/...e_connector_with_an_rpm_package/index.mdx → ...e_connector_with_an_rpm_package/index.mdx
diff --git a/...al_installer_to_install_the_connector.mdx → ...al_installer_to_install_the_connector.mdx b/...al_installer_to_install_the_connector.mdx → ...al_installer_to_install_the_connector.mdx
diff --git a/...ng_the_advanced_server_jdbc_connector.mdx → ...ng_the_advanced_server_jdbc_connector.mdx b/...ng_the_advanced_server_jdbc_connector.mdx → ...ng_the_advanced_server_jdbc_connector.mdx
diff --git a/..._configuring_the_jdbc_connector/index.mdx → ..._configuring_the_jdbc_connector/index.mdx b/..._configuring_the_jdbc_connector/index.mdx → ..._configuring_the_jdbc_connector/index.mdx
diff --git a/...ng_the_advanced_server_jdbc_connector.mdx → ...ng_the_advanced_server_jdbc_connector.mdx b/...ng_the_advanced_server_jdbc_connector.mdx → ...ng_the_advanced_server_jdbc_connector.mdx
diff --git a/...e/01_additional_connection_properties.mdx → ...e/01_additional_connection_properties.mdx b/...e/01_additional_connection_properties.mdx → ...e/01_additional_connection_properties.mdx
@@ -39,8 +39,6 @@ Some of the additional connection properties are shown in the following table.
 | user                  | String  | The database user on whose behalf the connection is being made.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
 | password              | String  | The database user’s password.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
 | ssl                   | Boolean | Requests an authenticated, encrypted SSL connection.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
-| loggerLevel           | String  | The logger level of the driver. The allowed values are `OFF`, `DEBUG`, or `TRACE`. This enables the `java.util.logging.Logger` level of the driver based on the following mapping of levels: `DEBUG` -> `FINE`, `TRACE` -> `FINEST`. The `loggerLevel` property is intended for debugging the driver and not for general SQL query debugging.                                                                                                                                                                                                                                                      |
-| loggerFile            | String  | The file name output of the logger. This parameter must be used together with `loggerLevel`. If set, the logger uses a `java.util.logging.FileHandler` to write to a specified file. If the parameter isn't set or the file can’t be created, the `java.util.logging.ConsoleHandler` is used instead of `java.util.logging.FileHandler`.                                                                                                                                                                                                                                                |
 | charSet               | String  | The value of `charSet` determines the character set used for data sent to or received from the database.                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
 | prepareThreshold      | Integer | The value of `prepareThreshold` determines the number of `PreparedStatement` executions required before switching to server-side prepared statements. The default is five.                                                                                                                                                                                                                                                                                                                                                                                                           |
 | loadBalanceHosts      | Boolean | In default mode (disabled) hosts are connected in the given order. If enabled, hosts are chosen randomly from the set of suitable candidates.                                                                                                                                                                                                                                                                                                                                                                                                                                    |

diff --git a/...ynchronous_secondary_database_servers.mdx → ...ynchronous_secondary_database_servers.mdx b/...ynchronous_secondary_database_servers.mdx → ...ynchronous_secondary_database_servers.mdx
diff --git a/...s/02_connecting_to_the_database/index.mdx → ...s/02_connecting_to_the_database/index.mdx b/...s/02_connecting_to_the_database/index.mdx → ...s/02_connecting_to_the_database/index.mdx
diff --git a/..._statements_through_statement_objects.mdx → ..._statements_through_statement_objects.mdx b/..._statements_through_statement_objects.mdx → ..._statements_through_statement_objects.mdx
@@ -51,27 +51,30 @@ Use the `registerOutParameter` method to identify each `OUT` or `INOUT` paramete
 The following examples show using the `CallableStatement` method to provide parameters to a procedure with the following signature:
 
 ```text
-PROCEDURE hire_emp (ename VARCHAR2
-empno NUMBER
-job VARCHAR2
-sal NUMBER
+CREATE OR REPLACE PROCEDURE hire_emp (ename VARCHAR2
+empno NUMBER,
+job VARCHAR2,
+sal NUMBER,
 hiredate DATE DEFAULT now(),
 mgr NUMBER DEFAULT 7100,
 deptno NUMBER
 )
+IS
+	BEGIN
+	    INSERT INTO emp VALUES (empno, ename, job, mgr, hiredate, sal, deptno);
+	END;
 ```
 
 The following example uses ordinal notation to provide parameters:
 
 ```text
-CallableStatement cstmt = con.prepareCall
-("{CALL hire_emp(?,?,?,?,?,?,?)}");
+CallableStatement cstmt = con.prepareCall("{CALL hire_emp(?,?,?,?,?,?,?)}");
 //Bind a value to each parameter.
 cstmt.setString(1, "SMITH");
 cstmt.setInt(2, 8888);
 cstmt.setString(3, "Sales");
 cstmt.setInt(4, 5500);
-cstmt.setDate(5, "2016-06-01");
+cstmt.setDate(5, Date.valueOf("2016-06-01"));
 cstmt.setInt(6, 7566);
 cstmt.setInt(7, 30);
 ```

diff --git a/...eving_results_from_a_resultset_object.mdx → ...eving_results_from_a_resultset_object.mdx b/...eving_results_from_a_resultset_object.mdx → ...eving_results_from_a_resultset_object.mdx
diff --git a/...ava_applications/05_freeing_resources.mdx → ...ava_applications/05_freeing_resources.mdx b/...ava_applications/05_freeing_resources.mdx → ...ava_applications/05_freeing_resources.mdx
diff --git a/..._java_applications/06_handling_errors.mdx → ..._java_applications/06_handling_errors.mdx b/..._java_applications/06_handling_errors.mdx → ..._java_applications/06_handling_errors.mdx
diff --git a/...onnector_with_java_applications/index.mdx → ...onnector_with_java_applications/index.mdx b/...onnector_with_java_applications/index.mdx → ...onnector_with_java_applications/index.mdx
diff --git a/.../42.3.2.1/05a_using_advanced_queueing.mdx → .../42.3.3.1/05a_using_advanced_queueing.mdx b/.../42.3.2.1/05a_using_advanced_queueing.mdx → .../42.3.3.1/05a_using_advanced_queueing.mdx
diff --git a/...ing_sql_commands_with_executeUpdate().mdx → ...ing_sql_commands_with_executeUpdate().mdx b/...ing_sql_commands_with_executeUpdate().mdx → ...ing_sql_commands_with_executeUpdate().mdx
diff --git a/...graphical_interface_to_a_java_program.mdx → ...graphical_interface_to_a_java_program.mdx b/...graphical_interface_to_a_java_program.mdx → ...graphical_interface_to_a_java_program.mdx
diff --git a/...ing_client-side_resource_requirements.mdx → ...ing_client-side_resource_requirements.mdx b/...ing_client-side_resource_requirements.mdx → ...ing_client-side_resource_requirements.mdx
diff --git a/...eparedstatements_to_send_sql_commands.mdx → ...eparedstatements_to_send_sql_commands.mdx b/...eparedstatements_to_send_sql_commands.mdx → ...eparedstatements_to_send_sql_commands.mdx
diff --git a/...nality/03_executing_stored_procedures.mdx → ...nality/03_executing_stored_procedures.mdx b/...nality/03_executing_stored_procedures.mdx → ...nality/03_executing_stored_procedures.mdx
diff --git a/...nality/04_using_ref_cursors_with_java.mdx → ...nality/04_using_ref_cursors_with_java.mdx b/...nality/04_using_ref_cursors_with_java.mdx → ...nality/04_using_ref_cursors_with_java.mdx
@@ -35,8 +35,8 @@ The stored procedure shown in the following (`getEmpNames`) builds two `REF CURS
 ```text
 CREATE OR REPLACE PROCEDURE getEmpNames
 (
-  commissioned IN OUT SYS_REFCURSOR,
-  salaried IN OUT SYS_REFCURSOR
+  commissioned OUT SYS_REFCURSOR,
+  salaried OUT SYS_REFCURSOR
 )
 IS
 BEGIN
@@ -82,7 +82,7 @@ public void RefCursorSample(Connection con)
 }
 ```
 
-A `CallableStatement` prepares each `REF CURSOR` (`commissioned` and `salaried`). Each cursor is returned as an `IN OUT` parameter of the stored procedure, `getEmpNames()`:
+A `CallableStatement` prepares each `REF CURSOR` (`commissioned` and `salaried`). Each cursor is returned as an `OUT` parameter of the stored procedure, `getEmpNames()`:
 
 ```text
 String commandText = "{call getEmpNames(?,?)}";

diff --git a/...onality/05_using_bytea_data_with_java.mdx → ...onality/05_using_bytea_data_with_java.mdx b/...onality/05_using_bytea_data_with_java.mdx → ...onality/05_using_bytea_data_with_java.mdx
diff --git a/...bject_types_and_collections_with_java.mdx → ...bject_types_and_collections_with_java.mdx b/...bject_types_and_collections_with_java.mdx → ...bject_types_and_collections_with_java.mdx
diff --git a/...fication_handling_with_noticelistener.mdx → ...fication_handling_with_noticelistener.mdx b/...fication_handling_with_noticelistener.mdx → ...fication_handling_with_noticelistener.mdx
diff --git a/...ed_jdbc_connector_functionality/index.mdx → ...ed_jdbc_connector_functionality/index.mdx b/...ed_jdbc_connector_functionality/index.mdx → ...ed_jdbc_connector_functionality/index.mdx
diff --git a/...1_using_ssl/01_configuring_the_server.mdx → ...1_using_ssl/01_configuring_the_server.mdx b/...1_using_ssl/01_configuring_the_server.mdx → ...1_using_ssl/01_configuring_the_server.mdx
diff --git a/...1_using_ssl/02_configuring_the_client.mdx → ...1_using_ssl/02_configuring_the_client.mdx b/...1_using_ssl/02_configuring_the_client.mdx → ...1_using_ssl/02_configuring_the_client.mdx
diff --git a/...sl/03_testing_the_ssl_jdbc_connection.mdx → ...sl/03_testing_the_ssl_jdbc_connection.mdx b/...sl/03_testing_the_ssl_jdbc_connection.mdx → ...sl/03_testing_the_ssl_jdbc_connection.mdx
diff --git a/...ate_authentication_without_a_password.mdx → ...ate_authentication_without_a_password.mdx b/...ate_authentication_without_a_password.mdx → ...ate_authentication_without_a_password.mdx
diff --git a/...ity_and_encryption/01_using_ssl/index.mdx → ...ity_and_encryption/01_using_ssl/index.mdx b/...ity_and_encryption/01_using_ssl/index.mdx → ...ity_and_encryption/01_using_ssl/index.mdx
diff --git a/...and_encryption/02_scram_compatibility.mdx → ...and_encryption/02_scram_compatibility.mdx b/...and_encryption/02_scram_compatibility.mdx → ...and_encryption/02_scram_compatibility.mdx
diff --git a/...pport_for_gssapi_encrypted_connection.mdx → ...pport_for_gssapi_encrypted_connection.mdx b/...pport_for_gssapi_encrypted_connection.mdx → ...pport_for_gssapi_encrypted_connection.mdx
diff --git a/....2.1/09_security_and_encryption/index.mdx → ....3.1/09_security_and_encryption/index.mdx b/....2.1/09_security_and_encryption/index.mdx → ....3.1/09_security_and_encryption/index.mdx
diff --git a/...dvanced_server_jdbc_connector_logging.mdx → ...dvanced_server_jdbc_connector_logging.mdx b/...dvanced_server_jdbc_connector_logging.mdx → ...dvanced_server_jdbc_connector_logging.mdx
@@ -14,29 +14,13 @@ The EDB Postgres Advanced Server JDBC Connector supports the use of logging to h
 !!! Note
     Previous versions of the EDB Postgres Advanced Server JDBC Connector used a custom mechanism to enable logging. It's now replaced by the use of `java.util.logging` in versions moving forward from community version 42.1.4.1. The older mechanism is no longer available.
 
-## Enabling logging with connection properties (static)
+    Previous versions of the Advanced Server JDBC Connector can enable logging using the connection properties, however it is no longer available from 42.3.3 onwards.
 
-You can directly configure logging within the connection properties of the JDBC Connector. The connection properties related to logging are `loggerLevel` and `loggerFile`.
 
-`loggerLevel`
+## Enabling logging with logging.properties
 
-Logger level of the driver. Allowed values are `OFF`, `DEBUG`, or `TRACE`. This option enables the `java.util.logging.Logger` level of the driver to correspond to the following EDB Postgres Advanced Server JDBC levels:
+The default Java logging framework stores its configuration in a file called `logging.properties`. You can use logging properties to configure the driver dynamically (for example, when using the JDBC Connector with an application server such as Tomcat, JBoss, WildFly, etc.), which makes it easier to enable/disable logging at runtime. The following example demonstrates configuring logging dynamically:
 
-| loggerLevel | java.util.logging |
-| ----------- | ----------------- |
-| OFF         | OFF               |
-| DEBUG       | FINE              |
-| TRACE       | FINEST            |
-
-`loggerFile`
-
-File name output of the logger. The default is `java.util.logging.ConsoleHandler`. The following example sets the logging level to `TRACE (FINEST)` and the log file `to EDB-JDBC.LOG`:
-
- `jdbc:edb://myhost:5444/mydb?loggerLevel=TRACE&loggerFile=EDB-JDBC.LOG`
-
-## Enabling logging with logging.properties (dynamic)
-
-You can use logging properties to configure the driver dynamically (for example, when using the JDBC Connector with an application server such as Tomcat, JBoss, WildFly, etc.), which makes it easier to enable/disable logging at runtime. The following example shows configuring logging dynamically:
 
 ```text
 handlers = java.util.logging.FileHandler
@@ -50,7 +34,10 @@ The default file output is in the user’s home directory:
 java.util.logging.FileHandler.pattern = %h/EDB-JDBC%u.log
 java.util.logging.FileHandler.limit = 5000000
 java.util.logging.FileHandler.count = 20
-java.util.logging.FileHandler.formatter = java.util.logging.SimpleFormatter java.util.logging.FileHandler.level = FINEST  java.util.logging.SimpleFormatter.format=%1$tY-%1$tm-%1$td %1$tH:%1$tM:%1$tS %4$s %2$s %5$s%6$s%n
+java.util.logging.FileHandler.formatter = 
+java.util.logging.SimpleFormatter 
+java.util.logging.FileHandler.level = FINEST  
+java.util.logging.SimpleFormatter.format=%1$tY-%1$tm-%1$td %1$tH:%1$tM:%1$tS %4$s %2$s %5$s%6$s%n
 ```
 
 Use the following command to set the logging level for the JDBC Connector to `FINEST` (maps to `loggerLevel`):

diff --git a/...42.3.2.1/11_reference_jdbc_data_types.mdx → ...42.3.3.1/11_reference_jdbc_data_types.mdx b/...42.3.2.1/11_reference_jdbc_data_types.mdx → ...42.3.3.1/11_reference_jdbc_data_types.mdx
diff --git a/....1/images/core_classes_and_interfaces.png → ....1/images/core_classes_and_interfaces.png b/....1/images/core_classes_and_interfaces.png → ....1/images/core_classes_and_interfaces.png
diff --git a/...42.3.2.1/images/drivermanager_drivers.png → ...42.3.3.1/images/drivermanager_drivers.png b/...42.3.2.1/images/drivermanager_drivers.png → ...42.3.3.1/images/drivermanager_drivers.png
diff --git a/...3.2.1/images/jdbc_class_relationships.png → ...3.3.1/images/jdbc_class_relationships.png b/...3.2.1/images/jdbc_class_relationships.png → ...3.3.1/images/jdbc_class_relationships.png
diff --git a/...2.1/images/jdbc_installation_complete.png → ...3.1/images/jdbc_installation_complete.png b/...2.1/images/jdbc_installation_complete.png → ...3.1/images/jdbc_installation_complete.png
diff --git a/...3.2.1/images/jdbc_installation_dialog.png → ...3.3.1/images/jdbc_installation_dialog.png b/...3.2.1/images/jdbc_installation_dialog.png → ...3.3.1/images/jdbc_installation_dialog.png
diff --git a/...3.2.1/images/jdbc_installation_wizard.png → ...3.3.1/images/jdbc_installation_wizard.png b/...3.2.1/images/jdbc_installation_wizard.png → ...3.3.1/images/jdbc_installation_wizard.png
diff --git a/...ctor/42.3.2.1/images/ready_to_install.png → ...ctor/42.3.3.1/images/ready_to_install.png b/...ctor/42.3.2.1/images/ready_to_install.png → ...ctor/42.3.3.1/images/ready_to_install.png
diff --git a/...es/selecting_the_connectors_installer.png → ...es/selecting_the_connectors_installer.png b/...es/selecting_the_connectors_installer.png → ...es/selecting_the_connectors_installer.png
diff --git a/...2.1/images/starting_stackbuilder_plus.png → ...3.1/images/starting_stackbuilder_plus.png b/...2.1/images/starting_stackbuilder_plus.png → ...3.1/images/starting_stackbuilder_plus.png
diff --git a/...3.2.1/images/the_showemployees_window.png → ...3.3.1/images/the_showemployees_window.png b/...3.2.1/images/the_showemployees_window.png → ...3.3.1/images/the_showemployees_window.png
diff --git a/...cs/docs/jdbc_connector/42.3.2.1/index.mdx → ...cs/docs/jdbc_connector/42.3.3.1/index.mdx b/...cs/docs/jdbc_connector/42.3.2.1/index.mdx → ...cs/docs/jdbc_connector/42.3.3.1/index.mdx
diff --git a/static/_redirects b/static/_redirects
@@ -85,6 +85,8 @@
 /docs/jdbc_connector/42.2.12.3/*  /docs/jdbc_connector/latest/:splat  301
 /docs/jdbc_connector/42.2.19.1/*  /docs/jdbc_connector/latest/:splat  301
 /docs/jdbc_connector/42.2.24.1/*  /docs/jdbc_connector/latest/:splat  301
+/docs/jdbc_connector/42.2.24.1/*  /docs/jdbc_connector/latest/:splat  301
+/docs/jdbc_connector/42.3.2.1/*   /docs/jdbc_connector/latest/:splat  301
 
 # ODBC Connector
 #   collapsed versions