- Elasticsearch Guide: other versions:
- What is Elasticsearch?
- What’s new in 7.11
- Getting started with Elasticsearch
- Set up Elasticsearch
- Installing Elasticsearch
- Configuring Elasticsearch
- Setting JVM options
- Secure settings
- Auditing settings
- Circuit breaker settings
- Cluster-level shard allocation and routing settings
- Cross-cluster replication settings
- Discovery and cluster formation settings
- Field data cache settings
- HTTP
- Index lifecycle management settings
- Index management settings
- Index recovery settings
- Indexing buffer settings
- License settings
- Local gateway settings
- Logging
- Machine learning settings
- Monitoring settings
- Node
- Network settings
- Node query cache settings
- Search settings
- Security settings
- Shard request cache settings
- Snapshot lifecycle management settings
- Transforms settings
- Transport
- Thread pools
- Watcher settings
- Advanced configuration settings
- Important Elasticsearch configuration
- Important System Configuration
- Bootstrap Checks
- Heap size check
- File descriptor check
- Memory lock check
- Maximum number of threads check
- Max file size check
- Maximum size virtual memory check
- Maximum map count check
- Client JVM check
- Use serial collector check
- System call filter check
- OnError and OnOutOfMemoryError checks
- Early-access check
- G1GC check
- All permission check
- Discovery configuration check
- Bootstrap Checks for X-Pack
- Starting Elasticsearch
- Stopping Elasticsearch
- Discovery and cluster formation
- Add and remove nodes in your cluster
- Full-cluster restart and rolling restart
- Remote clusters
- Set up X-Pack
- Configuring X-Pack Java Clients
- Plugins
- Upgrade Elasticsearch
- Index modules
- Mapping
- Text analysis
- Overview
- Concepts
- Configure text analysis
- Built-in analyzer reference
- Tokenizer reference
- Token filter reference
- Apostrophe
- ASCII folding
- CJK bigram
- CJK width
- Classic
- Common grams
- Conditional
- Decimal digit
- Delimited payload
- Dictionary decompounder
- Edge n-gram
- Elision
- Fingerprint
- Flatten graph
- Hunspell
- Hyphenation decompounder
- Keep types
- Keep words
- Keyword marker
- Keyword repeat
- KStem
- Length
- Limit token count
- Lowercase
- MinHash
- Multiplexer
- N-gram
- Normalization
- Pattern capture
- Pattern replace
- Phonetic
- Porter stem
- Predicate script
- Remove duplicates
- Reverse
- Shingle
- Snowball
- Stemmer
- Stemmer override
- Stop
- Synonym
- Synonym graph
- Trim
- Truncate
- Unique
- Uppercase
- Word delimiter
- Word delimiter graph
- Character filters reference
- Normalizers
- Index templates
- Data streams
- Ingest pipelines
- Search your data
- Query DSL
- Aggregations
- Bucket aggregations
- Adjacency matrix
- Auto-interval date histogram
- Children
- Composite
- Date histogram
- Date range
- Diversified sampler
- Filter
- Filters
- Geo-distance
- Geohash grid
- Geotile grid
- Global
- Histogram
- IP range
- Missing
- Nested
- Parent
- Range
- Rare terms
- Reverse nested
- Sampler
- Significant terms
- Significant text
- Terms
- Variable width histogram
- Subtleties of bucketing range fields
- Metrics aggregations
- Pipeline aggregations
- Bucket aggregations
- EQL
- SQL access
- Overview
- Getting Started with SQL
- Conventions and Terminology
- Security
- SQL REST API
- SQL Translate API
- SQL CLI
- SQL JDBC
- SQL ODBC
- SQL Client Applications
- SQL Language
- Functions and Operators
- Comparison Operators
- Logical Operators
- Math Operators
- Cast Operators
- LIKE and RLIKE Operators
- Aggregate Functions
- Grouping Functions
- Date/Time and Interval Functions and Operators
- Full-Text Search Functions
- Mathematical Functions
- String Functions
- Type Conversion Functions
- Geo Functions
- Conditional Functions And Expressions
- System Functions
- Reserved keywords
- SQL Limitations
- Scripting
- Data management
- ILM: Manage the index lifecycle
- Overview
- Concepts
- Automate rollover
- Customize built-in ILM policies
- Index lifecycle actions
- Configure a lifecycle policy
- Migrate index allocation filters to node roles
- Resolve lifecycle policy execution errors
- Start and stop index lifecycle management
- Manage existing indices
- Skip rollover
- Restore a managed data stream or index
- Autoscaling
- Monitor a cluster
- Frozen indices
- Roll up or transform your data
- Set up a cluster for high availability
- Snapshot and restore
- Secure a cluster
- Overview
- Configuring security
- User authentication
- Built-in users
- Internal users
- Token-based authentication services
- Realms
- Realm chains
- Active Directory user authentication
- File-based user authentication
- LDAP user authentication
- Native user authentication
- OpenID Connect authentication
- PKI user authentication
- SAML authentication
- Kerberos authentication
- Integrating with other authentication systems
- Enabling anonymous access
- Controlling the user cache
- Configuring SAML single-sign-on on the Elastic Stack
- Configuring single sign-on to the Elastic Stack using OpenID Connect
- User authorization
- Built-in roles
- Defining roles
- Granting access to Stack Management features
- Security privileges
- Document level security
- Field level security
- Granting privileges for data streams and index aliases
- Mapping users and groups to roles
- Setting up field and document level security
- Submitting requests on behalf of other users
- Configuring authorization delegation
- Customizing roles and authorization
- Enabling audit logging
- Encrypting communications
- Restricting connections with IP filtering
- Cross cluster search, clients, and integrations
- Tutorial: Getting started with security
- Tutorial: Encrypting communications
- Troubleshooting
- Some settings are not returned via the nodes settings API
- Authorization exceptions
- Users command fails due to extra arguments
- Users are frequently locked out of Active Directory
- Certificate verification fails for curl on Mac
- SSLHandshakeException causes connections to fail
- Common SSL/TLS exceptions
- Common Kerberos exceptions
- Common SAML issues
- Internal Server Error in Kibana
- Setup-passwords command fails due to connection failure
- Failures due to relocation of the configuration files
- Limitations
- Watch for cluster and index events
- Command line tools
- How To
- Glossary of terms
- REST APIs
- API conventions
- Autoscaling APIs
- Compact and aligned text (CAT) APIs
- cat aliases
- cat allocation
- cat anomaly detectors
- cat count
- cat data frame analytics
- cat datafeeds
- cat fielddata
- cat health
- cat indices
- cat master
- cat nodeattrs
- cat nodes
- cat pending tasks
- cat plugins
- cat recovery
- cat repositories
- cat segments
- cat shards
- cat snapshots
- cat task management
- cat templates
- cat thread pool
- cat trained model
- cat transforms
- Cluster APIs
- Cluster allocation explain
- Cluster get settings
- Cluster health
- Cluster reroute
- Cluster state
- Cluster stats
- Cluster update settings
- Nodes feature usage
- Nodes hot threads
- Nodes info
- Nodes reload secure settings
- Nodes stats
- Pending cluster tasks
- Remote cluster info
- Task management
- Voting configuration exclusions
- Cross-cluster replication APIs
- Data stream APIs
- Document APIs
- Enrich APIs
- Graph explore API
- Index APIs
- Analyze
- Bulk index alias
- Clear cache
- Clone index
- Close index
- Create index
- Create or update component template
- Create or update index alias
- Create or update index template
- Create or update index template (legacy)
- Delete component template
- Delete dangling index
- Delete index
- Delete index alias
- Delete index template
- Delete index template (legacy)
- Flush
- Force merge
- Freeze index
- Get component template
- Get field mapping
- Get index
- Get index alias
- Get index settings
- Get index template
- Get index template (legacy)
- Get mapping
- Import dangling index
- Index alias exists
- Index exists
- Index recovery
- Index segments
- Index shard stores
- Index stats
- Index template exists (legacy)
- List dangling indices
- Open index
- Refresh
- Resolve index
- Rollover index
- Shrink index
- Simulate index
- Simulate template
- Split index
- Synced flush
- Type exists
- Unfreeze index
- Update index settings
- Update mapping
- Index lifecycle management APIs
- Ingest APIs
- Info API
- Licensing APIs
- Machine learning anomaly detection APIs
- Add events to calendar
- Add jobs to calendar
- Close jobs
- Create jobs
- Create calendars
- Create datafeeds
- Create filters
- Delete calendars
- Delete datafeeds
- Delete events from calendar
- Delete filters
- Delete forecasts
- Delete jobs
- Delete jobs from calendar
- Delete model snapshots
- Delete expired data
- Estimate model memory
- Find file structure
- Flush jobs
- Forecast jobs
- Get buckets
- Get calendars
- Get categories
- Get datafeeds
- Get datafeed statistics
- Get influencers
- Get jobs
- Get job statistics
- Get machine learning info
- Get model snapshots
- Get overall buckets
- Get scheduled events
- Get filters
- Get records
- Open jobs
- Post data to jobs
- Preview datafeeds
- Revert model snapshots
- Set upgrade mode
- Start datafeeds
- Stop datafeeds
- Update datafeeds
- Update filters
- Update jobs
- Update model snapshots
- Upgrade model snapshots
- Machine learning data frame analytics APIs
- Create data frame analytics jobs
- Create trained models
- Update data frame analytics jobs
- Delete data frame analytics jobs
- Delete trained models
- Evaluate data frame analytics
- Explain data frame analytics
- Get data frame analytics jobs
- Get data frame analytics jobs stats
- Get trained models
- Get trained models stats
- Start data frame analytics jobs
- Stop data frame analytics jobs
- Migration APIs
- Reload search analyzers API
- Repositories metering APIs
- Rollup APIs
- Search APIs
- Searchable snapshots APIs
- Security APIs
- Authenticate
- Change passwords
- Clear cache
- Clear roles cache
- Clear privileges cache
- Clear API key cache
- Create API keys
- Create or update application privileges
- Create or update role mappings
- Create or update roles
- Create or update users
- Delegate PKI authentication
- Delete application privileges
- Delete role mappings
- Delete roles
- Delete users
- Disable users
- Enable users
- Get API key information
- Get application privileges
- Get builtin privileges
- Get role mappings
- Get roles
- Get token
- Get users
- Grant API keys
- Has privileges
- Invalidate API key
- Invalidate token
- OpenID Connect prepare authentication
- OpenID Connect authenticate
- OpenID Connect logout
- SAML prepare authentication
- SAML authenticate
- SAML logout
- SAML invalidate
- SAML service provider metadata
- SSL certificate
- Snapshot and restore APIs
- Snapshot lifecycle management APIs
- Transform APIs
- Usage API
- Watcher APIs
- Definitions
- Migration guide
- Release notes
- Elasticsearch version 7.11.2
- Elasticsearch version 7.11.1
- Elasticsearch version 7.11.0
- Elasticsearch version 7.10.2
- Elasticsearch version 7.10.1
- Elasticsearch version 7.10.0
- Elasticsearch version 7.9.3
- Elasticsearch version 7.9.2
- Elasticsearch version 7.9.1
- Elasticsearch version 7.9.0
- Elasticsearch version 7.8.1
- Elasticsearch version 7.8.0
- Elasticsearch version 7.7.1
- Elasticsearch version 7.7.0
- Elasticsearch version 7.6.2
- Elasticsearch version 7.6.1
- Elasticsearch version 7.6.0
- Elasticsearch version 7.5.2
- Elasticsearch version 7.5.1
- Elasticsearch version 7.5.0
- Elasticsearch version 7.4.2
- Elasticsearch version 7.4.1
- Elasticsearch version 7.4.0
- Elasticsearch version 7.3.2
- Elasticsearch version 7.3.1
- Elasticsearch version 7.3.0
- Elasticsearch version 7.2.1
- Elasticsearch version 7.2.0
- Elasticsearch version 7.1.1
- Elasticsearch version 7.1.0
- Elasticsearch version 7.0.0
- Elasticsearch version 7.0.0-rc2
- Elasticsearch version 7.0.0-rc1
- Elasticsearch version 7.0.0-beta1
- Elasticsearch version 7.0.0-alpha2
- Elasticsearch version 7.0.0-alpha1
- Dependencies and versions
Search API
editSearch API
editReturns search hits that match the query defined in the request.
GET /my-index-000001/_search
Prerequisites
edit-
If the Elasticsearch security features are enabled, you must have the
read
index privilege for the target data stream, index, or index alias. For cross-cluster search, see Cross cluster search and security.To search a point in time (PIT) for an index alias, you must have the
read
index privilege for the alias’s concrete indices.
Description
editAllows you to execute a search query and get back search hits that match the
query. You can provide search queries using the q
query string parameter or request body.
Path parameters
edit-
<target>
-
(Optional, string) Comma-separated list of data streams, indices, and index aliases to search. Wildcard (
*
) expressions are supported.To search all data streams and indices in a cluster, omit this parameter or use
_all
or*
.
Query parameters
editSeveral options for this API can be specified using a query parameter or a request body parameter. If both parameters are specified, only the query parameter is used.
-
allow_no_indices
-
(Optional, Boolean) If
false
, the request returns an error if any wildcard expression, index alias, or_all
value targets only missing or closed indices. This behavior applies even if the request targets other open indices. For example, a request targetingfoo*,bar*
returns an error if an index starts withfoo
but no index starts withbar
.Defaults to
true
.
-
allow_partial_search_results
-
(Optional, Boolean) If
true
, returns partial results if there are request timeouts or shard failures. Iffalse
, returns an error with no partial results. Defaults totrue
.To override the default for this field, set the
search.default_allow_partial_results
cluster setting tofalse
. -
analyzer
-
(Optional, string) Analyzer to use for the query string.
This parameter can only be used when the
q
query string parameter is specified. -
analyze_wildcard
-
(Optional, Boolean) If
true
, wildcard and prefix queries are analyzed. Defaults tofalse
.This parameter can only be used when the
q
query string parameter is specified. -
batched_reduce_size
-
(Optional, integer) The number of shard results that should be reduced at once
on the coordinating node. This value should be used as a protection mechanism
to reduce the memory overhead per search request if the potential number of
shards in the request can be large. Defaults to
512
.
-
ccs_minimize_roundtrips
-
(Optional, Boolean) If
true
, network round-trips between the coordinating node and the remote clusters are minimized when executing cross-cluster search (CCS) requests. See How cross-cluster search handles network delays. Defaults totrue
. -
default_operator
-
(Optional, string) The default operator for query string query: AND or OR. Defaults to
OR
.This parameter can only be used when the
q
query string parameter is specified. -
df
-
(Optional, string) Field to use as default where no field prefix is given in the query string.
This parameter can only be used when the
q
query string parameter is specified. -
docvalue_fields
- (Optional, string) A comma-separated list of fields to return as the docvalue representation of a field for each hit.
-
expand_wildcards
-
(Optional, string) Type of index that wildcard expressions can match. If the request can target data streams, this argument determines whether wildcard expressions match hidden data streams. Supports comma-separated values, such as
open,hidden
. Valid values are:-
all
- Match any data stream or index, including hidden ones.
-
open
- Match open, non-hidden indices. Also matches any non-hidden data stream.
-
closed
- Match closed, non-hidden indices. Also matches any non-hidden data stream. Data streams cannot be closed.
-
hidden
-
Match hidden data streams and hidden indices. Must be combined with
open
,closed
, or both. -
none
- Wildcard expressions are not accepted.
Defaults to
open
. -
-
explain
-
(Optional, Boolean) If
true
, returns detailed information about score computation as part of a hit. Defaults tofalse
. -
from
-
(Optional, integer) Starting document offset. Defaults to
0
.By default, you cannot page through more than 10,000 hits using the
from
andsize
parameters. To page through more hits, use thesearch_after
parameter. -
ignore_throttled
-
(Optional, Boolean) If
true
, concrete, expanded or aliased indices will be ignored when frozen. Defaults totrue
. -
ignore_unavailable
-
(Optional, Boolean) If
false
, the request returns an error if it targets a missing or closed index. Defaults tofalse
. -
lenient
-
(Optional, Boolean) If
true
, format-based query failures (such as providing text to a numeric field) in the query string will be ignored. Defaults tofalse
.This parameter can only be used when the
q
query string parameter is specified. -
max_concurrent_shard_requests
-
(Optional, integer) Defines the number of concurrent shard requests per node
this search executes concurrently. This value should be used to limit the
impact of the search on the cluster in order to limit the number of concurrent
shard requests. Defaults to
5
. -
pre_filter_shard_size
-
(Optional, integer) Defines a threshold that enforces a pre-filter roundtrip to prefilter search shards based on query rewriting if the number of shards the search request expands to exceeds the threshold. This filter roundtrip can limit the number of shards significantly if for instance a shard can not match any documents based on its rewrite method ie. if date filters are mandatory to match but the shard bounds and the query are disjoint. When unspecified, the pre-filter phase is executed if any of these conditions is met:
-
The request targets more than
128
shards. - The request targets one or more read-only index.
- The primary sort of the query targets an indexed field.
-
The request targets more than
-
preference
-
(Optional, string) Nodes and shards used for the search. By default, Elasticsearch selects from eligible nodes and shards using adaptive replica selection, accounting for allocation awareness.
Valid values for
preference
-
_only_local
- Run the search only on shards on the local node.
-
_local
- If possible, run the search on shards on the local node. If not, select shards using the default method.
-
_only_nodes:<node-id>,<node-id>
- Run the search on only the specified nodes IDs. If suitable shards exist on more than one selected nodes, use shards on those nodes using the default method. If none of the specified nodes are available, select shards from any available node using the default method.
-
_prefer_nodes:<node-id>,<node-id>
- If possible, run the search on the specified nodes IDs. If not, select shards using the default method.
-
_shards:<shard>,<shard>
-
Run the search only on the specified shards. You can combine this value with
other
preference
values, excluding<custom-string>
. However, the_shards
value must come first. For example:_shards:2,3|_local
. -
<custom-string>
-
Any string that does not start with
_
. If the cluster state and selected shards do not change, searches using the same<custom-string>
value are routed to the same shards in the same order.
-
-
q
-
(Optional, string) Query in the Lucene query string syntax.
You can use the
q
parameter to run a query parameter search. Query parameter searches do not support the full Elasticsearch Query DSL but are handy for testing.The
q
parameter overrides thequery
parameter in the request body. If both parameters are specified, documents matching thequery
request body parameter are not returned. -
request_cache
-
(Optional, Boolean) If
true
, the caching of search results is enabled for requests wheresize
is0
. See Shard request cache settings. Defaults to index level settings. -
rest_total_hits_as_int
-
(Optional, Boolean) Indicates whether hits.total should be rendered as an
integer or an object in the rest search response. Defaults to
false
. -
routing
- (Optional, string) Target the specified primary shard.
-
scroll
-
(Optional, time value) Period to retain the search context for scrolling. See Scroll search results.
By default, this value cannot exceed
1d
(24 hours). You can change this limit using thesearch.max_keep_alive
cluster-level setting.
-
search_type
-
(Optional, string) How distributed term frequencies are calculated for relevance scoring.
Valid values for
search_type
-
query_then_fetch
- (Default) Distributed term frequencies are calculated locally for each shard running the search. We recommend this option for faster searches with potentially less accurate scoring.
-
-
seq_no_primary_term
-
(Optional, Boolean) If
true
, returns sequence number and primary term of the last modification of each hit. See Optimistic concurrency control. -
size
-
(Optional, integer) Defines the number of hits to return. Defaults to
10
.By default, you cannot page through more than 10,000 hits using the
from
andsize
parameters. To page through more hits, use thesearch_after
parameter. -
sort
- (Optional, string) A comma-separated list of <field>:<direction> pairs.
-
_source
-
(Optional) Indicates which source fields are returned for matching documents. These fields are returned in the
hits._source
property of the search response. Defaults totrue
.Valid values for
_source
-
true
- (Boolean) The entire document source is returned.
-
false
- (Boolean) The document source is not returned.
-
<string>
-
(string)
Comma-separated list of source fields to return.
Wildcard (
*
) patterns are supported.
-
-
_source_excludes
-
(Optional, string) A comma-separated list of source fields to exclude from the response.
You can also use this parameter to exclude fields from the subset specified in
_source_includes
query parameter.If the
_source
parameter isfalse
, this parameter is ignored. -
_source_includes
-
(Optional, string) A comma-separated list of source fields to include in the response.
If this parameter is specified, only these source fields are returned. You can exclude fields from this subset using the
_source_excludes
query parameter.If the
_source
parameter isfalse
, this parameter is ignored. -
stats
-
(Optional, string) Specific
tag
of the request for logging and statistical purposes. -
stored_fields
-
(Optional, string) A comma-separated list of stored fields to return as part of a hit. If no fields are specified, no stored fields are included in the response.
If this field is specified, the
_source
parameter defaults tofalse
. You can pass_source: true
to return both source fields and stored fields in the search response. -
suggest_field
- (Optional, string) Specifies which field to use for suggestions.
-
suggest_mode
-
(Optional, string) Specifies the suggest mode. Defaults to
missing
. Available options:-
always
-
missing
-
popular
This parameter can only be used when the
suggest_field
andsuggest_text
query string parameters are specified. -
-
suggest_size
-
(Optional, integer) Number of suggestions to return.
This parameter can only be used when the
suggest_field
andsuggest_text
query string parameters are specified. -
suggest_text
-
(Optional, string) The source text for which the suggestions should be returned.
This parameter can only be used when the
suggest_field
query string parameter is specified. -
terminate_after
-
(Optional, integer) The maximum number of documents to collect for each shard, upon reaching which the query execution will terminate early.
Defaults to
0
, which does not terminate query execution early. -
timeout
- (Optional, time units) Specifies the period of time to wait for a response. If no response is received before the timeout expires, the request fails and returns an error. Defaults to no timeout.
-
track_scores
-
(Optional, Boolean) If
true
, calculate and return document scores, even if the scores are not used for sorting. Defaults tofalse
. -
track_total_hits
-
(Optional, integer or Boolean) Number of hits matching the query to count accurately. Defaults to
10000
.If
true
, the exact number of hits is returned at the cost of some performance. Iffalse
, the response does not include the total number of hits matching the query. -
typed_keys
-
(Optional, Boolean) If
true
, aggregation and suggester names are be prefixed by their respective types in the response. Defaults totrue
. -
version
-
(Optional, Boolean)
If
true
, returns document version as part of a hit. Defaults tofalse
.
Request body
edit-
docvalue_fields
-
(Optional, array of strings and objects) Array of wildcard (
*
) patterns. The request returns doc values for field names matching these patterns in thehits.fields
property of the response.You can specify items in the array as a string or object. See Doc value fields.
Properties of
docvalue_fields
objects-
field
- (Required, string) Wildcard pattern. The request returns doc values for field names matching this pattern.
-
format
-
(Optional, string) Format in which the doc values are returned.
For date fields, you can specify a date date
format
. For numeric fields fields, you can specify a DecimalFormat pattern.For other field data types, this parameter is not supported.
-
-
fields
-
(Optional, array of strings and objects) Array of wildcard (
*
) patterns. The request returns values for field names matching these patterns in thehits.fields
property of the response.You can specify items in the array as a string or object. See Fields for more details.
Properties of
fields
objects-
field
- (Required, string) Wildcard pattern. The request returns values for field names matching this pattern.
-
format
-
(Optional, string) Format in which the values are returned.
The date fields
date
anddate_nanos
accept a date format. Spatial fields accept eithergeojson
for GeoJSON (the default) orwkt
for Well Known Text.For other field data types, this parameter is not supported.
-
-
explain
-
(Optional, Boolean) If
true
, returns detailed information about score computation as part of a hit. Defaults tofalse
. -
from
-
(Optional, integer) Starting document offset. Defaults to
0
.By default, you cannot page through more than 10,000 hits using the
from
andsize
parameters. To page through more hits, use thesearch_after
parameter. -
indices_boost
-
(Optional, array of objects) Boosts the
_score
of documents from specified indices.Properties of
indices_boost
objects-
<index>: <boost-value>
-
(Required, float)
<index>
is the name of the index or index alias. Wildcard (*
) expressions are supported.<boost-value>
is the factor by which scores are multiplied.A boost value greater than
1.0
increases the score. A boost value between0
and1.0
decreases the score.
-
-
min_score
-
(Optional, float)
Minimum
_score
for matching documents. Documents with a lower_score
are not included in the search results. -
pit
-
(Optional, object) Limits the search to a point in time (PIT). If you provide a
pit
, you cannot specify a<target>
in the request path.Properties of
pit
-
id
-
(Required*, string)
ID for the PIT to search. If you provide a
pit
object, this parameter is required. -
keep_alive
- (Optional, time value) Period of time used to extend the life of the PIT.
-
-
query
- (Optional, query object) Defines the search definition using the Query DSL.
-
runtime_mappings
-
(Optional, object) Defines a runtime field in the search request that exist only as part of the query. Fields defined in the search request take precedence over fields defined with the same name in the index mappings.
Properties of
runtime_mappings
objects-
type
-
(Required, string) Data type of the object, which can be any of the following:
-
boolean
-
date
-
double
-
geo_point
-
ip
-
keyword
-
long
-
-
script
-
(Optional, string) Painless script that is executed at query time. The script has access to the entire context of a document, including the original
_source
and any mapped fields plus their values.Your script must include
emit
to return calculated values. For example:"script": { "source": "emit(doc['@timestamp'].value.dayOfWeekEnum.getDisplayName(TextStyle.FULL, Locale.ROOT))" }
-
-
seq_no_primary_term
-
(Optional, Boolean) If
true
, returns sequence number and primary term of the last modification of each hit. See Optimistic concurrency control. -
size
-
(Optional, integer) The number of hits to return. Defaults to
10
.By default, you cannot page through more than 10,000 hits using the
from
andsize
parameters. To page through more hits, use thesearch_after
parameter. -
_source
-
(Optional) Indicates which source fields are returned for matching documents. These fields are returned in the
hits._source
property of the search response. Defaults totrue
.Valid values for
_source
-
true
- (Boolean) The entire document source is returned.
-
false
- (Boolean) The document source is not returned.
-
<wildcard_pattern>
-
(string or array of strings)
Wildcard (
*
) pattern or array of patterns containing source fields to return. -
<object>
-
(object) Object containing a list of source fields to include or exclude.
Properties for
<object>
-
excludes
-
(string or array of strings) Wildcard (
*
) pattern or array of patterns containing source fields to exclude from the response.You can also use this property to exclude fields from the subset specified in
includes
property. -
includes
-
(string or array of strings) Wildcard (
*
) pattern or array of patterns containing source fields to return.If this property is specified, only these source fields are returned. You can exclude fields from this subset using the
excludes
property.
-
-
-
stats
- (Optional, array of strings) Stats groups to associate with the search. Each group maintains a statistics aggregation for its associated searches. You can retrieve these stats using the indices stats API.
-
terminate_after
-
(Optional, integer) The maximum number of documents to collect for each shard, upon reaching which the query execution will terminate early.
Defaults to
0
, which does not terminate query execution early. -
timeout
- (Optional, time units) Specifies the period of time to wait for a response. If no response is received before the timeout expires, the request fails and returns an error. Defaults to no timeout.
Response body
edit-
_scroll_id
-
(string) Identifier for the search and its search context.
You can use this scroll ID with the scroll API to retrieve the next batch of search results for the request. See Scroll search results.
This parameter is only returned if the
scroll
query parameter is specified in the request. -
took
-
(integer) Milliseconds it took Elasticsearch to execute the request.
This value is calculated by measuring the time elapsed between receipt of a request on the coordinating node and the time at which the coordinating node is ready to send the response.
Took time includes:
- Communication time between the coordinating node and data nodes
-
Time the request spends in the
search
thread pool, queued for execution - Actual execution time
Took time does not include:
- Time needed to send the request to Elasticsearch
- Time needed to serialize the JSON response
- Time needed to send the response to a client
-
timed_out
-
(Boolean)
If
true
, the request timed out before completion; returned results may be partial or empty. -
_shards
-
(object) Contains a count of shards used for the request.
Properties of
_shards
-
total
- (integer) Total number of shards that require querying, including unallocated shards.
-
successful
- (integer) Number of shards that executed the request successfully.
-
skipped
- (integer) Number of shards that skipped the request because a lightweight check helped realize that no documents could possibly match on this shard. This typically happens when a search request includes a range filter and the shard only has values that fall outside of that range.
-
failed
-
(integer)
Number of shards that failed to execute the request. Note that shards
that are not allocated will be considered neither successful nor failed.
Having
failed+successful
less thantotal
is thus an indication that some of the shards were not allocated.
-
-
hits
-
(object) Contains returned documents and metadata.
Properties of
hits
-
total
-
(object) Metadata about the number of returned documents.
Properties of
total
-
value
- (integer) Total number of returned documents.
-
relation
-
(string) Indicates whether the number of returned documents in the
value
parameter is accurate or a lower bound.Values of
relation
:-
eq
- Accurate
-
gte
- Lower bound, including returned documents
-
-
-
max_score
-
(float) Highest returned document
_score
.This value is
null
for requests that do not sort by_score
.
-
hits
-
(array of objects) Array of returned document objects.
Properties of
hits
objects-
_index
- (string) Name of the index containing the returned document.
-
_type
- [6.0.0] Deprecated in 6.0.0. Mapping types are deprecated and will be removed in 8.0. See Removal of mapping types. (string) Mapping type of the returned document.
-
_id
- (string) Unique identifier for the returned document. This ID is only unique within the returned index.
-
_score
- (float) Positive 32-bit floating point number used to determine the relevance of the returned document.
-
_source
-
(object) Original JSON body passed for the document at index time.
You can use the
_source
parameter to exclude this property from the response or specify which source fields to return. -
fields
-
(object) Contains field values for the documents. These fields must be specified in the request using one or more of the following request parameters:
This property is returned only if one or more of these parameters are set.
Properties of
fields
-
<field>
- (array) Key is the field name. Value is the value for the field.
-
-
-
Examples
editGET /my-index-000001/_search { "query": { "term": { "user.id": "kimchy" } } }
The API returns the following response:
{ "took": 5, "timed_out": false, "_shards": { "total": 1, "successful": 1, "skipped": 0, "failed": 0 }, "hits": { "total": { "value": 1, "relation": "eq" }, "max_score": 1.3862942, "hits": [ { "_index": "my-index-000001", "_type" : "_doc", "_id": "0", "_score": 1.3862942, "_source": { "@timestamp": "2099-11-15T14:12:12", "http": { "request": { "method": "get" }, "response": { "status_code": 200, "bytes": 1070000 }, "version": "1.1" }, "source": { "ip": "127.0.0.1" }, "message": "GET /search HTTP/1.1 200 1070000", "user": { "id": "kimchy" } } } ] } }
On this page