tLog row displaying different # of outputs than tPostgresqlOutput sends to DB
I have an odd problem, basically I have a parent job setup that takes in an excel sheet with 38 different context groups. The parent job runs taking in 1 context group at a time, sends it to a child job where it runs some API calls does some calculations and pushes the results to the DB waits 3 seconds then starts the parent job again iterating through 38 times. I've been seeing some weird issues where there are 0's being sent to the DB when they should not be. I've been doing some testing, and at the last step of the child job I have a tmap to tpostgresqloutput. I've added a tlog row as a separate output from the tmap to see what's happening. When I compare the tlog row to what is pushed to the DB sometimes there is a "double row" I'll call it. I see lets say 40 rows in the tlog outputs, for example, when the DB only shows 38 (which is the correct amount). It seems one of the "double rows" has the incorrect data and sometimes is being pushed into the DB rather than the correct row. I'm confused to why were getting double rows, and I've attached screenshots of the two jobs. If anyone has any ideas on what's going on I would love to hear it!
Date objects are not dependent on format. If you want a date that is limited to just yyyy-MM-dd you will need to ensure that the hours, minutes, seconds and milliseconds are set to 00:00:00.000. You can write a routine to do that which would be the easiest way to ensure it.
I just created the date in the tMap with "TalendDate.parseDate("yyyy-MM-dd",TalendDate.formatDate("yyyy-MM-dd",TalendDate.getCurrentDate())) ". I'm assuming this would work as well, but if you see nay issues please let me know. I've ran it a few times with no issues, but sometimes there's 10+ runs that look ok so I will continue testing, but think this may have been the cause.
