Each of the Regenerate*Index configuration parameters rebuilds one or more of the IDOL data indexes for optimized fields (MatchType fields, NumericType fields, and so on) from the textual document field values held in the server. You can do this to reconcile the index or indexes with the document data if:
validation of one or more indexes has failed, indicating that the data is no longer in a consistent state
you have changed the server [FieldProcessing] or [Properties] configuration to:
make an existing field an optimized type.
remove an optimized field.
set or clear the NumericIntegerOnly setting for a numeric type field.
In these cases, the alternative to regenerating is to reindex all documents. Regenerating is generally significantly faster, as only the requested indexes regenerate.
In addition, you might need to regenerate fields if you have indexed ReferenceMemoryMappedType fields out of order, with some child fields indexed before their parents. You regenerate these fields either by using the DREREGENERATE index action, or by using the Regenerate feature on the Service Control tab of the Console page in the Control section of IDOL Admin. For more information on the DREREGENERATE action, refer to the IDOL Server Reference.
You can regenerate indexes for the following field types:
BitFieldType (RegenerateBitFieldIndex)
CountType (RegenerateCountIndex)
MatchType (RegenerateMatchIndex)
NumericType (RegenerateNumericIndex)
NumericDateType (RegenerateNumericDateIndex)
ParametricType and ParametricRangeType (RegenerateParametricIndex)
SortType (RegenerateSortFieldIndex)
Additionally, you can regenerate the following indexes if validation fails:
Security index (RegenerateSecIndex)
Unstemmed indexWildcard searches (and some advanced search techniques) use the index of unstemmed terms. This index contains all the exact terms that occur in documents. (RegenerateUnstemmedIndex)
To regenerate a data index
Stop IDOL Server.
Make any required changes to the [FieldProcessing] or [Properties] configuration sections.
Set the required Regenerate*Index settings to True in the [Server] section of the configuration file.
Restart IDOL Server.
At start-up, IDOL runs through all stored documents, and loads the values of any fields to regenerate from disk. It inserts these values into new index structures.
When the process is complete, IDOL Server deletes any existing indexes and replaces them with the newly built versions.
After the server has started, remember to remove or turn off any Regenerate*Index settings in the configuration file if you do not want the server to regenerate the indexes every time it starts.
Regenerating the index requires a server restart. In addition, regenerating indexes also results in an increased startup time.
Regenerating the unstemmed index is an intensive process and generally takes significantly longer than regenerating other indexes (though it is still faster than reindexing the data).
Consider the following points when you are using the regeneration options:
Regeneration requires a server restart. The server is not available for further indexing or querying until the regeneration process is complete.
The regeneration affects all indexes of the requested type. For example, if you add a field as NumericType in the configuration file, setting RegenerateNumericIndex to True regenerates all existing numeric indexes, as well as creating one for the new numeric field.
The original document content must be stored in IDOL Server.
If you have set NodeTableStoreContent to False, you can only regenerate a given index if all the fields in question are also explicitly configured as StoredType.
|
|