LinkProperties Properties

A list of analyzers, by name as defined via the Analyzers feature, that should be applied to values of processed document attributes.

Fields that should be processed at each level of the document. Each key specifies the document attribute/field to be processed. Note that the value of includeAllFields is also consulted when selecting fields to be processed. Each value specifies the Link properties directives to be used when processing the specified field, an empty/null value denotes inheritance of all (except fields) directives from the current level.

If set to true, then no exclusive lock is used on the source collection during View index creation, so that it remains basically available. This option can be set when adding links. It does not get persisted as it is not a View property, but only a one-off option.

If set to true, then process all document attributes. Otherwise, only consider attributes mentioned in fields. Attributes not explicitly specified in fields will be processed with default link properties, i.e. null. Using includeAllFields for a lot of attributes in combination with complex Analyzers may significantly slow down the indexing process.

Controls how the view should keep track of the attribute values. Valid values are NoStoreValue and NoStoreValue. Not to be confused with StoredValues, which stores attribute values in the View index.

If set to true, then for array values track the value position in arrays. E.g., when querying for the input { attr: [ "valueX", "valueY", "valueZ" ] }, the user must specify: doc.attr[1] == "valueY". Otherwise, all values in an array are treated as equal alternatives. E.g., when querying for the input { attr: [ "valueX", "valueY", "valueZ" ] }, the user must specify: doc.attr == "valueY"