+1I am in doubt whether the custom transformer I created processes just one feature at a time. It does not have any "group-by" clause active, but still seems to accumulate all the features first and then process them, instead of processing one by one.
Is there a way how to check this behavior?
Or better, is there a way how to forcingly make it feature-based instead of group-based?
Thank you in anticipation,
Jaroslav
Best answer by takashi
I think it cannot generally be said whether a custom transformer behaves like group-based transformer. A test like this could be effective to check how your custom transformer behaves:
If the custom transformer behaves like group-based one, you will get {0, 1, 2, 3, 4, 0, 1, 2, 3, 4}, if not {0, 0, 1, 1, 2, 2, 3, 3, 4, 4}. Takashi
I think it cannot generally be said whether a custom transformer behaves like group-based transformer. A test like this could be effective to check how your custom transformer behaves:
If the custom transformer behaves like group-based one, you will get {0, 1, 2, 3, 4, 0, 1, 2, 3, 4}, if not {0, 0, 1, 1, 2, 2, 3, 3, 4, 4}. Takashi
