Difference between revisions of "Issues:MatchUp Object"

From Melissa Data Wiki
Jump to navigation Jump to search
Line 1: Line 1:
{{CustomTOC}}
{{CustomTOC}}
MatchUp Object known issues.
 


==Large KeyFile Size effect on Memory resources==
==Large KeyFile Size effect on Memory resources==

Revision as of 20:25, 17 February 2014



Large KeyFile Size effect on Memory resources

By default, MatchUp object allocates a large SetUserInfo, the unique identifier attached to built match key - 1024 bytes. See MatchUp Best Practices for override instructions.

Fuzzy: Containment returns false for empty values

If you set a component as Both Fields for the short empty.
and set fuzzy setting to Containment
Then, Compare two records where the component values are blank for both records.

The records do not match


Fuzzy: Jaro and Jaro-Winkler crashes on certain columns

Under certain combinations, Jaro settings for component size and component distance can cause a crash


Fuzzy: Legacy Matchcodes

Legacy Matchcodes, imported from previous versions, allowed a Fuzzy: Near setting of '0'. This is incompatible with the current version and can cause an error. Using the interface to edit the matchcode by changing the Distance to 1 will resolve the problem


Email domain Update Keys built incorrectly

If your source data contains a TLD of a domain you want to update, the key will not get updated with the new domain If the domain you wish to update does not have the TLD in the source data, the key does get built correctly.

Back to MatchUp Object Main Page