Commit Graph

16 Commits

Author SHA1 Message Date
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
James Rodewig 5c75d004fa
[DOCS] Replace `put` with `create or update` in API names (#70330)
Co-authored-by: debadair <debadair@elastic.co>
Co-authored-by: Lisa Cawley <lcawley@elastic.co>
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
2021-03-15 14:49:44 -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
David Turner ec08f924c7
Introduce ?wait_for_active_shards=index-setting (#67158)
In 7.x the close indices API defaulted to `?wait_for_active_shards=0`
but from 8.0 it defaults to respecting the index settings instead.  This
commit introduces the `index-setting` value for this parameter on this
API allowing users to opt-in to the future behaviour today, and emits a
deprecation warning indicating that the default no longer needs to be
used and will be unsupported in future.

In 7.x a follow up PR will introduce support for the same
`index-setting` value for this parameter and will emit deprecation
warnings if users try and use the default instead.

Relates #66419
2021-01-11 08:33:16 +00:00
David Turner b622adeb7a Revert "Document new waiting on shards on index close (#66543)"
This reverts commit 1c059e79e8.
2020-12-17 21:32:16 +00:00
David Turner 1c059e79e8
Document new waiting on shards on index close (#66543)
In 8.x the default for `?wait_for_active_shards` changes from `NONE` to
`DEFAULT` on calls to `POST /index/_close`. This commit adds this change
to the breaking changes docs.

Relates #66419, #66542
2020-12-17 17:51:24 +00:00
Dan Hermann c829f8edd1
Remove deprecated _upgrade API (#64732) 2020-11-12 11:09:56 -06: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 d6fbbe9afd
[DOCS] Add collapsible sections to 8.0 breaking changes [Part 3] (#56297) 2020-05-07 12:22:05 -04: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
Nhat Nguyen 6e0fbbd4db
Remove translog retention settings (#51697)
The translog retention settings index.translog.retention.size and 
index.translog.retention.age were effectively ignored in 7.4, 
deprecated in 7.7, and now removed in 8.0 in favor of soft-deletes.

Closes #50775
2020-01-31 08:18:07 -05:00
Nhat Nguyen c893a3e495
Make soft-deletes mandatory in 8.0 (#51122)
Creating indices with soft deletes disabled is no longer supported in 8.0.
2020-01-17 17:34:22 -05:00
Nhat Nguyen 09b46c8646
Goodbye and thank you synced flush! (#50882)
Synced flush was a brilliant idea. It supports instant recoveries with a 
quite small implementation. However, with the presence of sequence
numbers and retention leases, it is no longer needed. This change
removes it from 8.0.

Relates #5077
2020-01-16 09:43:07 -05:00
Julie Tibshirani 54f5907067
Remove the 'template' field in index templates. (#49460)
The `template` field was deprecated in 6.0 in favor of `index_patterns`, and can
now be removed.

Relates to #21009.
2020-01-09 17:07:58 -08:00
David Turner 3ce7a37f1f
Remove index.force_memory_term_dictionary setting (#48873)
This temporary setting was introduced in #39741 but has had no effect since it
was deprecated in #42838. This commit removes this setting.
2019-11-05 20:17:32 -05: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