Hi @gio, try checking the Process Duplicate Suppliers.

@takashi

Hi Takashi,

I don't need to process duplicates. And it therefore should not bug me with the "extra_reference_feature".

The point is that there are no duplicates technically, only some of the merge keys are, and some are even null or empty so technically duplicate key.

7keys.png

Here are 7 keys. The keys combined are unique. Only separate keys might and are none-unique.

There is no need to waste time concatenating the keys in to a single key here as I am supposed to be able to merge on multiple keys.

But the transformer seems to judge individual keys and pass them to the rejected port, forcing me to add a disabled inspector to this port.

I understand the logic of the merging. I do state that 1 or more single keys out of multiple keys being non-unique should not yield a duplicate detection if the total keys are unique.

And even so, it should not halt the process (when no inspector is connected).

@gio,

What about changing the workspace parameters on how the rejected features are handled?

It will still say that you have extra reference features, but it wont terminate your translation and you wont need to add a disabled inspector.

So there is a setting to have it not terminate translation.

But this does not address my complaint.

There is NO extra reference feature.

The combined merge-keys are unique.

The transformer starts nagging as soon as there is one or more sub-keys of the key-complex that is not unique!

It therefore should not report extra reference keys. No object should be rejected, they should be passed to the unreferenced port.