Skip to main content
Archived

Significantly improve "Rejected" error message information from FeatureReader

Related products:Transformers
  • November 24, 2016
  • 1 reply
  • 3 views

lifalin2016
Supporter

Hi,

I’m trying to build a dataflow using FeatureReader to read my files.

Whenever I encounter a file with an error, the log file contains this snippet:

2016-11-24 09:50:12| 994.1| 0.0|INFORM|Expected a value string for '%L1KR', found '%KM1' instead, in line '916' of input file

2016-11-24 09:50:12| 994.1| 0.0|INFORM|DSFL halted, approx. line in input file: '916'

2016-11-24 09:50:12| 994.1| 0.0|ERROR |Error DSFL expected a value string from the input file

2016-11-24 09:50:12| 994.1| 0.0|INFORM|Closing the DSFL reader

However, the feature output by the “<Rejected>” port of the FeatureReader only contains a single “_reader_error” attribute with very limited content:

Error DSFL expected a value string from the input file

Would it be possible to enhance this error output significantly, preferably adding more error information (e.g. the offending line number), but at least so that the error message attribute reflects the full error messages shown at the top in the log file ?

Cheers

Lars I.

This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

1 reply

lifalin2016
Supporter
Forum|alt.badge.img+37
  • Author
  • Supporter
  • January 28, 2019

To add to my previous suggestion, how about adding the transformer name and other relevant attributes pertinent to the reader format in the REJECTED port as well ? As it is now, it's anyones guess which transformer failed if multiple FeatureReader rejected ports end up in the same error handling.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings