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?
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