Commit Graph

36 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
Francisco Fernández Castaño abc7a4776d
Avoid auto following leader system indices in CCR (#72815)
Relates #67686
2021-07-09 18:08:41 +02:00
James Rodewig f8d2578ede
[DOCS] EQL: Remove wildcard function (#72121) 2021-04-22 15:49:07 -04:00
James Rodewig 693807a6d3
[DOCS] Fix double spaces (#71082) 2021-03-31 09:57:47 -04: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
Przemyslaw Gomulka a3a7ae77fa
[doc] joda migration guide to version 8 (#60506)
indices created in v6 and not migrated earlier to java-time have to be
updated before upgrading to v8
closes #60374
2020-08-20 16:01:42 +02:00
James Rodewig 9ab920c8f1
[DOCS] Collapse remaining 8.0 breaking changes (#56418) 2020-05-08 10:21:33 -04:00
James Rodewig 4c44806d0f
[DOCS] Add collapsible sections to 8.0 breaking changes [Part 1] (#55811)
Co-authored-by: debadair <debadair@elastic.co>
2020-05-05 09:43:50 -04:00
James Rodewig f9e39f0759
[DOCS] Sort 8.0.0 breaking changes alphabetically (#55828) 2020-04-28 16:40:50 -04:00
David Turner 235c29eeba
Remove node filters for voting config exclusions (#55673)
The use of node filters for excluding nodes from the voting configuration was
deprecated in #50836; this commit removes support for node filters in this API.

Closes #47990
2020-04-24 16:04:47 +01:00
Hendrik Muhs 854f698cec
Percentiles aggregation: disallow specifying same percentile v… (#52257)
Disallow specifying the same percentile multiple times in percentiles
aggregation

Related: #51871
2020-02-26 13:40:33 +01:00
Yannick Welsch a9afdd7611
Remove fixed_auto_queue_size threadpool type (#52280)
* Remove fixed_auto_queue_size threadpool type

* Remove less

* compilation fix

* weaken assertion to accomodate tests that mock threadpool
2020-02-14 16:20:40 +01:00
David Turner 8c6f821c75
Remove the 'local' parameter of /_cat/nodes (#50594)
The cat nodes API performs a `ClusterStateAction` then a `NodesInfoAction`.
Today it accepts the `?local` parameter and passes this to the
`ClusterStateAction` but this parameter has no effect on the `NodesInfoAction`.
This is surprising, because `GET _cat/nodes?local` looks like it might be a
completely local call but in fact it still depends on every node in the
cluster.

This parameter was deprecated in 7.x in #50499 and this commit removes it.

Relates #50088
2020-01-06 14:12:51 +00:00
Julie Tibshirani a12b4094bf
Remove deprecated endpoints containing _xpack. (#48170)
The endpoints with `_xpack` in their path were deprecated in 7.x and can now be
removed. This commit removes deprecated endpoints for the following APIs:
* deprecation
* graph
* license
* monitoring
* rollup
* SQL
* watcher
2019-10-28 18:23:04 -07:00
André Letterer 5ec9d7be4d
Fixed synchronizing REST API inflight breaker names with internal variable (#40878)
The internal configuration settings were like that: network.breaker.inflight_requests
But the exposed REST API had the value names with underscore like that: network.breaker.in_flight_requests
This was now corrected to without underscores like that: network.breaker.inflight_requests
2019-09-03 14:56:36 +02:00
David Turner bc31ea752e
Always auto-release the flood-stage block (#45274)
Removes support for using a system property to disable the automatic release of
the write block applied when a node exceeds the flood-stage watermark.

Relates #42559
2019-08-08 11:47:14 +01:00
Tanguy Leroux 321c2b8627
Force Merge should reject requests with `only_expunge_deletes` and `max_num_segments` set (#44761)
This commit changes the ForceMergeRequest.validate() method so that it does 
not accept the parameters only_expunge_deletes and max_num_segments 
to be set at the same time.

The motivation is that InternalEngine.forceMerge() just ignores the max. number 
of segments parameter when the only expunge parameter is set to true, leaving 
the wrong impression to the user that max. number of segments has been applied. 
It also changes InternalEngine.forceMerge() so that it now throws an exception 
when both parameters are set, and modifies tests where needed.

Because it changes the behavior of the REST API I marked this as >breaking. 

Closes #43102
2019-07-26 09:34:36 +02:00
Zachary Tong 64642e4a7d
RollupStart endpoint should return OK if job already started (#41502)
If a job is started or indexing, RollupStart should always return
a success (200 OK) response since the job is, in fact, started
2019-06-03 11:24:16 -04: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
Jason Tedor 1b0c728cfa
Remove deprecated search.remote settings (#42381)
We deprecated these settings awhile ago, in favor of cluster.remote. In
7.x we were gentle and provided automatic upgrade of these settings to
the new settings. Now it is time for them to go. This commit removes the
deprecated search.remote settings.
2019-05-23 08:06:07 -07:00
Yannick Welsch c459ea828f
Remove node.max_local_storage_nodes (#42428)
This setting, which prior to Elasticsearch 5 was enabled by default and caused all kinds of
confusion, has since been disabled by default and is not recommended for production use. The
preferred way going forward is for users to explicitly specify separate data folders for each started
node to ensure that each node is consistently assigned to the same data path.

Relates to #42426
2019-05-23 16:02:12 +02:00
Henning Andersen 8dbdd06886
Reindex from Remote encoding (#41007)
Removed the leniency when encoding remote reindex search requests that
was introduced in 7.x. All index-names are now encoded before being sent
to the remote host.

Follow-up to #40303
2019-04-16 16:46:54 +02:00
Tim Brooks 07e0f0df21
Remove deprecated transport settings (#40918)
This is related to #36652. There are a number of transport settings that
were deprecated and replaced with new versions in 7.x. This commit
removes them from 8.0.
2019-04-12 15:42:05 -06:00
Gordon Brown 454e4967f1
Add ILM poll_interval limit to breaking changes (#41095)
ILM's poll_interval setting now has a lower limit of 1 second, which is
technically a breaking change.
2019-04-12 10:43:10 -06:00
Jason Tedor 8deadfb2d1
Bump the minimum Java version to Java 11 (#40754)
With the 8.0.0 release of Elasticsearch we will bump the minimum
required Java to Java 11. This commit puts this into effect on the
master branch.
2019-04-07 16:16:23 -04:00
Christoph Büscher 1597f69e44
Make Fuzziness reject illegal values earlier (#33511)
The current java implementation of Fuzziness leaves a lot of room for
initializing it with illegal values that either cause errors later when the
queries reach the shards where they are executed or values that are silently
ignored in favour of defaults. We should instead tighten the java implementation
of the class so that we only accept supported values. Currently those are
numeric values representing the edit distances 0, 1 and 2, optionally also as
float or string, and the "AUTO" fuzziness, which can come in a cusomizable
variant that allows specifying two value that define the positions in a term
where the AUTO option increases the allowed edit distance.

This change removes several redundant ways of object construction and adds input
validation to the remaining ones. Java users should either use one of the
predefined constants or use the static factory methods `fromEdits(int)` or
`fromString(String)` to create instances of the class, while other ctors are
hidden. This allows for instance control, e.g. returning one of the constants
when creating instances from an integer value.

Previously the class would accept any positive integer value and any float
value, while in effect the maximum allowed edit distance was capped at 2 in
practice. These values while throw an error now, as will any other String value
other than "AUTO" that where previously accepted but led to numeric exceptions
when the query was executed.
2019-04-05 10:35:35 +02:00
Tim Vernum 7b6e7146ea
Remove obsolete security settings (#40496)
Removes the deprecated accept_default_password setting.
This setting become redundant when default passwords were removed
from 6.0, but the setting was kept for BWC.

Removes native role store cache settings.
These have been unused since 5.2 but were kept for BWC.
2019-03-29 18:04:49 +11:00
lcawl 7dc6ddf62c [DOCS] Remove broken link 2019-03-22 15:57:27 -07:00
lcawl 05af3a51fb [DOCS] Removes notable breaking changes section 2019-03-22 15:45:13 -07:00
Lisa Cawley dda8cf82f8
[DOCS] Adds notable changes section (#38238) 2019-03-08 10:51:27 -08:00
Yannick Welsch 3b71a31557
Remove Zen1 (#39466)
Removes all traces of Zen1 from the code base. Some of these commits will also be backported to
7.0/7.x (#39470) as the cluster.coordination package was making use of some things in
discovery.zen and we want to keep 7.x as close as possible to master.
2019-03-04 15:51:12 +01:00
Henning Andersen ac7ec99bea
Unify blob store compress setting (#39346)
Blob store compression was all implemented generally, except reading the
setting for it. Moved the setting to BlobStoreRepository to unify this.
Also removed deprecated env setting 'repositories.fs.compress'.

This is a follow up on #39073
2019-02-28 12:34:13 +01:00
Christoph Büscher 6e3e3b1530
Move some token filter migration notes (#39072)
The removal of the "nGram" and "edgeNGram" token filter was filed in a new
migrate_8_0/mappings.asciidoc document but it should better be in an
analysis.asciidoc section and file.
2019-02-26 15:02:43 +01:00
Tamara Braun c1ab8218f1 Enforce Completion Context Limit (#38675)
This change adds a limit to the number of completion contexts that a completion field can define.

Closes #32741
2019-02-18 12:51:39 +01:00
Christoph Büscher 7bb2da197d
Remove `nGram` and `edgeNGram` token filter names (#38911)
In #30209 we deprecated the camel case `nGram` filter name in favour of `ngram` and
did the same for `edgeNGram` and `edge_ngram`. Using these names has been deprecated
since 6.4 and is issuing deprecation warnings since then.
I think we can remove these filters in 8.0. In a backport of this PR I would change what was a
dreprecation warning from 6.4. to an error starting with new indices created in 7.0.
2019-02-15 20:15:05 +01:00
Lisa Cawley 4775919cac
[DOCS] Adds placeholders for v8 highlights, breaking changes, release notes (#38641) 2019-02-08 15:48:42 -08:00