Skip to main content
Question

Inconsistent behaviour featuremerger missing

  • September 30, 2022
  • 3 replies
  • 44 views

romar
Contributor
Forum|alt.badge.img+3
  • Contributor
  • 3 replies

During one of my projects I noticed in my counts that I am missing records.

 

Project Image 

As you can see 16k entries enter the requester eand only 13k exit via either port. This is connected to missing keys entering into the requestor

 

I know that I can solve this using a nullattributemapper to change missing into null, or by setting reject null and missing keys to 'Yes' (non-default setting). However the fact that this is largely invisible has me worried.

 

I have also concluded that this behaviour is not consistent. The below workspace has a test setup testing for the behaviour with simple input data. All 4 cases behave as expected. Unless I missed something, I believe this is a bug. If you can confirm, deny or reproduce, it would be highly appreciated :).

 

 

3 replies

tomfriedl
Contributor
Forum|alt.badge.img+13
  • Contributor
  • 177 replies
  • September 30, 2022

Set the parameter "Reject Null and Missing Keys" to "Yes".

By the way: Very good Workbench to test


romar
Contributor
Forum|alt.badge.img+3
  • Author
  • Contributor
  • 3 replies
  • September 30, 2022

Set the parameter "Reject Null and Missing Keys" to "Yes".

By the way: Very good Workbench to test

Thank you for your answer and the compliment:).

 

I know of multiple ways of how to fix the issue, once spotted.

 

It is the 'stealth' and inconsistent behaviour of this issue that I am concerned about.


tomfriedl
Contributor
Forum|alt.badge.img+13
  • Contributor
  • 177 replies
  • September 30, 2022

You are right. Better is "Reject Null and Missing Keys" set default to "Yes". Much better the features going out to "UnmergedRequestor".