honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

[DOCS] Remove collapsible examples (#59820) (#59857) 

Snippets are now visible without additional clicks.
This commit is contained in:
James Rodewig 2020-07-20 09:14:36 -04:00 committed by GitHub
parent e31ebc96f9
commit a160daa5d9
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 0 additions and 32 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/reference/search/request/from-size.asciidoc
View File

@ -9,9 +9,6 @@ and `from` parameters. The `size` parameter is the number of matching documents
to return. The `from` parameter is a zero-indexed offset from the beginning of to return. The `from` parameter is a zero-indexed offset from the beginning of
the complete result set that indicates the document you want to start with. the complete result set that indicates the document you want to start with.
.*Example*
[%collapsible]
====
The following search API request sets the `from` offset to `5`, meaning the The following search API request sets the `from` offset to `5`, meaning the
request offsets, or skips, the first five matching documents. request offsets, or skips, the first five matching documents.
@ -31,7 +28,6 @@ GET /_search
} }
} }
---- ----
====
By default, you cannot page through more than 10,000 documents using the `from` By default, you cannot page through more than 10,000 documents using the `from`
and `size` parameters. This limit is set using the and `size` parameters. This limit is set using the

20
docs/reference/search/run-a-search.asciidoc
View File

@ -30,9 +30,6 @@ You can use the search API's <<search-api-query-params-q,`q` query string
parameter>> to run a search in the request's URI. The `q` parameter only accepts parameter>> to run a search in the request's URI. The `q` parameter only accepts
queries written in Lucene's <<query-string-syntax,query string syntax>>. queries written in Lucene's <<query-string-syntax,query string syntax>>.
.*Example*
[%collapsible]
====
To get started, ingest or add some data to an {es} index. To get started, ingest or add some data to an {es} index.
The following <<docs-bulk,bulk API>> request adds some example user log data to The following <<docs-bulk,bulk API>> request adds some example user log data to
@ -99,7 +96,6 @@ the document that matched the query.
} }
---- ----
// TESTRESPONSE[s/"took": 2/"took": "$body.took"/] // TESTRESPONSE[s/"took": 2/"took": "$body.took"/]
====
[discrete] [discrete]
[[run-request-body-search]] [[run-request-body-search]]
@ -109,9 +105,6 @@ You can use the search API's <<request-body-search-query,`query` request
body parameter>> to provide a query as a JSON object, written in body parameter>> to provide a query as a JSON object, written in
<<query-dsl,Query DSL>>. <<query-dsl,Query DSL>>.
.*Example*
[%collapsible]
====
The following request body search uses the <<query-dsl-match-query,`match`>> The following request body search uses the <<query-dsl-match-query,`match`>>
query to match documents with a `message` value of `login successful`. Note the query to match documents with a `message` value of `login successful`. Note the
`match` query is specified as a JSON object in the `query` parameter. `match` query is specified as a JSON object in the `query` parameter.
@ -197,7 +190,6 @@ score>> that measures how well each document matches the query.
} }
---- ----
// TESTRESPONSE[s/"took": 1/"took": "$body.took"/] // TESTRESPONSE[s/"took": 1/"took": "$body.took"/]
====
[discrete] [discrete]
[[search-multiple-indices]] [[search-multiple-indices]]
@ -206,9 +198,6 @@ score>> that measures how well each document matches the query.
To search multiple data streams and indices, add them as comma-separated values To search multiple data streams and indices, add them as comma-separated values
in the search API request path. in the search API request path.
.*Example*
[%collapsible]
====
The following request searches the `user_logs_000001` and `user_logs_000002` The following request searches the `user_logs_000001` and `user_logs_000002`
indices. indices.
@ -225,14 +214,10 @@ GET /user_logs_000001,user_logs_000002/_search
---- ----
// TEST[continued] // TEST[continued]
// TEST[s/^/PUT user_logs_000002\n/] // TEST[s/^/PUT user_logs_000002\n/]
====
You can also search multiple data streams and indices using a wildcard (`*`) You can also search multiple data streams and indices using a wildcard (`*`)
pattern. pattern.
.*Example*
[%collapsible]
====
The following request targets the wildcard pattern `user_logs*`. The request The following request targets the wildcard pattern `user_logs*`. The request
searches any data streams or indices in the cluster that start with `user_logs`. searches any data streams or indices in the cluster that start with `user_logs`.
@ -248,14 +233,10 @@ GET /user_logs*/_search
} }
---- ----
// TEST[continued] // TEST[continued]
====
To search all data streams and indices in a cluster, omit the target from the To search all data streams and indices in a cluster, omit the target from the
request path. Alternatively, you can use `_all` or `*`. request path. Alternatively, you can use `_all` or `*`.
.*Example*
[%collapsible]
====
The following requests are equivalent and search all data streams and indices in the cluster. The following requests are equivalent and search all data streams and indices in the cluster.
[source,console] [source,console]
@ -286,7 +267,6 @@ GET /*/_search
} }
---- ----
// TEST[continued] // TEST[continued]
====
include::request/from-size.asciidoc[] include::request/from-size.asciidoc[]

8
docs/reference/search/search-fields.asciidoc
View File

@ -39,9 +39,6 @@ following sections:
You can use the `_source` parameter to select what fields of the source are You can use the `_source` parameter to select what fields of the source are
returned. This is called _source filtering_. returned. This is called _source filtering_.
.*Example*
[%collapsible]
====
The following search API request sets the `_source` request body parameter to The following search API request sets the `_source` request body parameter to
`false`. The document source is not included in the response. `false`. The document source is not included in the response.
@ -120,7 +117,6 @@ GET /_search
} }
} }
---- ----
====
[discrete] [discrete]
@ -139,9 +135,6 @@ Doc values are stored for supported fields by default. However, doc values are
not supported for <<text,`text`>> or not supported for <<text,`text`>> or
{plugins}/mapper-annotated-text-usage.html[`text_annotated`] fields. {plugins}/mapper-annotated-text-usage.html[`text_annotated`] fields.
.*Example*
[%collapsible]
====
The following search request uses the `docvalue_fields` parameter to The following search request uses the `docvalue_fields` parameter to
retrieve doc values for the following fields: retrieve doc values for the following fields:
@ -176,7 +169,6 @@ GET /_search
<<mapping-date-format,date `format`>>. <<number,Numeric fields>> support a <<mapping-date-format,date `format`>>. <<number,Numeric fields>> support a
https://docs.oracle.com/javase/8/docs/api/java/text/DecimalFormat.html[DecimalFormat https://docs.oracle.com/javase/8/docs/api/java/text/DecimalFormat.html[DecimalFormat
pattern]. Other field data types do not support the `format` parameter. pattern]. Other field data types do not support the `format` parameter.
====
TIP: You cannot use the `docvalue_fields` parameter to retrieve doc values for TIP: You cannot use the `docvalue_fields` parameter to retrieve doc values for
nested objects. If you specify a nested object, the search returns an empty nested objects. If you specify a nested object, the search returns an empty