Skip to main content
Question

Inconsistent behaviour featuremerger missing

  • September 30, 2022
  • 3 replies
  • 29 views

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

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
  • 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
  • September 30, 2022
tomfriedl wrote:

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
  • 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".


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings