Include the row being processed in any exception

Bug #619390 reported by Phill
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
NDataflow
Fix Released
High
Phill

Bug Description

Currently, if there is an exception the row causing the problem is not automatically reported by the framework. To resolve this, any component used the framework that throws an exception should, where appropriate, include the row that caused the problem.

For Action delegate components this involves a wrapper around the action decorating the exception that is being throw with data.

For Pipeline delegate components this involved a wrapper around the whole pipeline call decorating the exception with the last row that was sent into the pipeline component for processing.

For class implemented components this will be similar to the Pipeline delegate, but also adding to the framework to allow pre-run checks to be performed so that exceptions can be throw before rows are injected so that row information is not included where it is not relevant.

Related branches

Revision history for this message
Phill (phill.l) wrote :

WARNING: Some components in the framework do not use the Pipe method (which is the only generic framework method) to perform their actions. These will need to be changed to redirect through this method in order to gain advantage from this change.

Changed in easyetldotnet:
milestone: none → alpha
importance: Undecided → High
status: New → Confirmed
assignee: nobody → Phill (flooby)
Phill (phill.l)
Changed in easyetldotnet:
status: Confirmed → In Progress
Phill (phill.l)
Changed in easyetldotnet:
status: In Progress → Fix Committed
Phill (phill.l)
Changed in easyetldotnet:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.