+38A FeatureReader typically outputs data features on defined data ports, plus the "<Schema>" and "<Initiator>" ports.
I know that "<Schema>" features gets output before any data features (from that schema), but what about "<Initiator>" ?
Does this feature get output at the very end, i.e. after all data (for this initiator) has been output ?
If not, is there a way to initiate a downstream transformer _after_ all data has been output ?
Best answer by jdh
The initiator is output last, that's the only way it can have a valid _matched_records attribute.
+60The way I do this is by putting all features through a Sampler and set it to last 1.
+38I tried and attached loggers to the "<Initiator>" port and all data ports.
It does seem, that the "initiator" feature is logged last, although this is only determined by its position in the log, not the (identical) timestamps.
+38The way I do this is by putting all features through a Sampler and set it to last 1.
Plan B :-)
+37The initiator is output last, that's the only way it can have a valid _matched_records attribute.
+38The initiator is output last, that's the only way it can have a valid _matched_records attribute.
Excellent point.
