Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
We are outputting some records to Snowflake.
We have a Reject trigger than logs the error message of any rejected records.
However, the error message is logged twice no matter how many rejected rows we have.
Here is a snippet from the logs:
Records Processed: 5
Records Sent: 4
Records Rejected: 1
Reject Reason: Timestamp '0001-12-31 18:09:24-05:50:36 BC' is not recognized
Reject Reason: Timestamp '0001-12-31 18:09:24-05:50:36 BC' is not recognized
As you can see, there is only one rejected record but the error is logged twice (in this case a bad date). I have verified all this in the source and target tables. That all works as expected.
Here is a screenshot of the subjob.
tJava_23 is what is doing the reject logging.
tJava_14 is what is doing the processed, sent, and rejected logging.
Pretty basic. I am at a loss as to why this would be logged out twice.
Any insight is appreciated.
Thank you!
I solved my own question.
There were two columns in the same row with the exact same "bad" date.
I originally thought this odd since everything points to rejected "rows" so I assumed there should be one error. But, it is clearly every rejection; not rows specifically.
This might help someone in the future.
I solved my own question.
There were two columns in the same row with the exact same "bad" date.
I originally thought this odd since everything points to rejected "rows" so I assumed there should be one error. But, it is clearly every rejection; not rows specifically.
This might help someone in the future.