nsIndexAttribute: attribute:index1,index2
Parameter | Description |
Entry DN | cn=task_name, cn=index, cn=tasks, cn=config |
|
|
Valid Values | Any attribute |
| The index type, which can be: |
| pres (presence), |
| eq (equality), |
| approx (approximate), and |
| sub (substring) |
|
|
Default Value |
|
|
|
Syntax | |
|
|
Example | nsIndexAttribute: "cn:pres,eq" |
| nsIndexAttribute: "description:sub" |
|
|
nsIndexVLVAttribute This attribute gives the name of the target entry for a VLV index. A virtual list view is based on a browsing index entry (as described in the
Parameter | Description |
Entry DN | cn=task_name, cn=index, cn=tasks, cn=config |
|
|
Valid Values | Any attribute |
| The index type, which can be: |
| pres (presence), |
| eq (equality), |
| approx (approximate), and |
| sub (substring) |
|
|
Default Value |
|
|
|
Syntax | |
|
|
Example | nsIndexAttribute: "cn:pres,eq" |
| nsIndexAttribute: "description:sub" |
|
|
2.3.14.7 cn=schema reload task,cn=tasks,cn=config
The directory schema is loaded when the directory instance is started or restarted. Any changes to the directory schema, including adding custom schema elements, are not loaded automatically and available to the instance until the server is restarted or by initiating a schema reload task.
Custom schema changes can be reloaded dynamically, without having to restart the Directory Server instance. This is done by initiating a schema reload task through creating a new task entry under the cn=tasks entry.
The custom schema file can be located in any directory; if not specified with the “schemadir” attribute, the server reloads the schema from the default
2.3 Core server configuration attributes reference 109