Query Issue - Generic JDBC - Execute
Using a Generic JDBC - Execute snap at the beginning of my pipeline with a hard-coded SQL query that has no issues running from any other place (workbench, phpstorm, etc) returns 800 results and an e...
Forum Discussion
I found that there was an invalid date-time value set on one record which was the issue.
This does make me curious though, why would the whole process stop because of one row instead of either casting it as a string or just skipping only that one record and outputting an error for it?
The hard-stop seems counter to what snaplogic is supposed to do with creating a document for each row of data from the query.
