Details
-
Type:
Improvement
-
Status: Closed
-
Severity:
High
-
Resolution: Done
-
Affects Version/s: 5.4.0 GA, 6.0.0 GA
-
Component/s: Database
-
Labels:None
-
Story Points:0
-
Notice:
-
Epic Link:
Description
As an ETL developer, I would like to be able to select a custom JDBC driver to be used with a specific dialect. This allows flexibility in situations where I have multiple database driver options for a given database type (Impala, Redshift, MySQL/MariaDB, etc).
The generic database dialect option does not work in all cases, as any database dialect-specific settings would not be used with the Generic option.
This also helps when wanting to use the Log4JDBC driver, which provides a proxy class to do debug logging between Pentaho and a JDBC driver.

See the below link for our UX recommendation. Please feel free to reach out to Stephanie Bodendorfer if you have any questions.
http://ux.pentaho.com/pdi-dbc-driver-override/#g=1&p=concept
PractiTest Integration
Attachments
Issue Links
- is duplicated by
-
PDI-15696 improve DB2DatabaseMeta to support type 2 drivers
-
- Closed
-
- is related to
-
PDI-15528 Sybase JTDS driver issue
-
- Open
-
-
PDI-17692 Overriding the dialect on Generic Connection is not being called as expected
-
- Closed
-
-
PDI-15578 Allow the creation of a JDBC URL per Oracle documentation
-
- Closed
-
-
PDI-13565 jconn4 driver support for Sybase IQ database (null)
-
- Open
-
-
BISERVER-8085 DAW - The MySQL JDBC connection must be defined (in datasources table) as org.gjt.mm.mysql.Driver for getDatabaseMeta to "know" it's mysql
-
- Closed
-
-
PDI-14925 Include Log4JDBC for easier debugging
-
- Closed
-
- relates to
-
PDI-7640 As an ETL-Developer, I want to define new database dialects and change the behaviour of existing ones more easily without Java coding
-
- Open
-
- links to