Since last couple of versions this really annoying message pop's up.
As soon as one or more merge keys has duplicates. Even if the combined keys are unique.
I am forced to put a (disabled) inspector on the rejected features output port.
PCNLTSTRAATNAAM2324HG702Bachstraat2324HG704Bachstraat2324HG706Bachstraat
In the example above I use both fields as merge keys. The "straatname" causes the extra_ref._feature rejection.
This gets worse if I merge on more fields, which I do in this workbench the example is from, up to 7 fields. (setting ignore nulls or empty will cause everything to not merge, as all of them have 1 or more with value null)
There is no setting to "ignore rejection" afaik.
Of course I can concatenate first into a merge_key to emulate oracle's "coalesce". But shouldn't be necessary I think.
Anyone knows why? Or is there a setting to stop this behavior.
Is there a "ignore rejection" option?