There are several HPE IDOL Server configuration parameters that define how HPE IDOL Server stores and processes data at a very low level. To prevent inconsistencies in the index and potential failures, some configuration parameters are permanent, and can be set only in a clean server, or require a complete reindex of your content. Other settings might apply to new content, but require a reindex for existing content.
For more information about the configuration parameters, refer to the IDOL Server Reference.
You can use the Config page in the Monitor section of IDOL Admin to view and validate your configuration file.
The following settings can be set only for a clean HPE IDOL Server. If you want to change the setting, you must initialize the index (run a DREINITIAL
index action, or use the Initialize IDOL Content feature on the Service Control tab of the Console page in the Control section of IDOL Admin).
RepositoryStorage
XMLFullStructure
DiskHash
(only applies when RepositoryStorage=False
)
TermSize
AdvancedSearch
AdvancedPlus
AdvancedCaseSearch
IndexCompression
CaseSensitiveFieldNames
SplitNumbers
Soundex
The following settings can be changed, but require a full reindex of all your data:
AlphanumericTermChunkSize
NumericTermChunkSize
NodeTableStoreACLsInRefTable
UnstemmedTermTree
UnstemmedTrackFields
[LanguageType]
configuration parameters
The following configuration parameters can be changed in the index, but any change only applies to new content. If you want to apply the change to existing data, you must reindex the content.
NodeTableStoreContent
IndexNumbersMaxValue
IndexNumbersNMaxLength
[Synonym]
configuration parameters
UnstemmedMinDocOccs
[SectionBreaking]
configuration parameters
DateFormatCSVs
DisallowAgentWeights
DocumentDelimitersCSVs
FieldPositionGap
MaxIndexOccurrencesPerDocument
MaxIndexOccurrencesPerField
For the [FieldProcessing]
and associated [Properties]
configuration parameters, you can change some parameters at any time, but others require reindexing or further steps to apply your changes.
You can change the HighlightType
, PrintType
, and MemcachedType
properties at any time for existing content without regenerating or reindexing.
For some field properties, you can regenerate the data index without reindexing your content. This process allows you to change the configuration after indexing. However, the regeneration process can be slow. When you make a configuration change, you can run the ValidateConfig
action to determine whether you need to regenerate any indexes. This applies to the following field properties and related configuration parameters:
BitFieldType
CountType
MatchType
NumericType
ParametricType
SecurityType
SortType
ParametricNumericMapping
CaseSensitiveMatchValues
CaseSensitiveParametricValues
When you want to apply a property to a new field, you can sometimes update the field configuration. In this case, the new configuration applies to new documents. However, HPE recommends regenerating or reindexing to ensure that field properties are applied consistently across your index, and always when changing or adding a property for an existing field.
|