Difference between revisions of "Issues:MatchUp Object"

From Melissa Data Wiki
Jump to navigation Jump to search
(Created page with "{{CustomTOC}} MatchUp Object known issues. ==MatchUp API== ===Version 3.14=== ''Released February 2007'' *When a match group contains records because of one blank (short) ma...")
 
Line 2: Line 2:
MatchUp Object known issues.
MatchUp Object known issues.


==MatchUp API==
==Large KeyFile Size effect on Memory resources==
===Version 3.14===
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.
''Released February 2007''


*When a match group contains records because of one blank (short) matching, there is a chance that DTReadRecord may return a Dupe Group of 0 and a count of 0 for at least one of those records, even though its error code signifies it is matched as part of the group.
:This will be fixed in the next version
==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


;Unknown or Negative return codes.
:There is a problem with the high order bit (32) which is used in some languages and data types as a sign bit. Because the high order bits 32 - 17, which return the error codes are transposed, i.e.: bit 32 was combo 1, 31 was combo 2, etc - you get unknown or negative numbers returned when records matched using combination 1.


:;Status:
==Fuzzy: Jaro and Jaro-Winkler crashes on certain columns==
::This will be fixed in the next build. . There is an update for the API in the works, and we are looking into addressing this issue.
Under certain combinations, Jaro settings for component size and component distance can cause a crash


:;Workaround:
::Make sure to use combinations 16, 15, 14, etc (instead of 1, 2, 3, etc) in your code. Make sure to convert the signed integer into an unsigned after it has been read:
<blockquote>
<pre>If (Error<0)


Error=Error+4294967296</pre>
==Fuzzy: Legacy Matchcodes==
</blockquote>
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


::In case you’re wondering, 4294967296 is (2^32), which converts the number to it’s “2’s complement”.


==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.


;Function Declarations incorrectly defined as DtApi.
:The following function Declarations should read “Dt3Api”, not “DtApi” as below and in Visual Basic standard module DtApi.bas.
:Declare Sub BDTClose Lib "DtApi" (ByVal hDeduper As Long)
:Declare Sub DbgDTClose Lib "DtApi" (ByVal hDeduper As Long)
:;Status:
::This will be fixed in the next release.
:;Workaround:
::This could be fixed by simply changing DtApi to Dt3Api




[[Category:Issues]]
[[Category:Issues]]
[[Category:MatchUp Object]]
[[Category:MatchUp Object]]

Revision as of 16:30, 17 February 2014


MatchUp Object known issues.

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.

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