Global Configuration Record (GCR)

Definition

The Global Configuration Record is created automatically in the Oracle Endeca Server, and can be modified if needed. This information persists if you restart the Oracle Endeca Server data store.

The Global Configuration Record controls the following areas of the Oracle Endeca Server data store configuration:

Area of global configuration	What you can do...
Wildcard search enablement	Specify whether wildcard search should be enabled or disabled for value search in the Oracle Endeca Server. By default, it is disabled.
Search characters	List which characters you want to identify as search characters to the Oracle Endeca Server.
Merge policy	Optionally, change the policy that the Oracle Endeca Server uses in the background to merge its generations of data files. The default policy – `balanced` – is recommended, and is optimized for best performance.
Spelling correction settings	Control which words are eligible for the spelling dictionary. To do this, for each attribute assignment on a record and for each managed attribute value, you specify the following parameters: Minimum word occurrence Minimum word length Maximum word length Note: If you change the spelling settings in the Global Configuration Record, you must run the `admin?op=updateaspell` command in order for them to take effect.

Modifying the settings in the Global Configuration Record

To change the Global Configuration Record settings, use the Data Ingest Web Service, or Integrator.

Required attributes of the GCR

The Global Configuration Record has required attributes, but it cannot have arbitrary, user-defined attributes.

The required attributes are:

Attribute	Type	Description
`mdex-config_Key`	`String`	The only value for this attribute is `global`. This attribute is unique and single-assign.
`mdex-config_EnableValueSearchWildcard`	`Boolean`	If set to `true`, then wildcard search is enabled for value search. If set to `false`, then wildcard search is disabled. The default value is `false.`
`mdex-config_MergePolicy`	`String`	The allowed values are `balanced` or `aggressive`. The default is `balanced`.
`mdex-config_SearchChars`	`String`	The characters to use as search characters in the Oracle Endeca Server. The allowed values are strings that are listed sequentially and are not separated by commas or spaces. Each string is a search character.
`mdex-config_SystemRecordVersion`	`String`	The version of the system records in the Oracle Endeca Server. This attribute is used by the Oracle Endeca Server and should not be modified.
`mdex-config_SpellingRecordMinWordOccur`	`Int`	The minimum number of times a word must occur in a standard attribute value (record assignment on a standard attribute, in a key value pair) for it to affect the configuration for spelling correction. The default value is 4.
`mdex-config_SpellingRecordMinWordLength`	`Int`	The minimum number of characters that a word can contain in a standard attribute value for it to affect the configuration for spelling correction. The default value is 3.
`mdex-config_SpellingRecordMaxWordLength`	`Int`	The maximum number of characters that a word can contain in a standard attribute value for it to affect the spelling correction. The default value is 16.
`mdex-config_SpellingDValMinWordOccur`	`Int`	The minimum number of times a word must occur in a managed attribute value for it to affect the spelling correction. The default value is 1.
`mdex-config_SpellingDValMinWordLength`	`Int`	The minimum number of characters that a word must contain in a managed attribute value for it to affect the spelling correction. The default value is 3.
`mdex-config_SpellingDValMaxWordLength`	`Int`	The maximum number of characters that a word may contain in a managed attribute value for it to affect the spelling correction. The default value is 16.

Validating the GCR settings

During record updates, the Oracle Endeca Server validation process validates the configuration of the Global Configuration Record, and returns errors if its requirements are not met.

The requirements are as follows:

The mdex-config_Key attribute must be unique and single-assign. The value must be global.
The Global Configuration Record must contain valid allowable values for all of its attributes. None of its attributes can be omitted.
The Global Configuration Record cannot have any arbitrary, user-defined attributes.