Skip to main content
Question

Bug in FME ? - "SQL to run after write" triggered even after a Terminator is activated

  • October 30, 2024
  • 4 replies
  • 43 views
lifalin2016
Contributor
Forum|alt.badge.img+29

I would assume (dangerous in this case), that a Terminator would halt processing completely.

I have a workspace, that imports from a WFS. It errs because the provider made a breaking change by removing a column in the read dataset. This issues a rejected feature, which triggers a Terminator.

But even then, the postprocess action of my SQL writer is triggered.

Why does this happen ?

If a terminator is called, it indicates that the workspace has failed. And then triggering postprocessing is a dangerous action, as this usually requires the writing to have been completed without errors.

Is this not a bug ?

Using FME 2022.2.6 on FME Server/Flow.

Cheers

-- Cheers, Lars I.

4 replies

nielsgerrits
VIP
Forum|alt.badge.img+52

I think this depends on how the transformers are connected? Is the SQL writer only connected with the readers output? Sorry if this sounds dumb but just double checking.

hkingsbury
1 person upvoted this
  • hkingsbury
    hkingsbury
hkingsbury
Celebrity
Forum|alt.badge.img+50
  • hkingsburyCelebrity
  • Celebrity
  • October 30, 2024
nielsgerrits wrote:

I think this depends on how the transformers are connected? Is the SQL writer only connected with the readers output? Sorry if this sounds dumb but just double checking.

Yea, you’d want to hold off running any post processing until you’re sure that all API calls have successfully run.

Something like the following would achieve that:
 

 

lifalin2016
Contributor
Forum|alt.badge.img+29
  • lifalin2016Contributor
  • Author
  • Contributor
  • November 1, 2024
nielsgerrits wrote:

I think this depends on how the transformers are connected? Is the SQL writer only connected with the readers output? Sorry if this sounds dumb but just double checking.

 

It’s not a question of transformers and connections.

It’s the advanced setting “SQL To Run After Write” on the MSSQL_SPATIAL writer.

I have no control on when and if this piece of code is executed. Which is the reason for my question.

I recently introduced a Terminator transformer to force the workspace to fail, and was suprised to see, that the post-process code was executed regardless.

-- Cheers, Lars I.
nielsgerrits
VIP
Forum|alt.badge.img+52
lifalin2016 wrote:
nielsgerrits wrote:

I think this depends on how the transformers are connected? Is the SQL writer only connected with the readers output? Sorry if this sounds dumb but just double checking.

 

It’s not a question of transformers and connections.

It’s the advanced setting “SQL To Run After Write” on the MSSQL_SPATIAL writer.

I have no control on when and if this piece of code is executed. Which is the reason for my question.

I recently introduced a Terminator transformer to force the workspace to fail, and was suprised to see, that the post-process code was executed regardless.

Clear. I’m not sure if this is expected behaviour but I would think not.

Reply


Most helpful members this week

Community Stats

30,851
Posts
116,970
Replies
38,683
Members
Terms & ConditionsCookie settings

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
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.