| Info |
|---|
Valid as of Datafari 4.6 |
It can be useful sometimes There are scenarios that require to force a job to reindex all of its documents into MCF. When we do this the documents are still present into Solr and not deleted. Indeed, for a filer job, normally MCF compares the Note that doing this does not delete the documents from the index, so users can still search them.
As an example of such scenarios, take a filer job: normally MCF compares a document that it is stored in its internal database before fetching the content of the file. If they are the same, the document is not fetched because it is identical.For other jobs like a web job for example, each time that we start a job MCF does a full indexation because it can not . But if we modify the job itself, for instance if we add a metadata, this has no impact on the documents themselves, and therefore MCF will not update the index.
Some jobs do not do such comparisons of document (for instance the web job, that does a full indexation every time, because it cannot compare a webpage to crawl with a webpage already crawled so this ), and for such jobs this MCF reindexing process is not useful.
For other sourcestypes of jobs, if you are not sure unsure about the behavior of the crawler, you can apply this process.But if we do a modification into the job like adding a metadata, the change would not be visible because the document is not reindexed.
The process is in 2 steps :
...