Bug when logging job stats to stats table when running tELTPostgresqlOutput
The component seems to want to recreate the table which causes this bug:
Exception in component talendStats_DB (LoadClubs_ELT)Exception in component talendStats_DB (LoadClubs_ELT)java.lang.NullPointerException at local_project.loadclubs_elt_0_1.LoadClubs_ELT.talendStats_STATSProcess(LoadClubs_ELT.java:2824) at local_project.loadclubs_elt_0_1.LoadClubs_ELT.runJobInTOS(LoadClubs_ELT.java:9252) at local_project.loadclubs_elt_0_1.LoadClubs_ELT.main(LoadClubs_ELT.java:9057)[FATAL] 12:51:56 local_project.loadclubs_elt_0_1.LoadClubs_ELT- talendStats_DB nulljava.lang.NullPointerException: null at local_project.loadclubs_elt_0_1.LoadClubs_ELT.talendStats_STATSProcess(LoadClubs_ELT.java:2824) [classes/:?] at local_project.loadclubs_elt_0_1.LoadClubs_ELT.runJobInTOS(LoadClubs_ELT.java:9252) [classes/:?] at local_project.loadclubs_elt_0_1.LoadClubs_ELT.main(LoadClubs_ELT.java:9057) [classes/:?]
In the Stats & Logs property of the job if you set the Stats Table to a table that does not exist then the job will run successfully and the stats data will be logged in the table. If you then run the job for a second time it will fail (see above).
