Skip to main content
Question

Rejected Feature Handling: Continue Translation ignored when running with feature caching enabled

  • April 9, 2019
  • 2 replies
  • 1558 views

Forum|alt.badge.img

Getting failure from a <rejected> feature even though Rejected Feature Handling: Continue Translation selected:

 

2019-04-09 14:03:26|1543.0| 0.0|ERROR |FeatureMerger_2_<Rejected> (TeeFactory): FeatureMerger_2_<Rejected>: Termination Message: 'FeatureMerger_2 output a <Rejected> feature. To continue translation when features are rejected, change 'Workspace Parameters' > Translation > 'Rejected Feature Handling' to 'Continue Translation''

2019-04-09 14:03:26|1543.0| 0.0|ERROR |FeatureMerger_2_<Rejected>: Termination Message: 'FeatureMerger_2 output a <Rejected> feature. To continue translation when features are rejected, change 'Workspace Parameters' > Translation > 'Rejected Feature Handling' to 'Continue Translation''

I ran the fmw twice and got the same result. Here's my log up to the point of failure, if you're curious...Log with Feature Caching.txt

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, 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.

2 replies

jovitaatsafe
Safer
Forum|alt.badge.img+11

Hi @pvaziri,

I did a bit of digging and it looks like there is a difference between setting rejected feature handling in the Workspace Parameter Defaults where you are setting it, and setting it in the Workspace Parameters as Runtime options.

 

 

When setting the Workspace Parameter Defaults, this setting is used when you create a new workspace. The runtime option however can override this setting as the current user. To set the runtime option, you can go to the Navigator > Workspace Parameters > Translation > Rejected Feature Handling to set it to continue translation. Hope that helps!

 

 


Forum|alt.badge.img
  • Author
  • April 10, 2019

Hi @pvaziri,

I did a bit of digging and it looks like there is a difference between setting rejected feature handling in the Workspace Parameter Defaults where you are setting it, and setting it in the Workspace Parameters as Runtime options.

 

 

When setting the Workspace Parameter Defaults, this setting is used when you create a new workspace. The runtime option however can override this setting as the current user. To set the runtime option, you can go to the Navigator > Workspace Parameters > Translation > Rejected Feature Handling to set it to continue translation. Hope that helps!

 

 

It helps, although it is confusing and can lead to an unexpected error. Shouldn't the higher level FME Options setting override the Workspace Parameter (especially since that setting is referenced in the log). If it should work the other way (Workspace Parameter over FME Options setting), then what is presented in the log reflects what setting is causing the problem.