Table of Contents

Search

  1. Introduction
  2. Configuring Hub Console Tools
  3. Building the Data Model
  4. Configuring the Data Flow
  5. Executing Informatica MDM Hub Processes
  6. Configuring Application Access
  7. MDM Hub Properties
  8. Viewing Configuration Details
  9. Search with Solr
  10. Row-level Locking
  11. MDM Hub Logging
  12. Table Partitioning
  13. Collecting MDM Environment Information with the Product Usage Toolkit
  14. Glossary

Build Match Groups and Transitive Matches

Build Match Groups and Transitive Matches

The Build Match Group (BMG) process removes redundant matching in advance of the consolidate process. For example, suppose a base object had the following match pairs:
  • record 1 matches to record 2
  • record 2 matches to record 3
  • record 3 matches to record 4
After running the match process and creating build match groups, and before the running consolidation process, you might see the following records:
  • record 2 matches to record 1
  • record 3 matches to record 1
  • record 4 matches to record 1
In this example, there was no explicit rule that matched record 4 to record 1. Instead, the match was made indirectly due to the behavior of other matches (record 1 matched to 2, 2 matched to 3, and 3 matched to 4). An indirect matching is also known as a
transitive match
. In the Merge Manager and Data Manager, you can display the complete match history to expose the details of transitive matches.
If you use the Build Match Group (BMG) process, enable
Accept All unmatched Rows as Unique
in the match properties for the base object. If you do not enable
Accept All unmatched Rows as Unique
, the wrong value for rowid_match_rule appears in the HMRG table during transitive matching.

0 COMMENTS

We’d like to hear from you!