Issues:MatchUp Object

From Melissa Data Wiki
Revision as of 15:03, 4 April 2014 by Tim (talk | contribs)
Jump to navigation Jump to search


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


Fuzzy: First component with set distance missing dupes

Keybuilding

Email Domain Update: 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.


When parsing a FullName (keybuilding) datatype, hyphenated last names with spaces around the hyphen, keys not built with both last name parts.


Alpha Numeric County Road patterns' keys not built correctly
ex: 23505 K49, Le Mars, IA, 51031


Data: highway pattern parsing

The mdMatchUp.dat has many 'Highway type' indicators, but needs...

[Street]
COUNTY ROAD,Highway,Hwy,4


Back to MatchUp Object Main Page