Hi,

when developing applications with ML as the database, we need to add new indexes regularly to deliver new features. We often (probably 95%) of the time add new indexes that will not hit any content in the database currently, but know that eventually will when new content is added.

As we have terabytes / millions of docs of content, these reindex operations can be costly and take considerable time to run.

So finally to the question: given that we're adding a new field that has one include, it seems that ML goes through all documents in the database (include limits by element and attribute value) - is there a way to tell ML that hey, we know, and we take the responsibility, that the database currently does not have any content that needs to be reindex, so even though the database wide "reindexer enable" is on, please do not do any reindexing for this field?

Would it work to toggle reindexer enable off while adding the fields, and then toggling it back on. What about new documents added during reindexer is off? (We don't have the luxury to stop writes at any given time.)

Ville
_______________________________________________
General mailing list
[email protected]
http://developer.marklogic.com/mailman/listinfo/general

Reply via email to