Commit Graph

23 Commits

Author SHA1 Message Date
James Rodewig 78607b5abd
[DOCS] Fix formatting for several 8.0 breaking changes (#75715) 2021-07-26 18:46:58 -04:00
James Rodewig ab8766777b
[DOCS] Fix tags and xrefs for 8.0 breaking changes (#75712)
A tag is required to reuse Elasticsearch breaking changes in the Stack
Guide. To display properly, the breaking changes must use external
links rather than xrefs.

This PR correctly places those tags for reuse. It also replaces
several xrefs with external links for reuse.
2021-07-26 17:43:39 -04: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
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
debadair 3b7f2f50c6
Rebranded breaking changes as the migration guide (#67496)
* Rebranded breaking changes as the migration guide

* Fixed heading level
2021-01-14 09:14:48 -08: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
Julie Tibshirani 79c267f4fc
Document breaking change around _id field data. (#64610) 2020-11-04 13:45:07 -08: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 2be9db01c8
[DOCS] Replace `datatype` with `data type` (#58972) 2020-07-07 13:52:10 -04:00
Christoph Büscher 3d4f9fedaf
Check for negative "from" values in search request body (#54953)
Today we already disallow negative values for the "from" parameter in the search
API when it is set as a request parameter and setting it on the
SearchSourceBuilder, but it is still parsed without complaint from a search
body, leading to differing exceptions later. This PR changes this behavior to be
the same regardless of setting the value directly, as url parameter or in the
search body. While we silently accepted "-1" as meaning "unset" and used the
default value of 0 so far, any negative from-value is now disallowed.

Closes #54897
2020-05-28 16:25:19 +02:00
James Rodewig 754a3e98e6
[DOCS] Add impact sections to API, search, transport, thread pool 8.0 breaking changes (#56437) 2020-05-08 12:55:56 -04:00
James Rodewig 9ab920c8f1
[DOCS] Collapse remaining 8.0 breaking changes (#56418) 2020-05-08 10:21:33 -04:00
Julie Tibshirani 724e24ddf2
Remove use_field_mapping format option for docvalue fields. (#55622)
In 7.0, we began formatting `docvalue_fields` by default using each field's
mapping definition. To ease the transition from 6.x, we added the format
option `use_field_mapping`. This parameter was deprecated in 7.0, and we can
remove it in 8.0.
2020-04-27 12:42:28 -07:00
James Rodewig efe33f0658
[DOCS] Fix 8.0 breaking changes for reuse in Install/Upgrade Guide (#55694)
Adds `//tag::notable-breaking-changes[]` to several breaking changes
files. This tag is required for reuse in the [Elastic Stack Installation
and Upgrade Guide][0].

Also replaces a relative xref with an external links. External links are
required for reuse in the Installation and Upgrade Guide.

[0]: https://www.elastic.co/guide/en/elastic-stack/master/index.html
2020-04-23 16:47:39 -04:00
Julie Tibshirani 13053c6ad9
Remove the object format for indices_boost. (#55078)
This format has been deprecated since version 5.2.
2020-04-14 21:01:07 -07:00
Christoph Büscher 7cec5f93be
Make `date_range` query rounding consistent with `date` (#50237)
Currently the rounding used in range queries can behave differently for `date`
and `date_range` as explained in #50009. The behaviour on `date` fields is 
the one we document in https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-range-query.html#range-query-date-math-rounding. 
This change adapts the rounding behaviour for RangeType.DATE so it uses the
same logic as the `date` for the `date_range` type.

Closes #50009
2020-01-31 14:15:13 +01:00
Julie Tibshirani 460d545921
Remove support for sparse vectors. (#48781)
Follow up to #48368. This PR removes support for `sparse_vector` on new
indices. On 7.x indices a `sparse_vector` can still be defined, but it is not
possible to index or search on it.
2019-11-14 16:54:48 -05:00
Julie Tibshirani 939c24223b
Remove deprecated vector functions. (#48725)
Follow up to #48604. This PR removes the deprecated vector function signatures
of the form `cosineSimilarity(query, doc['field'])`.
2019-10-31 10:19:03 -07:00
Alan Woodward 7c90801aff
Remove types from Get/MultiGet (#46587)
This commit removes types from the ShardGetService, and propagates this API change
up through the Transport and Rest actions for Get and MultiGet

Relates to #41059
2019-09-20 14:22:57 +01:00
Jim Ferenczi a4ed7b1ca1
Decouple shard allocation awareness from search and get requests (#45735)
With this commit, Elasticsearch will no longer prefer using shards in the same location
(with the same awareness attribute values) to process `_search` and `_get` requests.
Instead, adaptive replica selection (the default since 7.0) should route requests more efficiently
using the service time of prior inter-node communications. Clusters with big latencies between
nodes should switch to cross cluster replication to isolate nodes within the same zone.
Note that this change only targets 8.0 since it is considered as breaking. However a follow up
pr should add an option to activate this behavior in 7.x in order to allow users to opt-in early.

Closes #43453
2019-09-04 21:48:03 +02:00
Jim Ferenczi a614415838
Remove deprecated sort options: nested_path and nested_filter (#42809)
This commit removes the nested_path and nested_filter options deprecated in 6x.
This change also checks that the sort field has a [nested] option if it is under a nested
object and throws an exception if it's not the case.

Closes #27098
2019-06-27 17:30:02 +02:00
Marios Trivyzas 6dd4d2b7a6
Remove CommonTermsQuery and cutoff_frequency param (#42654)
Remove `common` query and `cutoff_frequency` parameter of
`match` and `multi_match` queries. Both have already been
deprecated for the next 7.x version.

Closes: #37096
2019-05-31 17:06:06 +02:00
Colin Goodheart-Smithe 3647d7c94e
Removes typed REST endpoints from search and related APIs (#41640) 2019-05-09 14:41:11 +01:00