Pentaho Data Integration - Kettle

Vertica v5.1 JDBC driver class name change

Details

  • PDI Sub-component:
  • Customer Case:
  • QA Validation Status:
    Validated by QA
  • CI Build:
    October 5 build.

Description

The current pre configured Vertica database connection type is set to use the JDBC driver class "com.vertica.Driver" for older versions of Vertica's driver. However, Vertica 5.1 JDBC driver class has now changed to "com.vertica.jdbc.Driver" so using the pre configured connection type no longer works for the new version. The obvious workaround would be to use the "Generic database" connection type and manually specify the correct driver class name.

Issue Links

is related to

Bug - A problem which impairs or prevents the functions of the product. PRD-3786 Vertica v5.1 JDBC driver class name change (Report Designer)

  • Severe - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
relates to

New Feature - A new feature of the product, which has yet to be developed. PDI-7640 As an ETL-Developer, I want to define new database dialects and change the behaviour or existing ones more easily without Java coding

  • Critical - Crashes, loss of data, severe memory leak.
  • Open - The issue is open and ready for the assignee to start work on it.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Jens Bleuel added a comment - - edited
This can be accomplished by PDI-7640. When we need this sooner, we may reevaluate this.

Edit: Fixed linked Jira case.
Show
Jens Bleuel added a comment - - edited This can be accomplished by PDI-7640 . When we need this sooner, we may reevaluate this. Edit: Fixed linked Jira case.
Hide
Permalink
Sebastian Beca C. added a comment -
I'm testing Vertica on two subscribed Pentaho clients and I'm having the same problem (with 4.3). I also tried "Generic database" and specifying the driver class, but this did not work either. Can you give details on the workaround in order to be able to have a connection to Vertica via PDI?
Show
Sebastian Beca C. added a comment - I'm testing Vertica on two subscribed Pentaho clients and I'm having the same problem (with 4.3). I also tried "Generic database" and specifying the driver class, but this did not work either. Can you give details on the workaround in order to be able to have a connection to Vertica via PDI?
Hide
Permalink
Jens Bleuel added a comment -
When you are a Pentaho customer, please contact customer support to follow up on this case.
Show
Jens Bleuel added a comment - When you are a Pentaho customer, please contact customer support to follow up on this case.
Hide
Permalink
Sebastian Beca C. added a comment -
I tried the Generic Database workaround but many database functions did not work well. I did get this working fine with Vertica 4.X drivers, which is the solution I would recommend until the driver class name is updated in PDI.
Show
Sebastian Beca C. added a comment - I tried the Generic Database workaround but many database functions did not work well. I did get this working fine with Vertica 4.X drivers, which is the solution I would recommend until the driver class name is updated in PDI.
Hide
Permalink
Jens Bleuel added a comment -
Options I can think of:
1) Add a checkbox to the database dialog: "Vertica version 5 and later"
This should be enabled by default for new connections (but kept disabled for existing connections for backward compatibility)
2) Create a database type plugin which would simply subclass the VerticaDatabaseMeta class and give it another name.
3) Allow setting the driver class by a parameter (this could be implemented as a general solution also for other databases) - but should be obsolete by implementing PDI-7640.
Show
Jens Bleuel added a comment - Options I can think of: 1) Add a checkbox to the database dialog: "Vertica version 5 and later" This should be enabled by default for new connections (but kept disabled for existing connections for backward compatibility) 2) Create a database type plugin which would simply subclass the VerticaDatabaseMeta class and give it another name. 3) Allow setting the driver class by a parameter (this could be implemented as a general solution also for other databases) - but should be obsolete by implementing PDI-7640 .
Hide
Permalink
Jens Bleuel added a comment -
Discussed with Matt: it would probably be easier just to create a new Database type "Vertica 5+". That way there would be no compatibility issues.
Show
Jens Bleuel added a comment - Discussed with Matt: it would probably be easier just to create a new Database type "Vertica 5+". That way there would be no compatibility issues.
Hide
Permalink
Jake Cornelius added a comment -
we should validate this with version 6 as well once implemented
Show
Jake Cornelius added a comment - we should validate this with version 6 as well once implemented
Hide
Permalink
Jens Bleuel added a comment -
Implemented in rev. 17232 (4.4.0) and rev. 17233 (trunk).
I validated that it loads the vertica-jdk5-6.0.0-0.jar with the "Vertica 5+" database type (using "com.vertica.jdbc.Driver").
Show
Jens Bleuel added a comment - Implemented in rev. 17232 (4.4.0) and rev. 17233 (trunk). I validated that it loads the vertica-jdk5-6.0.0-0.jar with the "Vertica 5+" database type (using "com.vertica.jdbc.Driver").
Hide
Permalink
Sean Flatley added a comment -
Validating.
Show
Sean Flatley added a comment - Validating.
Hide
Permalink
Sean Flatley added a comment -
Validated using my Vertica 6.0.0 for ESX VM as the databse and the vertica-jdk5-6.0.0-0.jar.

I ran the attached transformation and performed Database Explorer functions. Rowcounts, etc....
Show
Sean Flatley added a comment - Validated using my Vertica 6.0.0 for ESX VM as the databse and the vertica-jdk5-6.0.0-0.jar. I ran the attached transformation and performed Database Explorer functions. Rowcounts, etc....

People

  • Assignee:
    Sean Flatley
    Reporter:
    Christopher Morehouse
Vote (1)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved: