This wiki is no longer being updated as of December 10, 2025.
  • In an effort to make our documentation better for our users, we are consolidating and streamlining the documents.
  • Please see our new, updated documentation at: Melissa Docs or https://docs.melissa.com/

Issues:MatchUp Object: Difference between revisions

From Melissa Data Wiki
Jump to navigation Jump to search
← Older editNewer edit →
No edit summary
Tim (talk | contribs)
Write
484 edits
No edit summary
Line 5: Line 5:
See [[MatchUp Object:Best Practices|MatchUp Object Best Practices]] for override instructions.
See [[MatchUp Object:Best Practices|MatchUp Object Best Practices]] for override instructions.


==Fuzzy: Containment returns false for empty values==
If you set a component as Both Fields for the short empty. <br>
and set fuzzy setting to Containment <br>
Then, Compare two records where the component values are blank for both records. <br>
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




Line 25: Line 14:




==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 <br>
ex: 23505 K49, Le Mars, IA, 51031
==Data: highway pattern parsing==
The mdMatchUp.dat has many 'Highway type' indicators, but needs... <br>
[Street] <br>
COUNTY ROAD,Highway,Hwy,4 <br>




Revision as of 15:01, 2 July 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 Object Best Practices for override instructions.


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

Back to MatchUp Object Main Page

Retrieved from "http://wiki.melissadata.com/index.php?title=Issues:MatchUp_Object&oldid=4410"