Clover 2.8.0: Null Key values and DENORMALIZER nodes

anweston

• September 08, 2009 00:00

• Answered

Follow

Heya,

I noticed that the release notes for 2.8.0 say that it "unified null and empty field values in sorting, Dedup, etc" Were there any changes to the DENORMALIZER node? We have files where the key fields are null and with the DEDUP node that isn't a problem because of the "equalNULL" attribute. The DENORMALIZER hasn't had that kind of flag and we used a forum suggestion to use a REFORMAT node to put a dummy value in the nullable key fields and then strip it out in the DENORMALIZER node. Do we still have to do this with version 2.8.0? We're trying to minimize the number of nodes for performance's sake. :mrgreen:

Thanks,
Anna

• 

  twaller

  • September 09, 2009 06:31

  0

  Comment actions Permalink

  Hello,
  
  in CloverETL 2.8, the EqualNULL attribute exists in the following components:
  Dedup
  DataIntersection
  Denormalizer
  Rollup (new component)
  in the four components mentioned above, the default value of EqualNULL is true.
  Aggregate - in it, the default value remains false.
  
  Best regards,
  
  Tomas Waller
• 

  twaller

  • September 09, 2009 06:56

  0

  Comment actions Permalink

  Moreover, in sorting components:
  ExtSort
  FastSort
  SortWithinGroups
  null values are considered equal.
  
  In all Joiners, null values are considered different.
  
  Regards,
  
  Tomas Waller
• 

  mzatopek

  • September 09, 2009 07:14

  0

  Comment actions Permalink

  The answer is YES. Now you can already omit your reformat node, because the null values are handled as equal by default. Enjoy it :)
• 

  anweston

  • September 09, 2009 14:37

  0

  Comment actions Permalink

  Woo hoo! Another set of nodes we can get rid of!!
  
  Thanks for the replies!
  
  Anna :D

Please sign in to leave a comment.