;
};
extendSearchSortType?: string[];
}
```
### host
\
The host of the Elasticsearch server. May also be specified in `clientOptions.node`.
### port
\
The port of the Elasticsearch server. May also be specified in `clientOptions.node`.
### connectionAttempts
\
Maximum amount of attempts made to connect to the ElasticSearch server on startup.
### connectionAttemptInterval
\
Interval in milliseconds between attempts to connect to the ElasticSearch server on startup.
### clientOptions
\
Options to pass directly to the
[Elasticsearch Node.js client](https://www.elastic.co/guide/en/elasticsearch/client/javascript-api/current/index.html). For example, to
set authentication or other more advanced options.
Note that if the `node` or `nodes` option is specified, it will override the values provided in the `host` and `port` options.
### indexPrefix
\
Prefix for the indices created by the plugin.
### indexSettings
\
[These options](https://www.elastic.co/guide/en/elasticsearch/reference/7.x/index-modules.html#index-modules-settings)
are directly passed to index settings. To apply some settings indices will be recreated.
*Example*
```ts
// Configuring an English stemmer
indexSettings: {
analysis: {
analyzer: {
custom_analyzer: {
tokenizer: 'standard',
filter: [
'lowercase',
'english_stemmer'
]
}
},
filter : {
english_stemmer : {
type : 'stemmer',
name : 'english'
}
}
}
},
```
A more complete example can be found in the discussion thread
[How to make elastic plugin to search by substring with stemming](https://github.com/vendurehq/vendure/discussions/1066).
### indexMappingProperties
\
This option allow to redefine or define new properties in mapping. More about elastic
[mapping](https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping.html)
After changing this option indices will be recreated.
*Example*
```ts
// Configuring custom analyzer for the `productName` field.
indexMappingProperties: {
productName: {
type: 'text',
analyzer:'custom_analyzer',
fields: {
keyword: {
type: 'keyword',
ignore_above: 256,
}
}
}
}
```
To reference a field defined by `customProductMappings` or `customProductVariantMappings`, you will
need to prefix the name with `'product-'` or `'variant-'` respectively, e.g.:
*Example*
```ts
customProductMappings: {
variantCount: {
graphQlType: 'Int!',
valueFn: (product, variants) => variants.length,
},
},
indexMappingProperties: {
'product-variantCount': {
type: 'integer',
}
}
```
### reindexProductsChunkSize
\
Products limit chunk size for each loop iteration when indexing products.
### reindexBulkOperationSizeLimit
\
Index operations are performed in bulk, with each bulk operation containing a number of individual
index operations. This option sets the maximum number of operations in the memory buffer before a
bulk operation is executed.
### searchConfig
\SearchConfig`} />
Configuration of the internal Elasticsearch query.
### customProductMappings
\; }`} />
Custom mappings may be defined which will add the defined data to the
Elasticsearch index and expose that data via the SearchResult GraphQL type,
adding a new `customMappings`, `customProductMappings` & `customProductVariantMappings` fields.
The `graphQlType` property may be one of `String`, `Int`, `Float`, `Boolean`, `ID` or list
versions thereof (`[String!]` etc) and can be appended with a `!` to indicate non-nullable fields.
The `public` (default = `true`) property is used to reveal or hide the property in the GraphQL API schema.
If this property is set to `false` it's not accessible in the `customMappings` field but it's still getting
parsed to the elasticsearch index.
This config option defines custom mappings which are accessible when the "groupByProduct" or "groupBySKU"
input options is set to `true` (Do not set both to true at the same time). In addition, custom variant mappings can be accessed by using
the `customProductVariantMappings` field, which is always available.
*Example*
```ts
customProductMappings: {
variantCount: {
graphQlType: 'Int!',
valueFn: (product, variants) => variants.length,
},
reviewRating: {
graphQlType: 'Float',
public: true,
valueFn: product => (product.customFields as any).reviewRating,
},
priority: {
graphQlType: 'Int!',
public: false,
valueFn: product => (product.customFields as any).priority,
},
}
```
*Example*
```graphql
query SearchProducts($input: SearchInput!) {
search(input: $input) {
totalItems
items {
productId
productName
customProductMappings {
variantCount
reviewRating
}
customMappings {
...on CustomProductMappings {
variantCount
reviewRating
}
}
}
}
}
```
### customProductVariantMappings
\; }`} />
This config option defines custom mappings which are accessible when the "groupByProduct" and "groupBySKU"
input options are both set to `false`. In addition, custom product mappings can be accessed by using
the `customProductMappings` field, which is always available.
*Example*
```graphql
query SearchProducts($input: SearchInput!) {
search(input: $input) {
totalItems
items {
productId
productName
customProductVariantMappings {
weight
}
customMappings {
...on CustomProductVariantMappings {
weight
}
}
}
}
}
```
### bufferUpdates
\
If set to `true`, updates to Products, ProductVariants and Collections will not immediately
trigger an update to the search index. Instead, all these changes will be buffered and will
only be run via a call to the `runPendingSearchIndexUpdates` mutation in the Admin API.
This is very useful for installations with a large number of ProductVariants and/or
Collections, as the buffering allows better control over when these expensive jobs are run,
and also performs optimizations to minimize the amount of work that needs to be performed by
the worker.
### hydrateProductRelations
\>`} default={`[]`} since="1.3.0" />
Additional product relations that will be fetched from DB while reindexing. This can be used
in combination with `customProductMappings` to ensure that the required relations are joined
before the `product` object is passed to the `valueFn`.
*Example*
```ts
{
hydrateProductRelations: ['assets.asset'],
customProductMappings: {
assetPreviews: {
graphQlType: '[String!]',
// Here we can be sure that the `product.assets` array is populated
// with an Asset object
valueFn: (product) => product.assets.map(a => a.asset.preview),
}
}
}
```
### hydrateProductVariantRelations
\>`} default={`[]`} since="1.3.0" />
Additional variant relations that will be fetched from DB while reindexing. See
`hydrateProductRelations` for more explanation and a usage example.
### extendSearchInputType
\; }`} default={`{}`} since="1.3.0" />
Allows the `SearchInput` type to be extended with new input fields. This allows arbitrary
data to be passed in, which can then be used e.g. in the `mapQuery()` function or
custom `scriptFields` functions.
*Example*
```ts
extendSearchInputType: {
longitude: 'Float',
latitude: 'Float',
radius: 'Float',
}
```
This allows the search query to include these new fields:
*Example*
```graphql
query {
search(input: {
longitude: 101.7117,
latitude: 3.1584,
radius: 50.00
}) {
items {
productName
}
}
}
```
### extendSearchSortType
\
Adds a list of sort parameters. This is mostly important to make the
correct sort order values available inside `input` parameter of the `mapSort` option.
*Example*
```ts
extendSearchSortType: ["distance"]
```
will extend the `SearchResultSortParameter` input type like this:
*Example*
```GraphQl
extend input SearchResultSortParameter {
distance: SortOrder
}
```
Configuration options for the internal Elasticsearch query which is generated when performing a search.
```ts title="Signature"
interface SearchConfig {
facetValueMaxSize?: number;
collectionMaxSize?: number;
totalItemsMaxSize?: number | boolean;
multiMatchType?: 'best_fields' | 'most_fields' | 'cross_fields' | 'phrase' | 'phrase_prefix' | 'bool_prefix';
boostFields?: BoostFieldsConfig;
priceRangeBucketInterval?: number;
mapQuery?: (
query: any,
input: ElasticSearchInput,
searchConfig: DeepRequired,
channelId: ID,
enabledOnly: boolean,
ctx: RequestContext,
) => any;
scriptFields?: { [fieldName: string]: CustomScriptMapping<[ElasticSearchInput]> };
mapSort?: (sort: ElasticSearchSortInput, input: ElasticSearchInput) => ElasticSearchSortInput;
}
```
### facetValueMaxSize
\
The maximum number of FacetValues to return from the search query. Internally, this
value sets the "size" property of an Elasticsearch aggregation.
### collectionMaxSize
\
The maximum number of Collections to return from the search query. Internally, this
value sets the "size" property of an Elasticsearch aggregation.
### totalItemsMaxSize
\
The maximum number of totalItems to return from the search query. Internally, this
value sets the "track\_total\_hits" property of an Elasticsearch query.
If this parameter is set to "True", accurate count of totalItems will be returned.
If this parameter is set to "False", totalItems will be returned as 0.
If this parameter is set to integer, accurate count of totalItems will be returned not bigger than integer.
### multiMatchType
\
Defines the
[multi match type](https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-multi-match-query.html#multi-match-types)
used when matching against a search term.
### boostFields
\
BoostFieldsConfig`} />
Set custom boost values for particular fields when matching against a search term.
### priceRangeBucketInterval
\
The interval used to group search results into buckets according to price range. For example, setting this to
`2000` will group into buckets every $20.00:
```json
{
"data": {
"search": {
"totalItems": 32,
"priceRange": {
"buckets": [
{
"to": 2000,
"count": 21
},
{
"to": 4000,
"count": 7
},
{
"to": 6000,
"count": 3
},
{
"to": 12000,
"count": 1
}
]
}
}
}
}
```
### mapQuery
\SearchConfig>, channelId: ID, enabledOnly: boolean, ctx: RequestContext, ) => any`} />
This config option allows the the modification of the whole (already built) search query. This allows
for e.g. wildcard / fuzzy searches on the index.
*Example*
```ts
mapQuery: (query, input, searchConfig, channelId, enabledOnly, ctx) => {
if (query.bool.must) {
delete query.bool.must;
}
query.bool.should = [
{
query_string: {
query: "*" + term + "*",
fields: [
`productName^${searchConfig.boostFields.productName}`,
`productVariantName^${searchConfig.boostFields.productVariantName}`,
]
}
},
{
multi_match: {
query: term,
type: searchConfig.multiMatchType,
fields: [
`description^${searchConfig.boostFields.description}`,
`sku^${searchConfig.boostFields.sku}`,
],
},
},
];
return query;
}
```
### scriptFields
\ }`} since="1.3.0" />
Sets `script_fields` inside the elasticsearch body which allows returning a script evaluation for each hit.
The script field definition consists of three properties:
* `graphQlType`: This is the type that will be returned when this script field is queried
via the GraphQL API. It may be one of `String`, `Int`, `Float`, `Boolean`, `ID` or list
versions thereof (`[String!]` etc) and can be appended with a `!` to indicate non-nullable fields.
* `context`: determines whether this script field is available when grouping by product. Can be
`product`, `variant` or `both`.
* `scriptFn`: This is the function to run on each hit. Should return an object with a `script` property,
as covered in the
[Elasticsearch script fields docs](https://www.elastic.co/guide/en/elasticsearch/reference/7.15/search-fields.html#script-fields)
*Example*
```ts
extendSearchInputType: {
latitude: 'Float',
longitude: 'Float',
},
indexMappingProperties: {
// The `product-location` field corresponds to the `location` customProductMapping
// defined below. Here we specify that it would be index as a `geo_point` type,
// which will allow us to perform geo-spacial calculations on it in our script field.
'product-location': {
type: 'geo_point', // contains function arcDistance
},
},
customProductMappings: {
location: {
graphQlType: 'String',
valueFn: (product: Product) => {
// Assume that the Product entity has this customField defined
const custom = product.customFields.location;
return `${custom.latitude},${custom.longitude}`;
},
}
},
searchConfig: {
scriptFields: {
distance: {
graphQlType: 'Float!',
// Run this script only when grouping results by product
context: 'product',
scriptFn: (input) => {
// The SearchInput was extended with latitude and longitude
// via the `extendSearchInputType` option above.
const lat = input.latitude;
const lon = input.longitude;
return {
script: `doc['product-location'].arcDistance(${lat}, ${lon})`,
}
}
}
}
}
```
### mapSort
\ ElasticSearchSortInput`} default={`{}`} since="1.4.0" />
Allows extending the `sort` input of the elasticsearch body as covered in
[Elasticsearch sort docs](https://www.elastic.co/guide/en/elasticsearch/reference/current/sort-search-results.html)
The `sort` input parameter contains the ElasticSearchSortInput generated for the default sort parameters "name" and "price".
If neither of those are applied it will be empty.
*Example*
```ts
mapSort: (sort, input) => {
// Assuming `extendSearchSortType: ["priority"]`
// Assuming priority is never undefined
const { priority } = input.sort;
return [
...sort,
{
// The `product-priority` field corresponds to the `priority` customProductMapping
// Depending on the index type, this field might require a
// more detailed input (example: 'productName.keyword')
["product-priority"]: {
order: priority === SortOrder.ASC ? 'asc' : 'desc'
}
}
];
}
```
A more generic example would be a sort function based on a product location like this:
*Example*
```ts
extendSearchInputType: {
latitude: 'Float',
longitude: 'Float',
},
extendSearchSortType: ["distance"],
indexMappingProperties: {
// The `product-location` field corresponds to the `location` customProductMapping
// defined below. Here we specify that it would be index as a `geo_point` type,
// which will allow us to perform geo-spacial calculations on it in our script field.
'product-location': {
type: 'geo_point',
},
},
customProductMappings: {
location: {
graphQlType: 'String',
valueFn: (product: Product) => {
// Assume that the Product entity has this customField defined
const custom = product.customFields.location;
return `${custom.latitude},${custom.longitude}`;
},
}
},
searchConfig: {
mapSort: (sort, input) => {
// Assuming distance is never undefined
const { distance } = input.sort;
return [
...sort,
{
["_geo_distance"]: {
"product-location": [
input.longitude,
input.latitude
],
order: distance === SortOrder.ASC ? 'asc' : 'desc',
unit: "km"
}
}
];
}
}
```
### productName
\
Defines the boost factor for the productName field.
### productVariantName
\
Defines the boost factor for the productVariantName field.
### description
\
Defines the boost factor for the description field.
### sku
\
Defines the boost factor for the sku field.