Should we create a dedicated index field for this property, or use a multi-field encoding? A dedicated field is recommended if more than a few percent of objects have this property. Internal: if there is no dedicated field, we store in the "metas" field and index using prefixed-words.

Storing this meta in a dynamical property decreases index's memory footprint and improve index's commit time. Faceting and sorting performances will be impacted (slower).

Allows users to search for matches in this property using a prefix. For example, to search for "API" in the title of a document, enter the search query <pre>title:API</pre>

Displays the meta in the hit content of search results. If the property doesn't have a dedicated field, the value will be CSV-encoded in the 'metas' field.

Stores this property in RAM. Use this option if you need to:

Only the "retrievable" part of the property is stored in RAM.

Creates a navigation facet from the property values.

Makes refinements on this facet disjunctive ("checkboxes") rather than exclusive (select one).

If there is no value for this property in the document, use this default value.

Maps these metas (as a comma-separated list) to this index or facet field. Usable only for properties having a dedicated field, a facet, or are searchable without prefix.

The arity of the property (zero_or_one, one, many) {@code enum(zero_or_one, one, many)}

Property name

Optional comment to explain property use.

Defines how the text is processed and indexed (tokenization, normalization and indexing-time semantic processing). This value must refer to a valid !SemanticType object in the DataModel.

Allows users to search for matches in this property without using a prefix, by mapping the values to the generic "text" index field, as invisible text. For example, to search for "API" in a document, enter the search query <pre>API</pre>

Search-time query expansion config to use for this property. This follows the 'QEC' format specification.

Is there a controlled and limited set of values for this property? Enumerated properties are indexed using a specific "Value" field, which stores entire values in an optimized way. Thus, performing faceting on this kind of field is faster than on a category field. It is not possible to perform any semantic processing on value fields.

User-defined tags for this property. This can be used for example to implement 6W faceting of the data model.

Labels for the internationalization of this property's name