JDBC connection opened linked to a tPreJob component leads to NullPointerException

[rmartin2]

Found a bug in 7.x (don't have access to JIRA but I reported it to one of your sales engineer I'm working with) :
If you open a connection in JDBC to GCP and try to use it in an ELT component, your connection finishes in NullPointerException probably because the ELT component build itself before the prejob code runs.

You have to use individual connection as far as I know ...
Only tested that on Google Cloud Platform, don't know if it's true in general.

[Anonymous]

Hi @mhodent,

Thanks for raising this. Could you give a screenshot of your job and the DB component configurations?

Also, you should be able to login to Jira here. Let me know if you cannot

Regards

Richard

[rmartin2]

Hi !

Here is the job :

It's pretty simple, but it doesn't seem to work ... The connection is marked as OK in the prejob. If you test connectivity it's ok, and you can parse your schema.

But if you try to run the thing, the connection is not created when ELT component try to initialize itself. So there's a NPE...

Thank you in advance !

[Anonymous]

Hmmm yes it does look pretty simple. I notice you have yellow triangles next to your input and output components. If you hover your cursor over them, what do they say?

Also, have you tried logging in to the Jira? I've read a few of your posts and you sound like the sort of person who would be great to have raising Jiras 🙂

[rmartin2]

Triangle are because I just put components as is. I didn't re-do the job.

I tried a simple thing with the sales engineer I know : try to use PostgreSQL components to connect to my GCP Instance.

I know from experience it works with Mysql on GCP without any changes.
It seems to work with Postgre too, and certs are not needed (strange !), while it's needed in JDBC.

I'll try later to use it in ELT mode, maybe it's related to the mode of connection (JDBC + SSL certificates).

Note : strange behaviour though, if you build this job, select the connection from metadata repository, a maven library is used. But if you "use" the connection on an ELT component, the target switch to the driver class (without maven URI). Maybe a clue to our problem.