Skip to main content
Question

stream order in feature caching partial runs

  • July 8, 2019
  • 2 replies
  • 39 views

jdh
Contributor
Forum|alt.badge.img+40

Has anyone else had issues with feature order in partial runs when there are two parallel streams?

 

 

Example a SpatialFilter set to Filters First

 

If I run the entire workspace everything behaves as expected.

 

If I Run From This on the SpatialFilter, all the filters are rejected as `EXTRA_BASE_FEATURE' and all the Candidates fail (due to lack of filters).

 

 

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

fmelizard
Safer
Forum|alt.badge.img+21
  • Safer
  • July 9, 2019

Hi @jdh I've reproduced the problem with FME 2019.0 and 2019.2 beta and have filed FMEENGINE-60677 about this. It's likely that any transformer which depends on feature order is affected for partial runs. Thanks for letting us know!


jdh
Contributor
Forum|alt.badge.img+40
  • Author
  • Contributor
  • July 9, 2019

Hi @jdh I've reproduced the problem with FME 2019.0 and 2019.2 beta and have filed FMEENGINE-60677 about this. It's likely that any transformer which depends on feature order is affected for partial runs. Thanks for letting us know!

I can confirm I've run into issues elsewhere, the SpatialFilter was simply the easiest to see what was going on.