13.07.2015 Views

TIBCO MDM Customization Guide - TIBCO Product Documentation

TIBCO MDM Customization Guide - TIBCO Product Documentation

TIBCO MDM Customization Guide - TIBCO Product Documentation

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Limitations| 237LimitationsThe Matching across repositories is based on the indexing of multiple repositoriesin a single Netrics table as a composite entity. This approach of using adenormalized table for indexing has several fundamental disadvantages, such asreplicating data, requirement of more memory for too many record bundles, andso on. These disadvantages counteracts with the fast searches on thedenormalized table, which do not require any joins.Therefore, you must carefully specify the composite entities and limit theircomplexity. Following are the various limitations that you must be aware of whilespecifying the index entities:• Composite index entities cannot be defined across a self relationship.• The repositories in a composite index entity must be specified in a linear way.The index entity does not allow two relationships in one repository, which isimplemented in the Index configuration file. Each repository tag inside theindex entity can only have one associated relationship.• Relationship attributes cannot be used in matching expressions. However, theText Search web service allows specifying relationship attributes for a searchcriteria.• Defining an index across reverse relationships is not possible. Similarly,matching and text searching across reverse relationships are not supported.<strong>TIBCO</strong> <strong>MDM</strong> <strong>Customization</strong> <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!