You can configure any crawl to write MDEX-compatible output; however, the most common scenario is to create a Record Store Merger crawl to write MDEX-compatible output. When the crawl runs in full-crawl mode, it does the following high-level operations:
Note
A crawl configured to produce MDEX-compatible output does not write dimension value records or any configuration stored in the Endeca Configuration Repository (such as properties and dimensions, precedence rules, and so on) when running in incremental mode. Run a full crawl if you want to create MDEX-compatible output that includes dimension value records and configuration stored in the Endeca Configuration Repository.
