commentBlock = $("#comment_post_37092").find('.comment-blocks'); commentBlock.find('.loading').hide(); commentBlock.find('.see-all-comments').hide(); commentBlock.html("
<\/a>
\"Brian<\/a>
Brian Dandeneau<\/a> Business Process and Strategy Specialist Advisor at NTTData<\/span><\/div>
<\/i>Top 5<\/span><\/span><\/span>Consultant<\/span><\/div>
<\/i><\/div>
<\/i>Report as inappropriate<\/a><\/div><\/div><\/div>

Alan Yves. Thanks for the comment. I would agree that definitely ODI can capture simple things like missing columns or the fact that you can create custom error handling. What I was referring to is out-of-the-box error handling. If you were to hook source file to a target table in other ETL tools there are built in error handling. Basically the Debugger needs some debugging. Although I don\'t mind all the extra billable hours sometimes you just want to know what record caused the error and not have to build a whole extra step.<\/p><\/div>

<\/i>Like<\/span>(0<\/span>)<\/a><\/i>Reply<\/span><\/a><\/div>
<\/div><\/div>
<\/a>
\"Alan<\/a>
Alan Yves<\/a>Big Data / Business Intelligence / Datawarehousing at DWgrain (Client Health BIS)<\/span><\/div>
<\/span>Consultant<\/span><\/div>