Skip to main content Skip to complementary content

Overriding a database driver by customizing the Maven URI

If you have different versions of a database driver, you can override the current version of the driver by customizing its Maven URI. That is, upgrading to the latest version or roll back to a previous version. Overriding a driver allows your Jobs to use any driver versions that are available.

Before you begin

Make sure the desired versions of the driver (for example, ojdbc14.jar and ojdbc14-9i.jar in the previous section) are available.

Information noteNote:
  • To avoid overriding failures, make sure the dependencies of the desired driver are resolved.
  • If you override a driver using the up-to-date driver (for example, version 2021) and then Talend Studio upgrades with a newer driver version (for example, version 2022), the newer version will be used.
  • If you override a driver using an earlier driver (for example, overriding version 2021 using version 2020) and then Talend Studio upgrades with the latest driver version (for example, version 2022), the latest version (that is, version 2022) will be used.

Procedure

  1. In the Modules view, locate the driver you want to override, click the Maven URI of the driver you want to customize, and then click the [...] button that appears.
    The Install Module dialog box opens.
  2. Enter the full path to the desired driver file in the Module File field or click the [...] button and navigate to the desired driver file.
    If the MVN URI of the library is within the jar file and is different from the default MVN URI, it is automatically detected and filled in the Custom MVN URI field.
    Install Module dialog box.
  3. Select the Custom MVN URI check box and enter a new URI in the field.
  4. Click Detect the module install status and then OK to validate the custom URI and close the dialog box.
    Information noteNote: To revert to the original driver, clear the check box to the left of the Custom MVN URI field.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!