NOTE: You are looking at documentation for an older release. For the latest information, see the current release documentation.

› ›

indices.forcemerge

edit

IMPORTANT: This documentation is no longer updated. Refer to Elastic's version policy and the latest documentation.

indices.forcemerge

edit

client.indices.forcemerge({
  index: string | string[],
  flush: boolean,
  ignore_unavailable: boolean,
  allow_no_indices: boolean,
  expand_wildcards: 'open' | 'closed' | 'none' | 'all',
  max_num_segments: number,
  only_expunge_deletes: boolean
})

Reference

`index`	`string \| string[]` - A comma-separated list of index names; use `_all` or empty string to perform the operation on all indices
`flush`	`boolean` - Specify whether the index should be flushed after performing the operation (default: true)
`ignore_unavailable` or `ignoreUnavailable`	`boolean` - Whether specified concrete indices should be ignored when unavailable (missing or closed)
`allow_no_indices` or `allowNoIndices`	`boolean` - Whether to ignore if a wildcard indices expression resolves into no concrete indices. (This includes `_all` string or when no indices have been specified)
`expand_wildcards` or `expandWildcards`	`'open' \| 'closed' \| 'none' \| 'all'` - Whether to expand wildcard expression to concrete indices that are open, closed or both. Default: `open`
`max_num_segments` or `maxNumSegments`	`number` - The number of segments the index should be merged into (default: dynamic)
`only_expunge_deletes` or `onlyExpungeDeletes`	`boolean` - Specify whether the operation should only expunge deleted documents

« indices.flushSynced indices.get »