Skip to main content
  • EN

With the original readers / writers you could control reader / writer order in the Navigator to upgrade performance.

But in a workflow with only FeatureReaders I have a data table being read completely before the lookup table starts to read. This causes all my datafeatures collected at a FeatureMerger before the lookuptable is read.

Any way to do this?

You should be able to control the order in which the FeatureReaders are fired by controlling the order of the incoming initiator features.

Or am I misunderstanding something?

Correct and if you are using a creator to trigger the featurereaders, you can now control the connection runtime exiting the creator(s), just right click on the connection > set connection runtime order

You should be able to control the order in which the FeatureReaders are fired by controlling the order of the incoming initiator features.

Or am I misunderstanding something?

Sorry, my bad. Still getting used to FeatureReaders plus forgot FeatureMerger parameter Suppliers First.

 

Correct and if you are using a creator to trigger the featurereaders, you can now control the connection runtime exiting the creator(s), just right click on the connection > set connection runtime order

Sweet, learned something new today! This looks more like the exact answer David.

 

 

Sweet, learned something new today! This looks more like the exact answer David.

 

 

Well, not everybody uses Creators to trigger their FeatureReaders. If that is the case, why not just use a regular reader?

Reply


Community Stats

30,123
Posts
114,333
Replies
37,751
Members
Terms & ConditionsCookie 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.