Commit Graph

754 Commits

Author SHA1 Message Date
Gonçalo Montalvão Marques c4bd4d3cbf
Fix typo in geo-distance-query doc (#89148) 2022-08-08 09:59:47 +02:00
Abdon Pijpelink 0eca582326
[DOCS] Remove camel case variations (#88650)
* [DOCS] Remove camel case variations. Closes #73417

* [DOCS] Switch to sentence casing in titles
2022-07-20 17:06:34 +02:00
Mayya Sharipova 1ae209335d
Undeprecate function_score query (#87807)
We had a plan to deprecate function_score query with
script_score query, but ran into a roadblock of missing
functionality to combine scores from different
functions (particularly "first" script_score).
Wee have several proposal to address this missing
functionality:
 [scripted_boolean](https://github.com/elastic/elasticsearch/issues/27588#issuecomment-444887726)
 [compound_query](https://github.com/elastic/elasticsearch/issues/51967)
 [first_query](https://github.com/elastic/elasticsearch/issues/52482)

But for now, we decided not to deprecate function_score query,
and hence we need to remove any mention that we are deprecating it.

Relates to #42811
Closes #71934
2022-06-17 11:04:26 -04:00
Luca Cavanna fe327c6e1a
[DOCS] Clarify index_prefix in prefix query docs (#87450)
The current docs mention that Elasticsearch indexes prefixes between 2 and 5 characters in a separate field. 2 and 5 are default values, and the size of the prefixes indexed depend on the configuration settings.
2022-06-14 14:32:37 +02:00
Ignacio Vera e6b4097fc8
new geo_grid query to be used with geogrid aggregations (#86596)
Query that allows users to define a query where the input is the key of the bucket and it will match the 
documents inside that bucket.
2022-05-23 11:38:07 +02:00
Craig Taverner 5f7ea792ac
Soft-deprecation of point/geo_point formats (#86835)
* Soft-deprecation of point/geo_point formats

Since GeoJSON and WKT are now common formats for all three types:
  geo_shape, geo_point and point
We decided to soft-deprecate the other point formats by ordering:
* GeoJSON (object with keys `type` and `coordinates`)
* WKT `POINT(x y)`
* Object with keys `lat` and `lon` (or `x` and `y` for point)
* Array [lon,lat]
* String `"lat,lon"` (or `"x,y"` in point)
* String with geohash (only in `geo_point`)

The geohash is last because it is only in one field type.
The string version is second last because it is the most controversial
being the only version to reverse the coordinate order from all other
formats (for geo_point only, since the coordinates are not reversed
in point).

In addition we replaced many examples in both documentation and tests
to prioritize WKT over the plain string format.

Many remaining examples of array format or object with keys still exist
and could be replaced by, for example, GeoJSON, if we feel the need.

* Incorrect quote position
2022-05-17 23:46:43 +02:00
Nik Everett de5ca3cfaa
fixed typo (#84694) (#84726)
Co-authored-by: Mustafa Balila (rootsofnull) <hitsugayatoshiro899@gmail.com>
2022-03-07 14:30:51 -05:00
James Rodewig 1fe2b0d866
[DOCS] Fix percolate query headings (#83988)
Fixes the heading levels for the percolate query doc so the on-page TOC displays correctly.
2022-02-15 15:56:04 -05:00
James Rodewig c1aba1e109
[DOCS] Move tip for percolate query example (#83972)
Moves a tip for the percolate query to the beginning of the example.
2022-02-15 15:24:33 -05:00
James Rodewig b552d5cb0e
[DOCS] Re-add network traffic para to `term` query (#83047)
Re-adds a paragraph about minimizing network traffic for a terms lookup.

This paragraph was erroneously removed as part of https://github.com/elastic/elasticsearch/pull/42889.
2022-01-25 10:27:10 -05:00
James Rodewig e53ecc3f43
[DOCS] Document missing `flag` values for `regexp` query (#82265)
Documents the `EMPTY` and `NONE` `flag` values for the `regexp` query.

Also documents the `""` (empty string) value, which is an alias for `ALL`.

Closes #81978.
2022-01-18 14:15:29 -05:00
jenish jain 13e9a605b8
[DOCS] Fix `track_total_hits` xref (#82739) 2022-01-18 12:43:17 -05:00
James Rodewig 0a3f6acadd
[DOCS] Clarify `nested` query behavior for `must_not` clauses (#82727)
Closes #81052.
2022-01-18 10:14:26 -05:00
James Rodewig f5f76ff1ca
[DOCS] Note that `default_field` support wildcards (#81127)
Changes:

* Notes that the query string query's `default_field` and `fields` parameters support wildcards.
* Adds an xref to the `index.query.default_field` docs to the `default_field` parameter.
2022-01-04 08:26:13 -05:00
James Rodewig dd1ed30731
[DOCS] Fix `combined_fields` query ref in `multi_match` query docs (#81456)
The current `multi_match` docs contain an erroneous reference to the `combined_fields` query. This updates the reference to reference the correct query.

Relates to https://github.com/elastic/elasticsearch/pull/76893
2021-12-07 16:47:44 -05:00
James Rodewig f56a0f4b66
[DOCS] Remove `testenv` annotations from doc snippet tests (#80023)
Removes `testenv` annotations and related code. These annotations originally let you skip x-pack snippet tests in the docs. However, that's no longer possible.

Relates to #79309, #31619
2021-11-05 18:38:50 -04:00
James Rodewig 0333d89f6e
[DOCS] Add `wildcard` parameter to `wildcard` query docs (#79722)
Changes:

* Documents the `wildcard` parameter for the `wildcard` query. This parameter is an alias for the `value` parameter.
* Reorders the parameters alphabetically.

Closes #79711
2021-10-26 12:35:11 -04:00
Alexander Reelsen 19d12f19f5
[DOCS] Add script note to nested query docs (#77431)
As the script has only access to the nested document, this should be
documented.

Co-authored-by: James Rodewig <40268737+jrodewig@users.noreply.github.com>
2021-10-05 10:32:20 -04:00
James Rodewig e729c3f543
[DOCS] Clarify geoshape orientation docs (#75888)
Adds additional information about how Elasticsearch uses polygon orientation. Elasticsearch only uses a polygon's orientation to determine if it crosses the international dateline. If so, Elasticsearch splits the polygon at the dateline.

Closes #74891
2021-09-08 11:10:03 -04:00
Adam Locke 1056c857ee
[DOCS] Update combined fields wording (#76893)
* [DOCS] Update combined fields wording

* Clarifications from review feedback
2021-08-26 13:16:55 -04:00
James Rodewig 22a6c1f0d3
[DOCS] Add search xref tip to `query_string` docs (#76728)
Adds a tip containing a cross-reference to the "Search your data" docs.
This is the preferred starting point for ES search.
2021-08-20 08:44:20 -04:00
Paweł Krześniak d2a6c1627f
[DOCS] Fix typo in parent-child example request (#76646) 2021-08-18 08:59:36 -04:00
James Rodewig 8eaf4043e4
[DOCS] Terms lookup doesn't support remote indices (#76371)
Changes:
* Notes that you can't use cross-cluster search to run a terms lookup on a remote index.
* Removes a redundant sentence noting `_source` is enabled by default.

Closes #61364.
2021-08-12 08:33:10 -04:00
James Rodewig fc0ac1923d
[DOCS] Correct spelling for geo terms (#76028)
Changes:
* Use "geopoint" when not referring to the literal field type
* Use "geoshape" when not referring to the literal field type or query type
* Use "GeoJSON" consistently
2021-08-03 09:55:48 -04:00
David Harsha ed7a65e053
Allow specifying index in pinned queries (#74873)
The current `ids` option doesn't allow pinning a specific document in a
single index when searching over multiple indices. This introduces a
`documents` option, which is an array of `_id` and `_index`
fields to allow index-specific pins.

Closes https://github.com/elastic/elasticsearch/issues/67855.
2021-07-27 15:55:07 +03:00
Adrien Grand feb6620d14
`indices.query.bool.max_clause_count` now limits all query clauses (#75297)
In the upcoming Lucene 9 release, `indices.query.bool.max_clause_count` is
going to apply to the entire query tree rather than per `bool` query. In order
to avoid breaks, the limit has been bumped from 1024 to 4096.

The semantics will effectively change when we upgrade to Lucene 9, this PR
is only about agreeing on a migration strategy and documenting this change.

To avoid further breaks, I am leaning towards keeping the current setting name
even though it contains `bool`. I believe that it still makes sense given that
`bool` queries are typically the main contributors to high numbers of clauses.

Co-authored-by: James Rodewig <40268737+jrodewig@users.noreply.github.com>
2021-07-21 12:16:30 +02:00
André Pessanha bb37e09d92
Rename field_masking_span to span_field_masking (#74718)
`field_masking_span` is the only span query that does not begin with
`span_`.  This commit deprecates the existing name and adds a new
name `span_field_masking` to better fit with the other queries.
2021-07-09 08:56:38 +01:00
James Rodewig d4ed43c5a4
[DOCS] Remove deprecated `geo_shape` parameters (#74519)
* Removes docs and references for the following `geo_shape` mapping parameters:
  * `tree`
  * `tree_levels`
  * `strategy`
  * `distance_error_pct`
* Updates a related breaking change.

Relates to #70850
2021-06-29 08:52:05 -04:00
James Rodewig 139eabad2d
[DOCS] Query strings are normalized for fuzzy (`~`) operator (#73921)
Notes that `fuzzy` queries made using the query string query's `~`
operator are normalized.

Closes #73299
2021-06-28 13:13:41 -04:00
Ignacio Vera d7ef5b6d21
Remove bounding box query type parameter (#74536)
The parameter has been deprecates in 7.14 as it is a no-op.
2021-06-28 07:37:04 +02:00
Ignacio Vera 28b4982df4
Deprecate Bounding box query type parameter (#74493)
This parameter has no effect on the query execution.
2021-06-24 07:34:57 +02:00
Mayya Sharipova f8215e752c
Add doc on rank_feature(s) negative score impact (#71795)
Add a warning about consequences of negative score impact
for documents that don't have values for rank_feature(s)
fields.

Related to #69994
2021-04-20 06:56:05 -04:00
Julie Tibshirani 318bf14126
Introduce `combined_fields` query (#71213)
This PR introduces a new query called `combined_fields` for searching multiple
text fields. It takes a term-centric view, first analyzing the query string
into individual terms, then searching for each term any of the fields as though
they were one combined field. It is based on Lucene's `CombinedFieldQuery`,
which takes a principled approach to scoring based on the BM25F formula.

This query provides an alternative to the `cross_fields` `multi_match` mode. It
has simpler behavior and a more robust approach to scoring.

Addresses #41106.
2021-04-14 13:33:19 -07:00
Adam Locke af700f4628
[DOCS] Update runtime fields for script query (#71338)
Fixes typo, moves example out of a NOTE admonition, and puts context before the example.
2021-04-06 10:12:08 -04:00
Nik Everett 5677c6822e
Point script query docs at runtime fields (#71291)
This adds a "note" on the docs for the script query pointing folks to
runtime fields because they are more flexible. It also translates the
request example into runtime fields.

Relates to #69291

Co-authored-by: Adam Locke <adam.locke@elastic.co>
2021-04-05 13:11:29 -04:00
Adam Locke f06dc219b2
[DOCS] Fixes deprecation message for Geo-polygon query (#71141)
* [DOCS] Fixes deprecation message for Geo-polygon query

* Change deprecation to full block admonition.
2021-03-31 16:37:29 -04:00
James Rodewig 693807a6d3
[DOCS] Fix double spaces (#71082) 2021-03-31 09:57:47 -04:00
James Rodewig 38edcb65ae
[DOCS] Document `index.query.default_field` index setting (#69922) 2021-03-17 17:11:25 -04:00
Julie Tibshirani da668e134a
Correct cross_fields docs on how analyzer groups are combined. (#69936)
When performing a multi_match in cross_fields mode, we group fields based on
their analyzer and create a blended query per group. Our docs claimed that the
group scores were combined through a boolean query, but they are actually
combined through a dismax that incorporates the tiebreaker parameter.

This commit updates the docs and adds a test verifying the behavior.
2021-03-08 14:56:17 -08:00
James Rodewig 79828761bc
[DOCS] Fix `prefix_length` data type (#70075) 2021-03-08 09:19:00 -05:00
James Rodewig 35c02c45f7
[DOCS] Note `case_sensitive` param was added in 7.10 (#69405) (#69466)
Co-authored-by: James Rodewig <40268737+jrodewig@users.noreply.github.com>

Co-authored-by: Bhavya Gupta <46423346+bhavya121999@users.noreply.github.com>
2021-02-23 13:12:28 -05:00
James Rodewig 31fc59efdf
[DOCS] Fix capitalization for Query DSL (#69236) 2021-02-18 18:57:19 -05:00
James Rodewig c65615911f
[DOCS] Expand simple query string query's multi-position token section (#68753) 2021-02-09 16:07:02 -05:00
Ignacio Vera f58d7854c5
Deprecate GeoPolygon query in favour of GeoShape query. (#64227) 2021-02-09 10:21:18 +01:00
James Rodewig 0f5af55258
[DOCS] Update example request description (#68587) (#68658)
The doc is misleading : The following intervals search returns documents containing `my favorite food` **immediately** followed by `hot water` or `cold porridge`

max_gaps apply only to the match query and is not used for checking proximity with the other match, the example given actually`This search would match a my_text value of my favorite food is cold`

Co-authored-by: Julien Guay <guay_j@yahoo.fr>
2021-02-08 08:50:56 -05:00
James Rodewig 7f3a4525a4
[DOCS] Remove outdated deprecated notes (#68246) 2021-02-01 09:30:45 -05:00
Ignacio Vera 808b4e71f1
Add support for Spatial Relationships to geo_point field (#67631)
Lucene 8.8 supports to query LatLonPoint field using spatial relationships.
2021-01-20 13:18:28 +01:00
Mayya Sharipova 76482210b8
Add linear function to rank_feature query (#67438)
This adds a linear function to the set of functions available
for rank_feature query

Closes #49859
2021-01-18 11:44:13 -05:00
Christoph Büscher c327794ae8
Fix range query on date fields for number inputs (#63692)
Currently, if you write a date range query with numeric 'to' or 'from' bounds,
they can be interpreted as years if no format is provided. We use
"strict_date_optional_time||epoch_millis" in this case that can interpret inputs
like 1000 as the year 1000 for example. 
This PR change this to always interpret and parse numbers with the "epoch_millis"
parser if no other formatter was provided.

Closes #63680
2020-12-01 18:49:50 +01:00
James Rodewig 1ea83359bb
[DOCS] Fix case for 'Boolean' (#64299) 2020-10-29 09:04:43 -04:00
Ignacio Vera b72be253a9
Enable geo_distance and geo_bounding_box queries on geo_shape field type (#64224) 2020-10-29 07:30:53 +01:00
markharwood 81b334913a
Search - make term/prefix/wildcard/regex query parsing more lenient (#63926)
* Remove errors when case_insensitive flag set to false

Closes #63893
2020-10-21 10:51:22 +01:00
Josh Devins 9b8b20a32b
[DOCS] Clarifies the effect of per-field boosting (#63733)
The original description of per-field boosting is incorrect. Boosting a
field does not imply that it is more important relative to other fields.
It simply means that the score is multiplied by the supplied boost
value. Due to the differences in each field's term and document
statistics, it's not possible to imply relative importance of fields
based on the per-field boost value alone.
2020-10-15 09:24:32 -04:00
Przemyslaw Gomulka b38eaae47f
[doc] Rounding range query rules (#63109)
a documentation explaining defaulting of missing fields when using date math parser.
relates #62268
2020-10-02 08:59:27 +02:00
markharwood fe9145fa5e
Search - add case insensitive flag for "term" family of queries (#61596)
Adds  case insensitive flag for term, prefix, and wildcard queries

Closes #61546
2020-09-18 17:17:08 +01:00
James Rodewig 224ff408de
[DOCS] Fix range query admon for clarity (#62163) 2020-09-09 10:17:58 -04:00
James Rodewig ea80a542a7
[DOCS] Fix typo in range query docs (#61722) 2020-08-31 10:46:06 -04:00
markharwood 7adf766fc4
Search - add case insensitive support for regex queries. (#59441)
Added case insensitive support for regex queries.
Forks a copy of Lucene’s RegexpQuery and RegExp from Lucene master.
This can be removed when 8.7 Lucene is released.

Closes #59235
2020-08-25 15:27:49 +01:00
James Rodewig c688cb6bfd
[DOCS] Fix hyphenation for "time series" (#61472) 2020-08-24 10:34:41 -04:00
Dan Hermann 9397510778
[DOCS] Update tie_breaker defaults for bool_prefix and most_fields query types (#61112) 2020-08-19 07:55:54 -05:00
James Rodewig a94e5cb7c4
[DOCS] Replace Wikipedia links with attribute (#61171) 2020-08-17 09:44:24 -04:00
James Rodewig a0f4edff66
[DOCS] Fix chunking in query docs (#61053)
Changes:
* Moves "Notes" sections for the joining queries and percolate query
  pages to the parent page
* Adds related redirects for the moved "Notes" pages
* Assigns explicit anchor IDs to other "Notes" headings. This was required for
  the redirects to work.
2020-08-12 13:45:49 -04:00
James Rodewig 929033f9dd
[DOCS] Move named query content to bool query (#60748) 2020-08-05 13:27:10 -04:00
James Rodewig 56c778235c
[DOCS] Fix metadata field refs (#60764) 2020-08-05 13:21:00 -04:00
James Rodewig 78b1cc426c
[DOCS] Fix query docs formatting (#60752) 2020-08-05 12:28:09 -04:00
James Rodewig a4dc336c16
[DOCS] Replace `twitter` dataset in search/agg docs (#60667) 2020-08-04 13:31:52 -04:00
James Rodewig ae01606785
[DOCS] Replace `twitter` dataset in docs (#60604) 2020-08-03 12:49:56 -04:00
Alexander Reelsen c7ac9e7073
[DOCS] http -> https, remove outdated plugin docs (#60380)
Plugin discovery documentation contained information about installing
Elasticsearch 2.0 and installing an oracle JDK, both of which is no
longer valid.

While noticing that the instructions used cleartext HTTP to install
packages, this commit replaces HTTPs links instead of HTTP where possible.

In addition a few community links have been removed, as they do not seem
to exist anymore.
2020-07-31 15:58:38 -04:00
James Rodewig 700c04d629
[DOCS] Fix `fuzzy_rewrite` ref in match query docs (#60237) 2020-07-27 15:17:17 -04:00
James Rodewig 441c3a21b1
[DOCS] Update my-index examples (#60132)
Changes the following example index names to `my-index-000001` for consistency:

* `my-index`
* `my_index`
* `myindex`
2020-07-27 14:46:39 -04:00
homersimpsons b0cc62f69e
[DOCS] Fix `rewrite` => `fuzzy_rewrite` in multi match query docs (#60175) 2020-07-27 12:13:33 -04:00
Ulas Keles a20fd49533
[DOCS] Fix formatting in simple query string query docs 2020-07-27 11:54:19 -04:00
James Rodewig d5b03f668b
[DOCS] Move search sort docs to separate page (#60123)
Moves the search sort docs from the deprecated 'Request Body Search'
page to a new subpage of 'Run a search'.

No substantive changes were made to the content.
2020-07-23 12:58:57 -04:00
James Rodewig 2774cd6938
[DOCS] Swap `[float]` for `[discrete]` (#60124)
Changes instances of `[float]` in our docs for `[discrete]`.

Asciidoctor prefers the `[discrete]` tag for floating headings:
https://asciidoctor.org/docs/asciidoc-asciidoctor-diffs/#blocks
2020-07-23 11:48:22 -04:00
James Rodewig 80b674fb25
[DOCS] Reformat snippets to use two-space indents (#59973) 2020-07-21 12:24:26 -04:00
James Rodewig 8a57800f1b
[DOCS] Add performance warning for scripts (#59890) 2020-07-20 14:04:35 -04:00
James Rodewig aa3ddfeefb
[DOCS] Move highlighting docs to separate page (#59768)
Moves the highlighting docs from the deprecated 'Request Body Search'
chapter to the new subpage of the 'Run a search chapter' section.

No substantive changes were made to the content.
2020-07-17 10:15:20 -04:00
homersimpsons 38aa0c18cd
[DOCS] MatchQuery: `transpositions` to `fuzzy_transpositions` (#59371) 2020-07-13 09:39:30 -04:00
James Rodewig 2be9db01c8
[DOCS] Replace `datatype` with `data type` (#58972) 2020-07-07 13:52:10 -04:00
István Zoltán Szabó d1e480e5bd
[DOCS] Extends geo_shape query docs to explain behavior when data is indexed as array of shapes (#57806)
Co-authored-by: James Rodewig <james.rodewig@elastic.co>
2020-06-08 15:03:59 +02:00
Tal Levy cfb36c3fcc
Update geo_point docs for geo_shape queries (#57487)
This commit highlights the ability for geo_point fields to be
used in geo_shape queries. It also adds an explicit geo_point
example in the geo_shape query documentation

Closes #56927.
2020-06-02 12:56:13 -07:00
Florian Kelbert 911c13bcf1
[DOCS] Fix typo in rank feature query docs (#57401) 2020-06-01 08:42:09 -04:00
Christoph Büscher 4e8134cfaf
Remove deprecated SimpleQueryStringBuilder parameters (#57200)
The `lowercase_expand_terms`, `locale` and `all_fields` parameters for
`simple_query_string` have been deprecated and a no-op for at least until 6.0
so we can remove them in 8.0
2020-05-28 16:36:32 +02:00
bellengao e0191438ed
[Docs] Fix typo in match-bool-prefix-query doc (#56077) 2020-05-04 14:17:00 +02:00
James Rodewig 3791a92603
[DOCS] Warn about searching across all fields wt. `query_string` (#55853)
Warn about potential performance impact when a large number of fields
is used with query string query and no default field.

Re-adds content from #35570.
That content was erroneously removed in #45296.

Co-authored-by: Peter Dyson <peter.dyson@geekpete.com>
2020-04-28 09:19:24 -04:00
James Rodewig 4ec2424442
[DOCS] Add query reference docs template (#52292) 2020-04-10 08:46:47 -04:00
Ignacio Vera 6182db5b77
Add new point field. (#53804)
This commit adds a new point field that is able to index arbitrary pair of values (x/y)
 in the cartesian space. It only supports filtering using shape queries at the moment.
2020-04-07 13:08:02 +02:00
Christoph Büscher 440fb48869
[Docs] Correct date rounding example for `range` query (#51524)
Looking into #50237 I realized that two of the examples given in the
documentation around date math rounding for range queries on date fields using
`gt` and `lt` is slightly off by a nanosecond. This PR changes this to the
bounds that are currently parsed using these parameters.
2020-04-06 17:02:38 +02:00
Alan Woodward 0f7cf7b720
TermsLookup fields should be marked as Required in docs (#53784)
The terms-lookup section of our terms query docs currently state that the
index, id and path fields are optional. They should be marked instead
as required.
2020-03-20 15:38:43 +00:00
Dominic Page d1cbdfb753
Geo shape query vs geo point (#52382)
Enable geo_shape query to work on geo_point fields for shapes: circle, polygon, multipolygon, rectangle

see: #48928

Co-Authored-By:  @iverase
2020-03-18 17:03:52 +01:00
Ralph Ursprung 2a44c29222
[Docs] Fix highlighting in match-query example (#52426) 2020-03-18 11:52:50 +01:00
Yash Joshi f9cbc76908 [Docs] Fix typo in range query (#53656) 2020-03-18 10:18:37 +01:00
Adam Canady 83baca1bbc [Docs] Correct examples for * and + in regexp-syntax.asciidoc (#53210) 2020-03-06 17:19:37 +01:00
Mayya Sharipova 556ee9a719
Correct boost calculation in script_score query (#52478)
Before boost in script_score query was wrongly applied only to the subquery.
This commit makes sure that the boost is applied to the whole score
that comes out of script.

Closes #48465
2020-02-24 10:46:33 -05:00
Marios Trivyzas a8b39ed842
Add a cluster setting to disallow expensive queries (#51385)
Add a new cluster setting `search.allow_expensive_queries` which by
default is `true`. If set to `false`, certain queries that have 
usually slow performance cannot be executed and an error message
is returned.

- Queries that need to do linear scans to identify matches:
  - Script queries
- Queries that have a high up-front cost:
  - Fuzzy queries
  - Regexp queries
  - Prefix queries (without index_prefixes enabled
  - Wildcard queries
  - Range queries on text and keyword fields
- Joining queries
  - HasParent queries
  - HasChild queries
  - ParentId queries
  - Nested queries
- Queries on deprecated 6.x geo shapes (using PrefixTree implementation)
- Queries that may have a high per-document cost:
  - Script score queries
  - Percolate queries

Closes: #29050
2020-02-12 18:06:04 +01:00
Mayya Sharipova 620996287a
Remove docs related to index time boosting (#51704)
As there is no really index time boosting,
as boost is only applied during query time,
this removes mentions of index time boosting.
2020-01-31 09:01:52 -05:00
Russ Cam ff22445364 [Docs] Including leading slash in range query doc example URLs (#51277) 2020-01-22 09:38:52 +01:00
Tal Levy 6c86606d2a
Adds support for geo-bounds filtering in geogrid aggregations (#50002)
It is fairly common to filter the geo point candidates in
geohash_grid and geotile_grid aggregations according to some
viewable bounding box. This change introduces the option of
specifying this filter directly in the tiling aggregation.

This is even more relevant to `geo_shape` where the bounds will restrict
the shape to be within the bounds

this optional `bounds` parameter is parsed in an equivalent fashion to 
the bounds specified in the geo_bounding_box query.
2020-01-14 08:29:10 -08:00
James Rodewig 979bfa6691
[DOCS] Fix time_zone example in range query docs (#50830)
One of the example snippets in the range query docs was missing a
required 'T' in the `date` format. This adds the required 'T'.
2020-01-10 07:23:25 -06:00
James Rodewig e090b9bcad
[DOCS] Fuzzy wildcard not supported in `query_string` (#50466)
The `query_string` does not support mixing wildcards with fuzziness.
This adds a related warning to the `query_string` docs.
2020-01-07 12:53:47 -06:00