Difference between revisions of "Issues:MatchUp Object"
(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...") |
|||
| (18 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
[[MatchUp Object|← MatchUp Object]] | |||
{{CustomTOC}} | {{CustomTOC}} | ||
== | ==Error Executing Linux Scripts== | ||
''Build 5118'' | |||
'' | |||
When running some of the linux scripts, you may receive the error: | |||
: | |||
<code>bad interpreter: No such file or directory</code> | |||
As we migrate our ISO building process to a newer automated process, some of the files are still being compiled with ‘windows’ end of line formatting. | |||
;Resolution | |||
<code>Run … $ dos2unix <scriptname></code> | |||
< | |||
< | |||
==Matchcode Edits Not Saving== | |||
When using the Matchcode Editor, when selecting [OK] after editing a matchcode and then reopening the matchcode editor, the changes have not been saved. | |||
;Resolution | |||
Check the location of your Matchcode data files. This is usually C:\ProgramData/Melissa DATA\MatchUP unless you have overridden the installer and or your code. Right Click the MatchUp folder and give ‘Full Control’ permissions to the respective user group. | |||
==.NET Wrapper Namespace== | |||
''Build 2628'' | |||
: | The namespace in the new mdMatchUp.cs classes is 'namespace MDClasses'. The previous wrapper namespace is 'namespace MelissaData' thus breaking backwards compatibility. Updating to the new wrapper will require you do change the namespace and recompile. We will rollback the namespace name in the next build. | ||
::This | |||
==Fuzzy Algorithms: Accurate Near , Frequency, and other Levenshtein based algorithms== | |||
Using the Accurate Near fuzzy algorithm on one or more components, running the same data set repeatedly could sporadically return different dupe counts. | |||
This may not be apparent for a single run because the fuzzy algorithms do not return a percent difference for used algorithms, only returning a status whether the algorithm found a match between records. | |||
We identified a new compiler issue and have also reviewed our other fuzzy algorithms which use similar computations and compiler variable initialization. | |||
If you use any of the Fuzzy algorithms, please contact us and we will provide you with the available patch. | |||
==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|MatchUp Object Best Practices]] for override instructions. | |||
This is for the ReadWrite Interface only. | |||
==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== | |||
Setting a distance for a first component forces the component to use the Intersecting deduper. This may result in records within a set distance to be put in different clusters, and therefore may never get compared. <br> | |||
Workaround: Use an exact algorithm in the first component and keep a distance component, if required further down the component list. This will prevent missed dupes (and give you better speed benchmarks. <br> | |||
Resolution: This may require an advanced change to the deduper. Development is aware of the issue and is exploring options. | |||
[[Category:Issues]] | [[Category:Issues]] | ||
[[Category:MatchUp Object]] | [[Category:MatchUp Object]] | ||
Revision as of 01:25, 23 December 2021
Error Executing Linux Scripts
Build 5118
When running some of the linux scripts, you may receive the error:
bad interpreter: No such file or directory
As we migrate our ISO building process to a newer automated process, some of the files are still being compiled with ‘windows’ end of line formatting.
- Resolution
Run … $ dos2unix <scriptname>
Matchcode Edits Not Saving
When using the Matchcode Editor, when selecting [OK] after editing a matchcode and then reopening the matchcode editor, the changes have not been saved.
- Resolution
Check the location of your Matchcode data files. This is usually C:\ProgramData/Melissa DATA\MatchUP unless you have overridden the installer and or your code. Right Click the MatchUp folder and give ‘Full Control’ permissions to the respective user group.
.NET Wrapper Namespace
Build 2628
The namespace in the new mdMatchUp.cs classes is 'namespace MDClasses'. The previous wrapper namespace is 'namespace MelissaData' thus breaking backwards compatibility. Updating to the new wrapper will require you do change the namespace and recompile. We will rollback the namespace name in the next build.
Fuzzy Algorithms: Accurate Near , Frequency, and other Levenshtein based algorithms
Using the Accurate Near fuzzy algorithm on one or more components, running the same data set repeatedly could sporadically return different dupe counts.
This may not be apparent for a single run because the fuzzy algorithms do not return a percent difference for used algorithms, only returning a status whether the algorithm found a match between records.
We identified a new compiler issue and have also reviewed our other fuzzy algorithms which use similar computations and compiler variable initialization.
If you use any of the Fuzzy algorithms, please contact us and we will provide you with the available patch.
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.
This is for the ReadWrite Interface only.
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
Setting a distance for a first component forces the component to use the Intersecting deduper. This may result in records within a set distance to be put in different clusters, and therefore may never get compared.
Workaround: Use an exact algorithm in the first component and keep a distance component, if required further down the component list. This will prevent missed dupes (and give you better speed benchmarks.
Resolution: This may require an advanced change to the deduper. Development is aware of the issue and is exploring options.