Discover all of the brand-new features and improvements to existing capabilities in the Dataiku 11.3 updateLET'S GO

Log nested exceptions

0 Kudos

It seems that when running jobs, if a nested exception occurs, only the top level exception is logged. This makes debugging very difficult, since the true error is not visible. Many Teradata errors occur as nested exceptions, so it would be very helpful if the Dataiku logger could tree down to the complete exception and write that to the log so the underlying issue behind these errors can be understood. I've gotten these messages for everything from out of space to invalid characters to overflowing a field. While I usually know to look for these conditions manually, it's very time consuming. Unfortunately, this sort of error also usually happens after a long execution time. For example, this one took 56 minutes to error out. That's a long iteration loop for trial and error processes, so a little more info here would save me hours. Example:


[14:48:05] [ERROR] [dku.output.sql] - Nested exception
java.sql.SQLException: [Teradata JDBC Driver] [TeraJDBC] [Error 1339] [SQLState HY000] A failure occurred while executing a PreparedStatement batch request. The parameter set was not executed and should be resubmitted individually using the PreparedStatement executeUpdate method.
	at com.teradata.jdbc.jdbc_4.util.ErrorFactory.cloneJDBCException(
	at com.teradata.jdbc.jdbc_4.util.ErrorFactory.makeChainedBatchJDBCException(
	at com.teradata.jdbc.jdbc_4.statemachine.PreparedBatchStatementController.handleRunException(
	at com.teradata.jdbc.jdbc_4.statemachine.StatementController.runBody(
	at com.teradata.jdbc.jdbc_4.TDStatement.executeStatement(
	at com.teradata.jdbc.jdbc_4.TDPreparedStatement.executeBatchDMLArray(
	at com.teradata.jdbc.jdbc_4.TDPreparedStatement.executeBatch(
	at com.dataiku.dip.datasets.sql.SQLTableOutput$SQLTableOutputWriter.emitRow(
	at com.dataiku.dip.datalayer.ProcessorOutputToSIP.emitRow(
	at com.dataiku.dip.dataflow.exec.sql.SQLQueryRecipeRunner.runRegular(
	at com.dataiku.dip.dataflow.jobrunner.ActivityRunner$


1 Comment

Just following up on this, it'd really help quality of life for Teradata users to have this. Basically, there's very little error logging for Teradata right now, since the majority of errors are nested exceptions. It's very difficult to troubleshoot failing recipes without errors being logged.