We're currently running into an issue with renaming columns within the Job log table that's specified within each job. Currently we have the following setup, which works:
However, in another environment we have I found that some of the columns specified here have been renamed, as you can see down below.
Here you see that LOGDATE has been replaced with ENDDATETIME and REPLAYDATE has been replaced with STARTDATETIME. These are also the actual column names within the Job log table.
The problem however is that we can't change the column names from the first mentioned instance. We would like to rename the columns so that they're aligned with the second instance, but when I rename the columns and recreate the table via the SQL button I get an error when running the Pentaho job:
2022/10/26 15:07:45 - Spoon - Starting job...
2022/10/26 15:07:45 - sj_dsa_synergy_kwartier_postgres - Start of job execution
2022/10/26 15:07:45 - sj_dsa_synergy_kwartier_postgres - ERROR (version 8.3.0.0-371, build 8.3.0.0-371 from 2019-06-11 11.09.08 by buildguy) : A serious error occurred during job execution:
2022/10/26 15:07:45 - sj_dsa_synergy_kwartier_postgres - Unable to begin processing by logging start in logtable RTICT_MONITORING_PENTAHO
2022/10/26 15:07:45 - sj_dsa_synergy_kwartier_postgres -
2022/10/26 15:07:45 - sj_dsa_synergy_kwartier_postgres - Unable to obtain last logdate from table "DPL_SP_META"."RTICT_MONITORING_PENTAHO"
2022/10/26 15:07:45 - sj_dsa_synergy_kwartier_postgres - ERROR: column "LOGDATE" does not exist
Hint: Perhaps you meant to reference the column "RTICT_MONITORING_PENTAHO.ENDDATE" or the column "RTICT_MONITORING_PENTAHO.DEPDATE".
Position: 170
For some reason when I've recreated the table with the renamed columns via Pentaho it still thinks it needs the 'old' column. As you can see in the logging here it is giving the error that the column LOGDATE does not exist. This is correct, because I've renamed this column to ENDDATETIME and recreated the table. In the table it therefore does not have this field, but I'd expect that when Pentaho recreates the table itself it would recognise the metadata.
The weirdest thing to me is that somehow it has worked in the past, since we have another instance that does work with renamed columns and works perfectly. Unfortunately I now have no opportunity to align both instances to one another.
Our Pentaho version is:
Any help is much appreciated.