IgnatiusN
New Contributor II
Joined 9 years ago
User Profile
User Widgets
Contributions
Error after the pipeline runs successfully
We are getting the below error after our pipeline runs successfully… I don’t see failures with any of the pipeline snaps, the failure message shows up in dashboard after the pipeline completes. Encountered an error while streaming data to triggered task client Reason: An established connection was aborted by the software in your host machine Resolution: Make sure the task client consumes the entire response not sure why this error is happening. the pipeline is triggered using a task through cloud url3.1KViews0likes1CommentSQL Server Stored Procedure Snap
Hello, SQL Server Stored Procedure snap has 2 outputs, one for output parameters and another for result set. I am only interested in the resultset, how do I make sure the “output parameter” view is closed? We don’t want to have multiple open outputs in the pipeline. Thanks, Ignatius4.7KViews0likes4CommentsRe: Data Validator Snap - date - required validation
Thanks. We wanted to take advantage of the data validator snap’s error output ability. We ended up adding a mapper in front of the data validator snap to convert them to boolean strings (“true”/“false”) and using the pattern matching on data validator. It would be good to have some clarity on how “Required” works. According to the documentation “Required” should work for all data types. We also tried to validate the date using “Type” validation for “date”, that didn’t work too. The validator appears to be working good only for string types.2.5KViews0likes0CommentsException handling in pipeline
Is there a way to handle exceptions across the pipeline. If we have 100 records streaming, we want to route any record that failed to a log file, and still process all the remaining records. Handling error in each snap looks very tedious, and I wanted to check if there was anything we could do to handle exceptions across the pipeline and route it to an error view.3.1KViews0likes2Comments