Package com.arangodb.entity
Class InvertedIndexField
java.lang.Object
com.arangodb.entity.InvertedIndexField
- Since:
- ArangoDB 3.10
- Author:
- Michele Rastelli
-
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionboolean
features
(AnalyzerFeature... features) getCache()
getName()
int
hashCode()
includeAllFields
(Boolean includeAllFields) nested
(InvertedIndexField... nested) searchField
(Boolean searchField) trackListPositions
(Boolean trackListPositions)
-
Constructor Details
-
InvertedIndexField
public InvertedIndexField()
-
-
Method Details
-
getName
-
name
- Parameters:
name
- An attribute path. The . character denotes sub-attributes.- Returns:
- this
-
getAnalyzer
-
analyzer
- Parameters:
analyzer
- The name of an Analyzer to use for this field. Default: the value defined by the top-level analyzer option, or if not set, the default identity Analyzer.- Returns:
- this
-
getIncludeAllFields
-
includeAllFields
- Parameters:
includeAllFields
- This option only applies if you use the inverted index in a search-alias Views. If set to true, then all sub-attributes of this field are indexed, excluding any sub-attributes that are configured separately by other elements in the fields array (and their sub-attributes). The analyzer and features properties apply to the sub-attributes. If set to false, then sub-attributes are ignored. The default value is defined by the top-level includeAllFields option, or false if not set.- Returns:
- this
-
getSearchField
-
searchField
- Parameters:
searchField
- This option only applies if you use the inverted index in a search-alias Views. You can set the option to true to get the same behavior as with arangosearch Views regarding the indexing of array values for this field. If enabled, both, array and primitive values (strings, numbers, etc.) are accepted. Every element of an array is indexed according to the trackListPositions option. If set to false, it depends on the attribute path. If it explicitly expand an array ([*]), then the elements are indexed separately. Otherwise, the array is indexed as a whole, but only geopoint and aql Analyzers accept array inputs. You cannot use an array expansion if searchField is enabled. Default: the value defined by the top-level searchField option, or false if not set.- Returns:
- this
-
getTrackListPositions
-
trackListPositions
- Parameters:
trackListPositions
- This option only applies if you use the inverted index in a search-alias Views. If set to true, then track the value position in arrays for array values. For example, when querying a document like { attr: [ "valueX", "valueY", "valueZ" ] }, you need to specify the array element, e.g. doc.attr[1] == "valueY". If set to false, all values in an array are treated as equal alternatives. You don’t specify an array element in queries, e.g. doc.attr == "valueY", and all elements are searched for a match. Default: the value defined by the top-level trackListPositions option, or false if not set.- Returns:
- this
-
getCache
-
cache
- Parameters:
cache
- Enable this option to always cache the field normalization values in memory for this specific field. This can improve the performance of scoring and ranking queries. Otherwise, these values are memory-mapped and it is up to the operating system to load them from disk into memory and to evict them from memory. (Enterprise Edition only)- Returns:
- this
- Since:
- ArangoDB 3.10.2
-
getFeatures
-
features
- Parameters:
features
- A list of Analyzer features to use for this field. They define what features are enabled for the analyzer.- Returns:
- this
-
getNested
-
nested
- Parameters:
nested
- Index the specified sub-objects that are stored in an array. Other than with the fields property, the values get indexed in a way that lets you query for co-occurring values. For example, you can search the sub-objects and all the conditions need to be met by a single sub-object instead of across all of them. This property is available in the Enterprise Edition only.- Returns:
- this
-
equals
-
hashCode
public int hashCode()
-