Change order that features leave an AttributeFilter

Update: I was able to solve this particular issue by putting a FeatureHolder between the InterFeatureLink and its SQLExecutor. This works for now but I would really like to know if there is a more elegant way of doing this, as I foresee a lot more of these situations arising in this workflow and I can only imagine the headaches that are in store for me with an elaborate series of FeatureHolders

Not sure if this is the best way but I would put a FeatureHolder behind SQLExecutor_3, connected on the Initiator port. Then a Sampler, releasing the first feature when all features are released by the FeatureHolder. Then strip all attributes and geometry and send it to a FeatureMerger Supplier input port. Merge using 1=1 with the IneFeatureLink features. Merged output port to SQLExecutor_4.

Curious what others use for the order problem.

Hi @iboates,

Another option for controlling the flow of features is to use a blocking transformer like the Sorter. This will also allow you to control the order in which individual features are passed into the SQLExecutor.

The Blocking Transformers and the Flow of Features and In what order are features processed when there are parallel transformers articles might also be a good resource in the future!

Just an idea I have used before:

After the AttributeFilter, add an AttributeCreator to create a priority attribute (with value 1, 2 or 3).

Merge all lines together in a Sorter, sorting on priority.

Then use an other AttributeFilter to split on priority and pass features to different SQLExecutors.

Hope this helps.

Another transformer to look at is the Decelerator.

Not a nice solution, but sometimes (and maybe in this case) useful.

It simply waits an amount of time before passing on features.

Not the best solution if performance is an issue.