
ASHISH PATIL (Customer) asked a question.
MarkLogic Server 12.1.0, single-node, single-forest.
What we did:
1. Loaded ~1000 XML documents into a database with default indexing config.
2. Configured 5 index-exclusion-paths entries via the Management API.
3. Waited to see if the reindexer picked up the change automatically.
4. Manually triggered a reindex, then a database merge.
5. As a separate run, cleared the database, configured the same excluded
paths on the empty database, then reinserted the same 1000 documents.
What we observed:
- After step 2, automatic reindexing did not trigger.
- After step 4 (manual reindex and merge), there was no effect - verified
via before/after size metrics and via word search (content inside the
excluded paths was still returned by cts:word-query).
- After step 5 (clear, configure, then reload), the universal index was
reduced as expected: 71.5% smaller, with content size unchanged, and
word search no longer matched content inside the excluded paths.
No data loss in either case.
Workaround: clear the database, apply the excluded-paths config first,
then load documents.
Question: Is there a supported way to apply excluded paths to an existing
database and have it actually take effect, without a full clear-and-reload?
Just learned that this has been accepted as a P1 bug. Looking forward to the fix patch.