The reindexer will not reindex all documents every time there is a change. It will try to minimize the work to only those fragments that need the indexing.
However, when you know you need an index, why not add it before you add the new content? Even though the reindexer will minimize the work, it will still need to reinsert the fragment, and there will likely be merges too. The reindexer would still need to be enabled to reindex the existing 12 GB (if such reindexing is needed) but the data you load after adding the index would be indexed when it is added to the db. On Mon, May 11, 2015 at 9:58 AM, Shashidhar Rao <[email protected]> wrote: > Hi Christopher, > > I wanted to check for this condition. > > Already 500GB loaded and re-indexing done. > > Now I first load 12 GB of data which has different elements without creating > any range index. When loading is finished I enable the reindexer enable to > false. Now I create the range indexes for these newly loaded data. > > Now I enable the reindexer enable to true and click ok. On the Admin status > page, when re-index starts it always gives out the number of fragments and > the time to complete. > > My question was on the number of fragments in this situation. Will the > number of fragments will be 4 million plus newly loaded data number or just > the newly added fragments say in this case .2 million. > > Thanks > > > > _______________________________________________ > General mailing list > [email protected] > Manage your subscription at: > http://developer.marklogic.com/mailman/listinfo/general > _______________________________________________ General mailing list [email protected] Manage your subscription at: http://developer.marklogic.com/mailman/listinfo/general
