Skip to main content
Question

upgrade transformer FMEServerJobSubmitter to version some outputs disappears


rudy_v
Contributor
Forum|alt.badge.img+6

Hi All,

I have upgrade my FMEServerJobSubmitter to version 3 from 2, and now some output parameters has disappeared.- i have been using the number of features output, time start and time finish

version 2 below

after upgrade, it is no longer available, and make the attribute manager fail

3 replies

david_r
Celebrity
  • April 17, 2018

Actually, the previous versions of the FMEServerJobSubmitter had a slightly broken logic, where e.g. the _numFeaturesOutput attribute would be exposed even when Wait for jobs to complete = No, which didn't make any sense.

Now, the attributes are dynamic according to how you set the "Wait for job" parameter.

Wait for jobs to complete = No

Wait for jobs to complete = Yes

Based on the fact that your output port is called "Submitted" and not "Succeeded", I'm guessing Wait for jobs to complete = No in your workspace. If you change it around, you should get back the missing attributes.


rudy_v
Contributor
Forum|alt.badge.img+6
  • Author
  • Contributor
  • April 17, 2018
david_r wrote:

Actually, the previous versions of the FMEServerJobSubmitter had a slightly broken logic, where e.g. the _numFeaturesOutput attribute would be exposed even when Wait for jobs to complete = No, which didn't make any sense.

Now, the attributes are dynamic according to how you set the "Wait for job" parameter.

Wait for jobs to complete = No

Wait for jobs to complete = Yes

Based on the fact that your output port is called "Submitted" and not "Succeeded", I'm guessing Wait for jobs to complete = No in your workspace. If you change it around, you should get back the missing attributes.

@david_r - thanks for the update - but you don't get the succeeded / failed if

 

wait for job to complete is a published parameter

 

 


david_r
Celebrity
  • April 18, 2018
rudy_v wrote:
@david_r - thanks for the update - but you don't get the succeeded / failed if

 

wait for job to complete is a published parameter

 

 

Ah, that's an interesting edge case, thanks for pointing that out.

 

It kinda makes sense, however, since parameters aren't resolved before you actually execute the workspace. But still, I can see how that's annoying in this case.

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