Skip to main content
Question

How to validate results of FME ETL process?


After the FME ETL process is completed, is there a way to validate the results automatically?

5 replies

danilo_fme
Evangelist
Forum|alt.badge.img+42
  • Evangelist
  • August 31, 2017

Hi @fantomfoto,

In my opinion you need to create another Workspace to validate your Writer:

- Schema

- Attributes

- Geometry

Thanks,

Danilo


Forum|alt.badge.img

Hi @fantomfoto

 

you definitely can do some automatic validation, e.g. you can check if a table has indeed been written into your database or the number of files output into a folder matches the expected number. The validation depends on your data and what might go wrong or what you would like to confirm did not go wrong. If you describe your scenario in more details, I am sure community will be happy to share ideas and suggestions.

 


rylanatsafe
Safer
Forum|alt.badge.img+13
  • Safer
  • August 31, 2017

For a general idea of the types of validation you can implement into your workflow, please see this Knowledge Center Article.

 

 

And, generally speaking, you could leverage FeatureWriter / FeatureReader in place of the native Reader / Writers in FME to have your ETL and validation occur in the same workspace – but it can just as easily be split into two workspaces. Note that this validation process itself will more or less have to read all the data back into FME, so when dealing with very large datasets it may impart a measurable overhead (especially those datasets where you cannot leverage filters or SQL statements to limit the number of features actually coming into the workspace).

danilo_fme
Evangelist
Forum|alt.badge.img+42
  • Evangelist
  • August 31, 2017
rylanatsafe wrote:

For a general idea of the types of validation you can implement into your workflow, please see this Knowledge Center Article.

 

 

And, generally speaking, you could leverage FeatureWriter / FeatureReader in place of the native Reader / Writers in FME to have your ETL and validation occur in the same workspace – but it can just as easily be split into two workspaces. Note that this validation process itself will more or less have to read all the data back into FME, so when dealing with very large datasets it may impart a measurable overhead (especially those datasets where you cannot leverage filters or SQL statements to limit the number of features actually coming into the workspace).
Hi @RylanAtSafe this article that you posted above is very interesting.

rylanatsafe
Safer
Forum|alt.badge.img+13
  • Safer
  • August 31, 2017
danilo_fme wrote:
Hi @RylanAtSafe this article that you posted above is very interesting.
It's a work in progress by @Mark2AtSafe – I'm excited to see the full picture as it comes out piece by piece!

 


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