From 0ef6c72bcf402cf3b43306747a13b3b16a928ed1 Mon Sep 17 00:00:00 2001 From: Rory Hunter Date: Wed, 21 Apr 2021 12:34:30 +0100 Subject: [PATCH] Bump version to v7.14.0 --- .ci/bwcVersions | 1 + buildSrc/version.properties | 2 +- docs/changelog/27600.yaml | 8 + docs/changelog/33511.yaml | 51 +++ docs/changelog/37907.yaml | 8 + docs/changelog/38413.yaml | 7 + docs/changelog/39328.yaml | 12 + docs/changelog/39346.yaml | 8 + docs/changelog/39450.yaml | 15 + docs/changelog/39459.yaml | 8 + docs/changelog/39593.yaml | 26 ++ docs/changelog/39747.yaml | 8 + docs/changelog/40033.yaml | 15 + docs/changelog/40379.yaml | 8 + docs/changelog/40419.yaml | 28 ++ docs/changelog/40496.yaml | 17 + docs/changelog/40878.yaml | 20 + docs/changelog/40952.yaml | 7 + docs/changelog/41007.yaml | 17 + docs/changelog/41011.yaml | 39 ++ docs/changelog/41124.yaml | 9 + docs/changelog/41347.yaml | 7 + docs/changelog/41492.yaml | 8 + docs/changelog/41502.yaml | 22 + docs/changelog/41560.yaml | 16 + docs/changelog/41620.yaml | 8 + docs/changelog/41640.yaml | 12 + docs/changelog/41676.yaml | 12 + docs/changelog/41808.yaml | 9 + docs/changelog/41972.yaml | 8 + docs/changelog/42090.yaml | 395 ++++++++++++++++++ docs/changelog/42112.yaml | 16 + docs/changelog/42155.yaml | 7 + docs/changelog/42174.yaml | 15 + docs/changelog/42179.yaml | 8 + docs/changelog/42198.yaml | 13 + docs/changelog/42202.yaml | 12 + docs/changelog/42253.yaml | 10 + docs/changelog/42288.yaml | 8 + docs/changelog/42333.yaml | 17 + docs/changelog/42359.yaml | 16 + docs/changelog/42381.yaml | 22 + docs/changelog/42428.yaml | 22 + docs/changelog/42471.yaml | 17 + docs/changelog/42489.yaml | 18 + docs/changelog/42538.yaml | 12 + docs/changelog/42654.yaml | 17 + docs/changelog/42729.yaml | 17 + docs/changelog/42770.yaml | 14 + docs/changelog/42809.yaml | 21 + docs/changelog/42815.yaml | 17 + docs/changelog/42816.yaml | 15 + docs/changelog/42817.yaml | 15 + docs/changelog/43099.yaml | 7 + docs/changelog/43108.yaml | 16 + docs/changelog/43164.yaml | 7 + docs/changelog/43236.yaml | 15 + docs/changelog/43344.yaml | 7 + docs/changelog/43373.yaml | 21 + docs/changelog/43382.yaml | 8 + docs/changelog/43430.yaml | 7 + docs/changelog/43536.yaml | 7 + docs/changelog/43558.yaml | 8 + docs/changelog/43559.yaml | 7 + docs/changelog/43686.yaml | 17 + docs/changelog/43781.yaml | 10 + docs/changelog/44090.yaml | 23 + docs/changelog/44133.yaml | 9 + docs/changelog/44264.yaml | 48 +++ docs/changelog/44642.yaml | 7 + docs/changelog/44752.yaml | 20 + docs/changelog/44761.yaml | 24 ++ docs/changelog/44894.yaml | 17 + docs/changelog/44902.yaml | 8 + docs/changelog/44905.yaml | 9 + docs/changelog/44929.yaml | 29 ++ docs/changelog/44982.yaml | 16 + docs/changelog/45497.yaml | 9 + docs/changelog/45586.yaml | 8 + docs/changelog/45675.yaml | 12 + docs/changelog/45735.yaml | 29 ++ docs/changelog/45878.yaml | 8 + docs/changelog/45892.yaml | 23 + docs/changelog/45905.yaml | 17 + docs/changelog/45940.yaml | 17 + docs/changelog/45945.yaml | 32 ++ docs/changelog/45947.yaml | 20 + docs/changelog/46055.yaml | 8 + docs/changelog/46147.yaml | 22 + docs/changelog/46327.yaml | 9 + docs/changelog/46603.yaml | 8 + docs/changelog/46702.yaml | 8 + docs/changelog/46749.yaml | 8 + docs/changelog/46967.yaml | 9 + docs/changelog/46983.yaml | 16 + docs/changelog/47105.yaml | 8 + docs/changelog/47203.yaml | 17 + docs/changelog/47207.yaml | 19 + docs/changelog/47364.yaml | 25 ++ docs/changelog/47650.yaml | 7 + docs/changelog/47651.yaml | 7 + docs/changelog/47717.yaml | 19 + docs/changelog/48170.yaml | 35 ++ docs/changelog/48443.yaml | 26 ++ docs/changelog/48471.yaml | 18 + docs/changelog/48632.yaml | 16 + docs/changelog/48725.yaml | 17 + docs/changelog/48781.yaml | 16 + docs/changelog/48927.yaml | 8 + docs/changelog/48949.yaml | 7 + docs/changelog/49079.yaml | 7 + docs/changelog/49460.yaml | 16 + docs/changelog/49728.yaml | 8 + docs/changelog/50067.yaml | 8 + docs/changelog/50277.yaml | 9 + docs/changelog/50359.yaml | 8 + docs/changelog/50415.yaml | 7 + docs/changelog/50594.yaml | 22 + docs/changelog/50739.yaml | 25 ++ docs/changelog/50844.yaml | 23 + docs/changelog/50882.yaml | 22 + docs/changelog/51189.yaml | 8 + docs/changelog/51195.yaml | 16 + docs/changelog/51219.yaml | 20 + docs/changelog/51417.yaml | 8 + docs/changelog/51421.yaml | 8 + docs/changelog/51697.yaml | 18 + docs/changelog/51704.yaml | 8 + docs/changelog/51716.yaml | 17 + docs/changelog/52208.yaml | 9 + docs/changelog/52257.yaml | 16 + docs/changelog/52280.yaml | 20 + docs/changelog/52987.yaml | 7 + docs/changelog/53314.yaml | 20 + docs/changelog/53715.yaml | 8 + docs/changelog/53785.yaml | 8 + docs/changelog/53845.yaml | 22 + docs/changelog/54175.yaml | 18 + docs/changelog/54381.yaml | 18 + docs/changelog/54753.yaml | 8 + docs/changelog/54904.yaml | 8 + docs/changelog/54953.yaml | 8 + docs/changelog/55078.yaml | 12 + docs/changelog/55100.yaml | 16 + docs/changelog/55109.yaml | 8 + docs/changelog/55181.yaml | 8 + docs/changelog/55399.yaml | 8 + docs/changelog/55489.yaml | 20 + docs/changelog/55544.yaml | 7 + docs/changelog/55622.yaml | 16 + docs/changelog/55673.yaml | 20 + docs/changelog/55736.yaml | 8 + docs/changelog/56149.yaml | 8 + docs/changelog/56211.yaml | 19 + docs/changelog/57200.yaml | 7 + docs/changelog/57591.yaml | 21 + docs/changelog/57594.yaml | 7 + docs/changelog/58220.yaml | 8 + docs/changelog/58387.yaml | 7 + docs/changelog/58732.yaml | 8 + docs/changelog/58779.yaml | 8 + docs/changelog/59262.yaml | 20 + docs/changelog/59265.yaml | 34 ++ docs/changelog/59336.yaml | 7 + docs/changelog/59349.yaml | 8 + docs/changelog/59475.yaml | 7 + docs/changelog/59501.yaml | 9 + docs/changelog/59507.yaml | 20 + docs/changelog/59698.yaml | 15 + docs/changelog/59870.yaml | 9 + docs/changelog/59949.yaml | 8 + docs/changelog/60044.yaml | 8 + docs/changelog/60158.yaml | 8 + docs/changelog/60351.yaml | 8 + docs/changelog/60505.yaml | 7 + docs/changelog/60873.yaml | 18 + docs/changelog/61043.yaml | 16 + docs/changelog/61259.yaml | 8 + docs/changelog/61427.yaml | 25 ++ docs/changelog/61428.yaml | 9 + docs/changelog/61508.yaml | 7 + docs/changelog/61594.yaml | 7 + docs/changelog/61825.yaml | 8 + docs/changelog/62156.yaml | 7 + docs/changelog/62309.yaml | 17 + docs/changelog/62468.yaml | 8 + docs/changelog/62639.yaml | 8 + docs/changelog/62646.yaml | 7 + docs/changelog/63038.yaml | 7 + docs/changelog/63384.yaml | 9 + docs/changelog/63660.yaml | 8 + docs/changelog/63692.yaml | 27 ++ docs/changelog/64252.yaml | 12 + docs/changelog/64327.yaml | 9 + docs/changelog/64406.yaml | 8 + docs/changelog/64423.yaml | 8 + docs/changelog/64472.yaml | 34 ++ docs/changelog/64481.yaml | 8 + docs/changelog/64650.yaml | 9 + docs/changelog/64708.yaml | 9 + docs/changelog/64721.yaml | 9 + docs/changelog/64732.yaml | 17 + docs/changelog/64794.yaml | 8 + docs/changelog/64867.yaml | 20 + docs/changelog/64868.yaml | 20 + docs/changelog/64869.yaml | 8 + docs/changelog/65255.yaml | 7 + docs/changelog/65259.yaml | 7 + docs/changelog/65500.yaml | 8 + docs/changelog/65590.yaml | 9 + docs/changelog/65753.yaml | 19 + docs/changelog/66297.yaml | 8 + docs/changelog/66671.yaml | 8 + docs/changelog/67154.yaml | 7 + docs/changelog/67158.yaml | 8 + docs/changelog/67216.yaml | 8 + docs/changelog/67374.yaml | 9 + docs/changelog/67409.yaml | 8 + docs/changelog/67552.yaml | 8 + docs/changelog/67672.yaml | 7 + docs/changelog/67677.yaml | 9 + docs/changelog/67923.yaml | 8 + docs/changelog/68113.yaml | 8 + docs/changelog/68157.yaml | 9 + docs/changelog/68176.yaml | 8 + docs/changelog/68214.yaml | 9 + docs/changelog/68564.yaml | 18 + docs/changelog/68606.yaml | 7 + docs/changelog/68648.yaml | 8 + docs/changelog/68754.yaml | 7 + docs/changelog/68808.yaml | 8 + docs/changelog/68966.yaml | 7 + docs/changelog/69029.yaml | 9 + docs/changelog/69131.yaml | 10 + docs/changelog/69149.yaml | 20 + docs/changelog/69512.yaml | 7 + docs/changelog/69606.yaml | 9 + docs/changelog/69710.yaml | 8 + docs/changelog/69774.yaml | 8 + docs/changelog/69901.yaml | 8 + docs/changelog/70209.yaml | 9 + docs/changelog/70243.yaml | 7 + docs/changelog/70878.yaml | 8 + elasticsearch | 0 .../main/java/org/elasticsearch/Version.java | 3 +- 245 files changed, 3513 insertions(+), 2 deletions(-) create mode 100644 docs/changelog/27600.yaml create mode 100644 docs/changelog/33511.yaml create mode 100644 docs/changelog/37907.yaml create mode 100644 docs/changelog/38413.yaml create mode 100644 docs/changelog/39328.yaml create mode 100644 docs/changelog/39346.yaml create mode 100644 docs/changelog/39450.yaml create mode 100644 docs/changelog/39459.yaml create mode 100644 docs/changelog/39593.yaml create mode 100644 docs/changelog/39747.yaml create mode 100644 docs/changelog/40033.yaml create mode 100644 docs/changelog/40379.yaml create mode 100644 docs/changelog/40419.yaml create mode 100644 docs/changelog/40496.yaml create mode 100644 docs/changelog/40878.yaml create mode 100644 docs/changelog/40952.yaml create mode 100644 docs/changelog/41007.yaml create mode 100644 docs/changelog/41011.yaml create mode 100644 docs/changelog/41124.yaml create mode 100644 docs/changelog/41347.yaml create mode 100644 docs/changelog/41492.yaml create mode 100644 docs/changelog/41502.yaml create mode 100644 docs/changelog/41560.yaml create mode 100644 docs/changelog/41620.yaml create mode 100644 docs/changelog/41640.yaml create mode 100644 docs/changelog/41676.yaml create mode 100644 docs/changelog/41808.yaml create mode 100644 docs/changelog/41972.yaml create mode 100644 docs/changelog/42090.yaml create mode 100644 docs/changelog/42112.yaml create mode 100644 docs/changelog/42155.yaml create mode 100644 docs/changelog/42174.yaml create mode 100644 docs/changelog/42179.yaml create mode 100644 docs/changelog/42198.yaml create mode 100644 docs/changelog/42202.yaml create mode 100644 docs/changelog/42253.yaml create mode 100644 docs/changelog/42288.yaml create mode 100644 docs/changelog/42333.yaml create mode 100644 docs/changelog/42359.yaml create mode 100644 docs/changelog/42381.yaml create mode 100644 docs/changelog/42428.yaml create mode 100644 docs/changelog/42471.yaml create mode 100644 docs/changelog/42489.yaml create mode 100644 docs/changelog/42538.yaml create mode 100644 docs/changelog/42654.yaml create mode 100644 docs/changelog/42729.yaml create mode 100644 docs/changelog/42770.yaml create mode 100644 docs/changelog/42809.yaml create mode 100644 docs/changelog/42815.yaml create mode 100644 docs/changelog/42816.yaml create mode 100644 docs/changelog/42817.yaml create mode 100644 docs/changelog/43099.yaml create mode 100644 docs/changelog/43108.yaml create mode 100644 docs/changelog/43164.yaml create mode 100644 docs/changelog/43236.yaml create mode 100644 docs/changelog/43344.yaml create mode 100644 docs/changelog/43373.yaml create mode 100644 docs/changelog/43382.yaml create mode 100644 docs/changelog/43430.yaml create mode 100644 docs/changelog/43536.yaml create mode 100644 docs/changelog/43558.yaml create mode 100644 docs/changelog/43559.yaml create mode 100644 docs/changelog/43686.yaml create mode 100644 docs/changelog/43781.yaml create mode 100644 docs/changelog/44090.yaml create mode 100644 docs/changelog/44133.yaml create mode 100644 docs/changelog/44264.yaml create mode 100644 docs/changelog/44642.yaml create mode 100644 docs/changelog/44752.yaml create mode 100644 docs/changelog/44761.yaml create mode 100644 docs/changelog/44894.yaml create mode 100644 docs/changelog/44902.yaml create mode 100644 docs/changelog/44905.yaml create mode 100644 docs/changelog/44929.yaml create mode 100644 docs/changelog/44982.yaml create mode 100644 docs/changelog/45497.yaml create mode 100644 docs/changelog/45586.yaml create mode 100644 docs/changelog/45675.yaml create mode 100644 docs/changelog/45735.yaml create mode 100644 docs/changelog/45878.yaml create mode 100644 docs/changelog/45892.yaml create mode 100644 docs/changelog/45905.yaml create mode 100644 docs/changelog/45940.yaml create mode 100644 docs/changelog/45945.yaml create mode 100644 docs/changelog/45947.yaml create mode 100644 docs/changelog/46055.yaml create mode 100644 docs/changelog/46147.yaml create mode 100644 docs/changelog/46327.yaml create mode 100644 docs/changelog/46603.yaml create mode 100644 docs/changelog/46702.yaml create mode 100644 docs/changelog/46749.yaml create mode 100644 docs/changelog/46967.yaml create mode 100644 docs/changelog/46983.yaml create mode 100644 docs/changelog/47105.yaml create mode 100644 docs/changelog/47203.yaml create mode 100644 docs/changelog/47207.yaml create mode 100644 docs/changelog/47364.yaml create mode 100644 docs/changelog/47650.yaml create mode 100644 docs/changelog/47651.yaml create mode 100644 docs/changelog/47717.yaml create mode 100644 docs/changelog/48170.yaml create mode 100644 docs/changelog/48443.yaml create mode 100644 docs/changelog/48471.yaml create mode 100644 docs/changelog/48632.yaml create mode 100644 docs/changelog/48725.yaml create mode 100644 docs/changelog/48781.yaml create mode 100644 docs/changelog/48927.yaml create mode 100644 docs/changelog/48949.yaml create mode 100644 docs/changelog/49079.yaml create mode 100644 docs/changelog/49460.yaml create mode 100644 docs/changelog/49728.yaml create mode 100644 docs/changelog/50067.yaml create mode 100644 docs/changelog/50277.yaml create mode 100644 docs/changelog/50359.yaml create mode 100644 docs/changelog/50415.yaml create mode 100644 docs/changelog/50594.yaml create mode 100644 docs/changelog/50739.yaml create mode 100644 docs/changelog/50844.yaml create mode 100644 docs/changelog/50882.yaml create mode 100644 docs/changelog/51189.yaml create mode 100644 docs/changelog/51195.yaml create mode 100644 docs/changelog/51219.yaml create mode 100644 docs/changelog/51417.yaml create mode 100644 docs/changelog/51421.yaml create mode 100644 docs/changelog/51697.yaml create mode 100644 docs/changelog/51704.yaml create mode 100644 docs/changelog/51716.yaml create mode 100644 docs/changelog/52208.yaml create mode 100644 docs/changelog/52257.yaml create mode 100644 docs/changelog/52280.yaml create mode 100644 docs/changelog/52987.yaml create mode 100644 docs/changelog/53314.yaml create mode 100644 docs/changelog/53715.yaml create mode 100644 docs/changelog/53785.yaml create mode 100644 docs/changelog/53845.yaml create mode 100644 docs/changelog/54175.yaml create mode 100644 docs/changelog/54381.yaml create mode 100644 docs/changelog/54753.yaml create mode 100644 docs/changelog/54904.yaml create mode 100644 docs/changelog/54953.yaml create mode 100644 docs/changelog/55078.yaml create mode 100644 docs/changelog/55100.yaml create mode 100644 docs/changelog/55109.yaml create mode 100644 docs/changelog/55181.yaml create mode 100644 docs/changelog/55399.yaml create mode 100644 docs/changelog/55489.yaml create mode 100644 docs/changelog/55544.yaml create mode 100644 docs/changelog/55622.yaml create mode 100644 docs/changelog/55673.yaml create mode 100644 docs/changelog/55736.yaml create mode 100644 docs/changelog/56149.yaml create mode 100644 docs/changelog/56211.yaml create mode 100644 docs/changelog/57200.yaml create mode 100644 docs/changelog/57591.yaml create mode 100644 docs/changelog/57594.yaml create mode 100644 docs/changelog/58220.yaml create mode 100644 docs/changelog/58387.yaml create mode 100644 docs/changelog/58732.yaml create mode 100644 docs/changelog/58779.yaml create mode 100644 docs/changelog/59262.yaml create mode 100644 docs/changelog/59265.yaml create mode 100644 docs/changelog/59336.yaml create mode 100644 docs/changelog/59349.yaml create mode 100644 docs/changelog/59475.yaml create mode 100644 docs/changelog/59501.yaml create mode 100644 docs/changelog/59507.yaml create mode 100644 docs/changelog/59698.yaml create mode 100644 docs/changelog/59870.yaml create mode 100644 docs/changelog/59949.yaml create mode 100644 docs/changelog/60044.yaml create mode 100644 docs/changelog/60158.yaml create mode 100644 docs/changelog/60351.yaml create mode 100644 docs/changelog/60505.yaml create mode 100644 docs/changelog/60873.yaml create mode 100644 docs/changelog/61043.yaml create mode 100644 docs/changelog/61259.yaml create mode 100644 docs/changelog/61427.yaml create mode 100644 docs/changelog/61428.yaml create mode 100644 docs/changelog/61508.yaml create mode 100644 docs/changelog/61594.yaml create mode 100644 docs/changelog/61825.yaml create mode 100644 docs/changelog/62156.yaml create mode 100644 docs/changelog/62309.yaml create mode 100644 docs/changelog/62468.yaml create mode 100644 docs/changelog/62639.yaml create mode 100644 docs/changelog/62646.yaml create mode 100644 docs/changelog/63038.yaml create mode 100644 docs/changelog/63384.yaml create mode 100644 docs/changelog/63660.yaml create mode 100644 docs/changelog/63692.yaml create mode 100644 docs/changelog/64252.yaml create mode 100644 docs/changelog/64327.yaml create mode 100644 docs/changelog/64406.yaml create mode 100644 docs/changelog/64423.yaml create mode 100644 docs/changelog/64472.yaml create mode 100644 docs/changelog/64481.yaml create mode 100644 docs/changelog/64650.yaml create mode 100644 docs/changelog/64708.yaml create mode 100644 docs/changelog/64721.yaml create mode 100644 docs/changelog/64732.yaml create mode 100644 docs/changelog/64794.yaml create mode 100644 docs/changelog/64867.yaml create mode 100644 docs/changelog/64868.yaml create mode 100644 docs/changelog/64869.yaml create mode 100644 docs/changelog/65255.yaml create mode 100644 docs/changelog/65259.yaml create mode 100644 docs/changelog/65500.yaml create mode 100644 docs/changelog/65590.yaml create mode 100644 docs/changelog/65753.yaml create mode 100644 docs/changelog/66297.yaml create mode 100644 docs/changelog/66671.yaml create mode 100644 docs/changelog/67154.yaml create mode 100644 docs/changelog/67158.yaml create mode 100644 docs/changelog/67216.yaml create mode 100644 docs/changelog/67374.yaml create mode 100644 docs/changelog/67409.yaml create mode 100644 docs/changelog/67552.yaml create mode 100644 docs/changelog/67672.yaml create mode 100644 docs/changelog/67677.yaml create mode 100644 docs/changelog/67923.yaml create mode 100644 docs/changelog/68113.yaml create mode 100644 docs/changelog/68157.yaml create mode 100644 docs/changelog/68176.yaml create mode 100644 docs/changelog/68214.yaml create mode 100644 docs/changelog/68564.yaml create mode 100644 docs/changelog/68606.yaml create mode 100644 docs/changelog/68648.yaml create mode 100644 docs/changelog/68754.yaml create mode 100644 docs/changelog/68808.yaml create mode 100644 docs/changelog/68966.yaml create mode 100644 docs/changelog/69029.yaml create mode 100644 docs/changelog/69131.yaml create mode 100644 docs/changelog/69149.yaml create mode 100644 docs/changelog/69512.yaml create mode 100644 docs/changelog/69606.yaml create mode 100644 docs/changelog/69710.yaml create mode 100644 docs/changelog/69774.yaml create mode 100644 docs/changelog/69901.yaml create mode 100644 docs/changelog/70209.yaml create mode 100644 docs/changelog/70243.yaml create mode 100644 docs/changelog/70878.yaml create mode 100644 elasticsearch diff --git a/.ci/bwcVersions b/.ci/bwcVersions index 543bf0c0b5463..40907cabc762d 100644 --- a/.ci/bwcVersions +++ b/.ci/bwcVersions @@ -80,3 +80,4 @@ BWC_VERSION: - "7.11.2" - "7.12.0" - "7.12.1" + - "7.13.0" diff --git a/buildSrc/version.properties b/buildSrc/version.properties index e4e9e7ad1e396..0847ce901a2bb 100644 --- a/buildSrc/version.properties +++ b/buildSrc/version.properties @@ -1,4 +1,4 @@ -elasticsearch = 7.13.0 +elasticsearch = 7.14.0 lucene = 8.8.2 bundled_jdk_vendor = adoptopenjdk diff --git a/docs/changelog/27600.yaml b/docs/changelog/27600.yaml new file mode 100644 index 0000000000000..3a1439645142b --- /dev/null +++ b/docs/changelog/27600.yaml @@ -0,0 +1,8 @@ +pr: 27600 +issues: + - 27583 +area: Infra/Settings +type: enhancement +summary: Remove setting `index.optimize_auto_generated_id` +versions: + - v8.0.0 diff --git a/docs/changelog/33511.yaml b/docs/changelog/33511.yaml new file mode 100644 index 0000000000000..e05fd615dc234 --- /dev/null +++ b/docs/changelog/33511.yaml @@ -0,0 +1,51 @@ +pr: 33511 +issues: [] +area: Search +type: breaking, enhancement +summary: Make Fuzziness reject illegal values earlier +versions: + - v8.0.0 +breaking: + notable: false + title: Make Fuzziness reject illegal values earlier + anchor: make_fuzziness_reject_illegal_values_earlier + body: >- + 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. diff --git a/docs/changelog/37907.yaml b/docs/changelog/37907.yaml new file mode 100644 index 0000000000000..b1dd580baadd5 --- /dev/null +++ b/docs/changelog/37907.yaml @@ -0,0 +1,8 @@ +pr: 37907 +issues: + - 37897 +area: Search +type: bug +summary: Handle total hits equal to `track_total_hits` +versions: + - v8.0.0 diff --git a/docs/changelog/38413.yaml b/docs/changelog/38413.yaml new file mode 100644 index 0000000000000..53eef5ad04cf7 --- /dev/null +++ b/docs/changelog/38413.yaml @@ -0,0 +1,7 @@ +pr: 38413 +issues: [] +area: Infra/REST API +type: enhancement +summary: Introduce stability description to the REST API specification +versions: + - v8.0.0 diff --git a/docs/changelog/39328.yaml b/docs/changelog/39328.yaml new file mode 100644 index 0000000000000..04d8002aeaf63 --- /dev/null +++ b/docs/changelog/39328.yaml @@ -0,0 +1,12 @@ +pr: 39328 +issues: [] +area: Aggregations +type: breaking +summary: Remove `MovingAverage` pipeline aggregation +versions: + - v8.0.0 +breaking: + notable: false + title: Remove `MovingAverage` pipeline aggregation + anchor: remove_movingaverage_pipeline_aggregation + body: This was deprecated in 6.4.0 and for the entirety of 7.0. Removed in 8.0 :) diff --git a/docs/changelog/39346.yaml b/docs/changelog/39346.yaml new file mode 100644 index 0000000000000..9ae9014a7d49c --- /dev/null +++ b/docs/changelog/39346.yaml @@ -0,0 +1,8 @@ +pr: 39346 +issues: + - 39073 +area: Snapshot/Restore +type: enhancement +summary: Unify blob store compress setting +versions: + - v8.0.0 diff --git a/docs/changelog/39450.yaml b/docs/changelog/39450.yaml new file mode 100644 index 0000000000000..30f17b77038a0 --- /dev/null +++ b/docs/changelog/39450.yaml @@ -0,0 +1,15 @@ +pr: 39450 +issues: [] +area: Aggregations +type: breaking +summary: Remove deprecated `_time` and `_term` sort orders +versions: + - v8.0.0 +breaking: + notable: false + title: Remove deprecated `_time` and `_term` sort orders + anchor: remove_deprecated_time_and_term_sort_orders + body: >- + Deprecated in 6.0, time to go :) + + This isn't really a bugfix so I feel like we missed the boat on 7.0? Just target 8.0? diff --git a/docs/changelog/39459.yaml b/docs/changelog/39459.yaml new file mode 100644 index 0000000000000..45589d449d226 --- /dev/null +++ b/docs/changelog/39459.yaml @@ -0,0 +1,8 @@ +pr: 39459 +issues: + - 39350 +area: Engine +type: upgrade +summary: Re-enable backwards compatibility +versions: + - v8.0.0 diff --git a/docs/changelog/39593.yaml b/docs/changelog/39593.yaml new file mode 100644 index 0000000000000..63236fedc8bd1 --- /dev/null +++ b/docs/changelog/39593.yaml @@ -0,0 +1,26 @@ +pr: 39593 +issues: + - 39163 +area: Features/ILM+SLM +type: breaking, enhancement +summary: Add lower bound on `poll_interval` +versions: + - v8.0.0 +breaking: + notable: false + title: Add lower bound on `poll_interval` + anchor: add_lower_bound_on_poll_interval_ + body: >- + #39163 + + Add lower bound on poll_interval + + $ curl -H "Content-Type: application/json" -X PUT -d '{ + "persistent": { + "indices.lifecycle.poll_interval": "1ms", + "logger.org.elasticsearch.xpack.indexlifecycle": "TRACE" + } + }' localhost:9200/_cluster/settings + + + {"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"failed to parse value [1ms] for setting [indices.lifecycle.poll_interval], must be >= [1s]"}],"type":"illegal_argument_exception","reason":"failed to parse value [1ms] for setting [indices.lifecycle.poll_interval], must be >= [1s]"},"status":400} diff --git a/docs/changelog/39747.yaml b/docs/changelog/39747.yaml new file mode 100644 index 0000000000000..75fe1197adce9 --- /dev/null +++ b/docs/changelog/39747.yaml @@ -0,0 +1,8 @@ +pr: 39747 +issues: + - 39525 +area: Highlighting +type: bug +summary: Bug fix for `AnnotatedTextHighlighter` - port of 39525 +versions: + - v8.0.0 diff --git a/docs/changelog/40033.yaml b/docs/changelog/40033.yaml new file mode 100644 index 0000000000000..842d693d65cf2 --- /dev/null +++ b/docs/changelog/40033.yaml @@ -0,0 +1,15 @@ +pr: 40033 +issues: [] +area: Snapshot/Restore +type: breaking, bug +summary: Blob Store compress default to true +versions: + - v8.0.0 +breaking: + notable: false + title: Blob Store compress default to true + anchor: blob_store_compress_default_to_true + body: |- + Changed default of compress setting from false to true for blob store + repositories. This aligns the code with documentation and also seems + like the better default. diff --git a/docs/changelog/40379.yaml b/docs/changelog/40379.yaml new file mode 100644 index 0000000000000..65168315e58b4 --- /dev/null +++ b/docs/changelog/40379.yaml @@ -0,0 +1,8 @@ +pr: 40379 +issues: + - 40335 +area: Features/CAT APIs, Recovery +type: bug +summary: Fix cat recovery display of bytes fields +versions: + - v8.0.0 diff --git a/docs/changelog/40419.yaml b/docs/changelog/40419.yaml new file mode 100644 index 0000000000000..8ca76a189f480 --- /dev/null +++ b/docs/changelog/40419.yaml @@ -0,0 +1,28 @@ +pr: 40419 +issues: + - 37863 +area: Search +type: breaking +summary: Make remote cluster resolution stricter +versions: + - v8.0.0 +breaking: + notable: false + title: Make remote cluster resolution stricter + anchor: make_remote_cluster_resolution_stricter + body: >- + Remote cluster resolution is currently lenient, to support local + + indices that may contain : in their name. From 8.0 on, there can no + + longer be indices in the cluster that contain : in their name, hence + + we can make remote cluster resolution stricter. Instead of treating + + as local any index expression containing a : whenever there is no corresponding + + matching remote cluster registered, we now throw a + + NoSuchRemoteClusterException. + + Closes #37863 diff --git a/docs/changelog/40496.yaml b/docs/changelog/40496.yaml new file mode 100644 index 0000000000000..b704c6019a2f8 --- /dev/null +++ b/docs/changelog/40496.yaml @@ -0,0 +1,17 @@ +pr: 40496 +issues: [] +area: Security +type: breaking, enhancement +summary: Remove obsolete security settings +versions: + - v8.0.0 +breaking: + notable: false + title: Remove obsolete security settings + anchor: remove_obsolete_security_settings + body: |- + 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. diff --git a/docs/changelog/40878.yaml b/docs/changelog/40878.yaml new file mode 100644 index 0000000000000..7a77324c7bbb5 --- /dev/null +++ b/docs/changelog/40878.yaml @@ -0,0 +1,20 @@ +pr: 40878 +issues: + - 40755 +area: Infra/Circuit Breakers +type: breaking, enhancement +summary: Fixed synchronizing inflight breaker with internal variable +versions: + - v8.0.0 +breaking: + notable: false + title: Fixed synchronizing inflight breaker with internal variable + anchor: fixed_synchronizing_inflight_breaker_with_internal_variable + body: >- + Tested http://localhost:9200/_nodes/stats/breaker + + and found out that the in flight requests are divided with underscores. + + This is wrong some versions already. + + This is a replacement of pull request #40755 and corrects the printed value in elasticsearch. diff --git a/docs/changelog/40952.yaml b/docs/changelog/40952.yaml new file mode 100644 index 0000000000000..f272c1179c512 --- /dev/null +++ b/docs/changelog/40952.yaml @@ -0,0 +1,7 @@ +pr: 40952 +issues: [] +area: Engine +type: upgrade +summary: Upgrade to lucene 8.1.0-snapshot-e460356abe +versions: + - v8.0.0 diff --git a/docs/changelog/41007.yaml b/docs/changelog/41007.yaml new file mode 100644 index 0000000000000..9fe976808daa3 --- /dev/null +++ b/docs/changelog/41007.yaml @@ -0,0 +1,17 @@ +pr: 41007 +issues: + - 40303 +area: Reindex +type: breaking, feature +summary: Reindex from Remote encoding +versions: + - v8.0.0 +breaking: + notable: false + title: Reindex from Remote encoding + anchor: reindex_from_remote_encoding + body: |- + 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 diff --git a/docs/changelog/41011.yaml b/docs/changelog/41011.yaml new file mode 100644 index 0000000000000..4fe6acf7425f2 --- /dev/null +++ b/docs/changelog/41011.yaml @@ -0,0 +1,39 @@ +pr: 41011 +issues: + - 39841 +area: Search +type: breaking +summary: Parse empty first line in msearch request body as action metadata +versions: + - v8.0.0 +breaking: + notable: false + title: Parse empty first line in msearch request body as action metadata + anchor: parse_empty_first_line_in_msearch_request_body_as_action_metadata + body: >- + It looks like when parsing the msearch request body, we allow for the first + line to be empty, yet that causes some different treatment for the first + line that ends up requiring the action metadata line, while all other lines + don't as they can be just empty. + + With this change we properly accept the following which we would otherwise reject due to the first line being empty: + + + { "query": {"match_all": {}}} + + + { "query": {"match_all": {}}} + + + but we stop accepting the following (note the empty line before the first action metadata line: + + + {} + + { "query": {"match_all": {}}} + + + { "query": {"match_all": {}}} + + + Relates to #39841 diff --git a/docs/changelog/41124.yaml b/docs/changelog/41124.yaml new file mode 100644 index 0000000000000..9d0971dc38b6e --- /dev/null +++ b/docs/changelog/41124.yaml @@ -0,0 +1,9 @@ +pr: 41124 +issues: + - 41090 + - 41091 +area: Machine Learning +type: bug +summary: Checking if p-tasks metadata is null before updating state +versions: + - v8.0.0 diff --git a/docs/changelog/41347.yaml b/docs/changelog/41347.yaml new file mode 100644 index 0000000000000..2151e0af0bc14 --- /dev/null +++ b/docs/changelog/41347.yaml @@ -0,0 +1,7 @@ +pr: 41347 +issues: [] +area: Search +type: enhancement +summary: Make 0 as invalid value for `min_children` in `has_child` query +versions: + - v8.0.0 diff --git a/docs/changelog/41492.yaml b/docs/changelog/41492.yaml new file mode 100644 index 0000000000000..1af0b2ea72be2 --- /dev/null +++ b/docs/changelog/41492.yaml @@ -0,0 +1,8 @@ +pr: 41492 +issues: + - 40052 +area: Infra/REST API +type: bug +summary: "Fix: added missing skip" +versions: + - v8.0.0 diff --git a/docs/changelog/41502.yaml b/docs/changelog/41502.yaml new file mode 100644 index 0000000000000..e5769c111ee86 --- /dev/null +++ b/docs/changelog/41502.yaml @@ -0,0 +1,22 @@ +pr: 41502 +issues: + - 39845 + - 35928 +area: Rollup +type: breaking, enhancement +summary: "`RollupStart` endpoint should return OK if job already started" +versions: + - v8.0.0 +breaking: + notable: false + title: "`RollupStart` endpoint should return OK if job already started" + anchor: _rollupstart_endpoint_should_return_ok_if_job_already_started + body: >- + If a job is started or indexing, RollupStart should always return a success + (200 OK) response since the job is, in fact, started + + This also removes some no-longer-needed serialization version checking on stop job (only needed for 6.x and 7.x) + + I'm not sure if this should be backported to 7.x. It's technically a breaking change, but also one that is unlikely to be noticed. It would only break someone if they were relying on the second invocation of the API to throw the exception so they could do something else. Thoughts? I also don't think this is critical, so if this is 8.0+ only that seems fine too. + + Closes #39845 and #35928 diff --git a/docs/changelog/41560.yaml b/docs/changelog/41560.yaml new file mode 100644 index 0000000000000..15a15adcbb97d --- /dev/null +++ b/docs/changelog/41560.yaml @@ -0,0 +1,16 @@ +pr: 41560 +issues: + - 41164 +area: Analysis +type: breaking +summary: Cleanup versioned deprecations in analysis +versions: + - v8.0.0 +breaking: + notable: false + title: Cleanup versioned deprecations in analysis + anchor: cleanup_versioned_deprecations_in_analysis + body: |- + This commit removes versioned logic in analyzer creation that is no + longer relevant for 8.0. + relates #41164 diff --git a/docs/changelog/41620.yaml b/docs/changelog/41620.yaml new file mode 100644 index 0000000000000..2822330d84d80 --- /dev/null +++ b/docs/changelog/41620.yaml @@ -0,0 +1,8 @@ +pr: 41620 +issues: + - 41478 +area: Packaging +type: bug +summary: Suppress illegal access in plugin install +versions: + - v8.0.0 diff --git a/docs/changelog/41640.yaml b/docs/changelog/41640.yaml new file mode 100644 index 0000000000000..daa022851716c --- /dev/null +++ b/docs/changelog/41640.yaml @@ -0,0 +1,12 @@ +pr: 41640 +issues: [] +area: Search +type: breaking +summary: Removes typed endpoint from search and related APIs +versions: + - v8.0.0 +breaking: + notable: false + title: Removes typed endpoint from search and related APIs + anchor: removes_typed_endpoint_from_search_and_related_apis + body: "" diff --git a/docs/changelog/41676.yaml b/docs/changelog/41676.yaml new file mode 100644 index 0000000000000..80620f3a5952e --- /dev/null +++ b/docs/changelog/41676.yaml @@ -0,0 +1,12 @@ +pr: 41676 +issues: [] +area: Mapping +type: breaking +summary: Removes typed URLs from mapping APIs +versions: + - v8.0.0 +breaking: + notable: false + title: Removes typed URLs from mapping APIs + anchor: removes_typed_urls_from_mapping_apis + body: "" diff --git a/docs/changelog/41808.yaml b/docs/changelog/41808.yaml new file mode 100644 index 0000000000000..5ef442feecd62 --- /dev/null +++ b/docs/changelog/41808.yaml @@ -0,0 +1,9 @@ +pr: 41808 +issues: + - 41385 + - 38646 +area: TLS +type: enhancement +summary: Update TLS ciphers and protocols for JDK 11 +versions: + - v8.0.0 diff --git a/docs/changelog/41972.yaml b/docs/changelog/41972.yaml new file mode 100644 index 0000000000000..8d47164dc43f5 --- /dev/null +++ b/docs/changelog/41972.yaml @@ -0,0 +1,8 @@ +pr: 41972 +issues: + - 41970 +area: Aggregations +type: bug +summary: Throw exception if legacy interval cannot be parsed in `DateIntervalWrapper` +versions: + - v8.0.0 diff --git a/docs/changelog/42090.yaml b/docs/changelog/42090.yaml new file mode 100644 index 0000000000000..e3db134a4a2a0 --- /dev/null +++ b/docs/changelog/42090.yaml @@ -0,0 +1,395 @@ +pr: 42090 +issues: + - 41799 + - 15151 + - 41210 +area: Snapshot/Restore +type: breaking, enhancement +summary: Get snapshots support for multiple repositories +versions: + - v8.0.0 +breaking: + notable: false + title: Get snapshots support for multiple repositories + anchor: get_snapshots_support_for_multiple_repositories + body: >- + Description + + This commit adds multiple repositories support to get snapshots request. + + If some repository throws an exception this method does not fail fast instead, it returns results for all repositories. + + This PR is opened in favour of #41799, because we decided to change the response format in a non-BwC manner. It makes sense to read discussion of the aforementioned PR. + + This is the continuation of work done here #15151. + + _snapshot API + + Now the following requests are supported: + + GET /_snapshot/[_all | * | repo* | repo1,repo2]/[_all | * | snap* | snap1,snap2] + + + This commit breaks BwC of response format for this request, that's why this PR is not backported to 7.x. For the response format see examples sections. + + _cat/snapshots API + + Cat snapshot API also supports multiple repositories now. + + GET /_cat/snapshots/[_all | * | repo* | repo1,repo2] + + + In the table returned new column named "repository" is added. If some repo fails with an exception, this method just reports that some repos have failed. See examples section. + + GET /_cat/snapshots + + + is also supported and will return all snapshots for all repositories. + + Interestingly enough, the previous implementation also was registering /_cat/snapshots filter but a request to this endpoint always resulted in + + { + "error": { + "root_cause": [ + { + "type": "action_request_validation_exception", + "reason": "Validation Failed: 1: repository is missing;" + } + ], + "type": "action_request_validation_exception", + "reason": "Validation Failed: 1: repository is missing;" + }, + "status": 400 + } + + + Implementation + + Technically, TransportGetSnapshotsAction calls TransportGetRepositoriesAction which resolves repo names and wildcards in request to concrete repository names. + + After that, we submit tasks in parallel for all returned repositories and are using the already implemented algorithm to get matching snapshots in the repositories. + + In terms of the transport level protocol, 2 classes are changed: + + + GetSnapshotsRequest now accepts the list of repository names (including wildcards) instead of single repo name. + + GetSnapshotsResponse is changed in non-BwC manner. + + + In terms of REST protocol, 2 classes are changed: + + + SnapshotRequestsConverters.getSnapshots now can understand the list of repository names in GetSnapshotRequest and adds it as comma separated list to the request path. + + RestGetSnapshotsAction can now parse the comma-separated list of the repo names. + + GetSnapshotsResponse XContent serialization is completely changed. + + + RestSnapshotAction which is responsible for handling cat API for the snapshots is extended with repository field as well. + + Testing + + + SharedClusterSnapshotRestoreIT.testGetSnapshotsMultipleRepos tests that multiple repositories and wildcard work fine on transport level. + + SnapshotRequestConvertersTests.getSnapshots tests that high-level REST client correctly sends the request when multiple repositories are used in the request. + + SnapshotIT.testGetSnapshots tests getting 2 snapshots from 2 different repositories using high-level REST client. + + Some BwC tests, because we need compatibility between 7.latest and 8 (TBD) + + + Documentation + + Seems that it makes sense to make adjustments to the following documentation pages: + + + cat-snapshots + + modules-snapshots + + + Both of them should talk about the ability to specify multiple repositories when querying the snapshots (TBD). + + Since it's breaking change also breaking changes doc should be extended (TBD). + + Examples + + Working with GetSnapshotsResponse + + Consider you have response. + + First of all, you can check if there are any failures response.isFailed(). + + If you were using wildcard/regex for repository names, you can use response.getRepositories to get the set of repositories. + + If you know particular repository name, you can just do response.getSnapshots(repoName) and it will return the list of SnapshotInfo for the repository or it throws ElasticsearchException. So all methods that previously called response.getSnapshots() can now achieve the same behaviour by just passing the repoName. + + Finally, you can get a map of successful and failed responses using getSuccessfulResponses and getFailedResponses. + + _snapshot API + + Consider you have 2 repositories: + + PUT _snapshot/repo1 + + PUT _snapshot/repo2 + + + And you have one snapshot in each repository: + + PUT _snapshot/repo1/snap1 + + PUT _snapshot/repo2/snap2 + + + Now the following commands + + GET _snapshot/[* | _all | repo*]/[* | _all | snap*] + + + will give you the same output + + { + "responses": [ + { + "repository": "repo2", + "snapshots": [ + { + "snapshot": "snap2", + "uuid": "XgGZx_QjRc6J5YkbbDWsdQ", + "version_id": 8000099, + "version": "8.0.0", + "indices": [], + "include_global_state": true, + "state": "SUCCESS", + "start_time": "2019-05-10T17:02:02.695Z", + "start_time_in_millis": 1557507722695, + "end_time": "2019-05-10T17:02:02.729Z", + "end_time_in_millis": 1557507722729, + "duration_in_millis": 34, + "failures": [], + "shards": { + "total": 0, + "failed": 0, + "successful": 0 + } + } + ] + }, + { + "repository": "repo1", + "snapshots": [ + { + "snapshot": "snap1", + "uuid": "cEzdqUKxQ5G6MyrJAcYwmA", + "version_id": 8000099, + "version": "8.0.0", + "indices": [], + "include_global_state": true, + "state": "SUCCESS", + "start_time": "2019-05-10T17:01:57.868Z", + "start_time_in_millis": 1557507717868, + "end_time": "2019-05-10T17:01:57.909Z", + "end_time_in_millis": 1557507717909, + "duration_in_millis": 41, + "failures": [], + "shards": { + "total": 0, + "failed": 0, + "successful": 0 + } + } + ] + } + ] + } + + + Responses are currently not sorted by repository name. However, SnapshotInfos are still sorted by startDate and then by snapshotId. + + The following request + + GET _snapshot/[* | _all | repo*]/snap1 + + + results in + + { + "responses": [ + { + "repository": "repo1", + "snapshots": [ + { + "snapshot": "snap1", + "uuid": "cEzdqUKxQ5G6MyrJAcYwmA", + "version_id": 8000099, + "version": "8.0.0", + "indices": [], + "include_global_state": true, + "state": "SUCCESS", + "start_time": "2019-05-10T17:01:57.868Z", + "start_time_in_millis": 1557507717868, + "end_time": "2019-05-10T17:01:57.909Z", + "end_time_in_millis": 1557507717909, + "duration_in_millis": 41, + "failures": [], + "shards": { + "total": 0, + "failed": 0, + "successful": 0 + } + } + ] + }, + { + "repository": "repo2", + "error": { + "root_cause": [ + { + "type": "snapshot_missing_exception", + "reason": "[repo2:snap1] is missing" + } + ], + "type": "snapshot_missing_exception", + "reason": "[repo2:snap1] is missing" + } + } + ] + } + + + because snap1 exists in repo1, but does not exist in repo2. + + This is an example of partial failure. + + Note that HTTP status code is 200 OK, despite partial failure. + + Even with full failure status code will be 200 OK. + + Currently, successful repositories are always reported on top. + + If you specify ignore_unavailable flag: + + GET _snapshot/[* | _all | repo*]/snap1?ignore_unavailable=true + + + And get the following response: + + { + "responses": [ + { + "repository": "repo2", + "snapshots": [] + }, + { + "repository": "repo1", + "snapshots": [ + { + "snapshot": "snap1", + "uuid": "cEzdqUKxQ5G6MyrJAcYwmA", + "version_id": 8000099, + "version": "8.0.0", + "indices": [], + "include_global_state": true, + "state": "SUCCESS", + "start_time": "2019-05-10T17:01:57.868Z", + "start_time_in_millis": 1557507717868, + "end_time": "2019-05-10T17:01:57.909Z", + "end_time_in_millis": 1557507717909, + "duration_in_millis": 41, + "failures": [], + "shards": { + "total": 0, + "failed": 0, + "successful": 0 + } + } + ] + } + ] + } + + + If you specify missing repository in the request + + GET _snapshot/repo1,repo2,repo3/snap1 + + + You get top-level error: + + { + "error": { + "root_cause": [ + { + "type": "repository_missing_exception", + "reason": "[repo3] missing" + } + ], + "type": "repository_missing_exception", + "reason": "[repo3] missing" + }, + "status": 404 + } + + + _cat/snapshot API + + Consider you have 2 repositories: + + PUT _snapshot/repo1 + + PUT _snapshot/repo2 + + + And you have one snapshot in each repository: + + PUT _snapshot/repo1/snap1 + + PUT _snapshot/repo2/snap2 + + + Now you can get all the snapshots using any of this API calls: + + GET _cat/snapshot + + GET _cat/snapshot/_all + + GET _cat/snapshot/* + + GET _cat/snapshot/repo* + + GET _cat/snapshot/repo1,repo2 + + + The response will contain the repository name: + + snap2 repo2 SUCCESS 1557507722 17:02:02 1557507722 17:02:02 34ms 0 0 0 0 + + snap1 repo1 SUCCESS 1557507717 17:01:57 1557507717 17:01:57 41ms 0 0 0 0 + + + Currently snapshots are not sorted by repo name. + + If there is an unexpected error for at least one of the repositories you will get the following + + response: + + { + "error": { + "root_cause": [ + { + "type": "exception", + "reason": "Repositories [repo1,repo2] failed to retrieve snapshots" + } + ], + "type": "exception", + "reason": "Repositories [repo1,repo2] failed to retrieve snapshots" + }, + "status": 500 + } + + + Closes #41210 diff --git a/docs/changelog/42112.yaml b/docs/changelog/42112.yaml new file mode 100644 index 0000000000000..bba05c6f07c80 --- /dev/null +++ b/docs/changelog/42112.yaml @@ -0,0 +1,16 @@ +pr: 42112 +issues: [] +area: Search +type: breaking-java +summary: Removes types from `SearchRequest` and `QueryShardContext` +versions: + - v8.0.0 +breaking: + notable: false + title: Removes types from `SearchRequest` and `QueryShardContext` + anchor: removes_types_from_searchrequest_and_queryshardcontext_ + body: >- + This change will remove the notion of types completely from the Search API + internals. + + For classes that are serialised (such as SearchRequest, IdsQuery, ShardLocalSearchRequest) we need to check for the wire version and deal with the types serialisation if the other node is <8.0.0 diff --git a/docs/changelog/42155.yaml b/docs/changelog/42155.yaml new file mode 100644 index 0000000000000..211b1aa21cd99 --- /dev/null +++ b/docs/changelog/42155.yaml @@ -0,0 +1,7 @@ +pr: 42155 +issues: [] +area: TLS +type: enhancement +summary: Add `ChaCha20` TLS ciphers on Java 12+ +versions: + - v8.0.0 diff --git a/docs/changelog/42174.yaml b/docs/changelog/42174.yaml new file mode 100644 index 0000000000000..d89e7608f6fb0 --- /dev/null +++ b/docs/changelog/42174.yaml @@ -0,0 +1,15 @@ +pr: 42174 +issues: [] +area: Security +type: breaking +summary: Remove the migrate tool +versions: + - v8.0.0 +breaking: + notable: false + title: Remove the migrate tool + anchor: remove_the_migrate_tool + body: |- + This commit removes the deprecated migrate tool which was used to + migrate users from the file realm to native realm when the native realm + was first created. diff --git a/docs/changelog/42179.yaml b/docs/changelog/42179.yaml new file mode 100644 index 0000000000000..9aeb61b340235 --- /dev/null +++ b/docs/changelog/42179.yaml @@ -0,0 +1,8 @@ +pr: 42179 +issues: + - 42154 +area: Aggregations +type: bug +summary: Fix `TopHitsAggregationBuilder` adding duplicate `_score` sort clauses +versions: + - v8.0.0 diff --git a/docs/changelog/42198.yaml b/docs/changelog/42198.yaml new file mode 100644 index 0000000000000..60f5a0dd3562c --- /dev/null +++ b/docs/changelog/42198.yaml @@ -0,0 +1,13 @@ +pr: 42198 +issues: + - 41059 +area: Search +type: breaking +summary: Removes type from `TermVectors` APIs +versions: + - v8.0.0 +breaking: + notable: false + title: Removes type from `TermVectors` APIs + anchor: removes_type_from_termvectors_apis + body: "Relates to #41059" diff --git a/docs/changelog/42202.yaml b/docs/changelog/42202.yaml new file mode 100644 index 0000000000000..167742590debc --- /dev/null +++ b/docs/changelog/42202.yaml @@ -0,0 +1,12 @@ +pr: 42202 +issues: [] +area: Infra/Core +type: breaking-java +summary: Remove transport client from xpack +versions: + - v8.0.0 +breaking: + notable: false + title: Remove transport client from xpack + anchor: remove_transport_client_from_xpack + body: his commit removes support for the transport client from xpack. diff --git a/docs/changelog/42253.yaml b/docs/changelog/42253.yaml new file mode 100644 index 0000000000000..63a297707550c --- /dev/null +++ b/docs/changelog/42253.yaml @@ -0,0 +1,10 @@ +pr: 42253 +issues: + - 42240 + - 42242 + - 42251 +area: Unknown +type: UNKNOWN +summary: Add 7.1.1 and 6.8.1 versions +versions: + - v8.0.0 diff --git a/docs/changelog/42288.yaml b/docs/changelog/42288.yaml new file mode 100644 index 0000000000000..9a411e86774e9 --- /dev/null +++ b/docs/changelog/42288.yaml @@ -0,0 +1,8 @@ +pr: 42288 +issues: + - 889 +area: Transform +type: UNKNOWN +summary: Documentation for Data Frame Analytics high-level REST client +versions: + - v8.0.0 diff --git a/docs/changelog/42333.yaml b/docs/changelog/42333.yaml new file mode 100644 index 0000000000000..f59db2d93262c --- /dev/null +++ b/docs/changelog/42333.yaml @@ -0,0 +1,17 @@ +pr: 42333 +issues: + - 41926 + - 41267 +area: Mapping +type: breaking +summary: Remove support for chained multi-fields. +versions: + - v8.0.0 +breaking: + notable: false + title: Remove support for chained multi-fields. + anchor: remove_support_for_chained_multi_fields_ + body: |- + Follow-up to #41926, where we deprecated support for multi-fields within + multi-fields. + Addresses #41267. diff --git a/docs/changelog/42359.yaml b/docs/changelog/42359.yaml new file mode 100644 index 0000000000000..26cb4ef7fd87e --- /dev/null +++ b/docs/changelog/42359.yaml @@ -0,0 +1,16 @@ +pr: 42359 +issues: + - 42213 +area: Snapshot/Restore +type: breaking-java +summary: Remove deprecated Repository methods +versions: + - v8.0.0 +breaking: + notable: false + title: Remove deprecated Repository methods + anchor: remove_deprecated_repository_methods + body: |- + We deprecated restoreShard and snapshotShard in #42213 + This change removes the deprecated methods and their usage and adds + a note in the migration docs. diff --git a/docs/changelog/42381.yaml b/docs/changelog/42381.yaml new file mode 100644 index 0000000000000..0c85a39ab11f8 --- /dev/null +++ b/docs/changelog/42381.yaml @@ -0,0 +1,22 @@ +pr: 42381 +issues: + - 33413 + - 38556 +area: Search +type: breaking +summary: Remove deprecated `search.remote` settings +versions: + - v8.0.0 +breaking: + notable: false + title: Remove deprecated `search.remote` settings + anchor: remove_deprecated_search_remote_settings + body: >- + 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. + + Relates #33413 + + Relates #38556 diff --git a/docs/changelog/42428.yaml b/docs/changelog/42428.yaml new file mode 100644 index 0000000000000..5db7f62a90436 --- /dev/null +++ b/docs/changelog/42428.yaml @@ -0,0 +1,22 @@ +pr: 42428 +issues: + - 42426 +area: Infra/Core +type: breaking +summary: Remove `node.max_local_storage_nodes` +versions: + - v8.0.0 +breaking: + notable: false + title: Remove `node.max_local_storage_nodes` + anchor: remove_node_max_local_storage_nodes_ + body: >- + 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 prefered 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. + + A follow-up will move the default data path from ${data.paths}/nodes/0 to ${data.paths} + + Relates to #42426 diff --git a/docs/changelog/42471.yaml b/docs/changelog/42471.yaml new file mode 100644 index 0000000000000..044a3774c9ad7 --- /dev/null +++ b/docs/changelog/42471.yaml @@ -0,0 +1,17 @@ +pr: 42471 +issues: [] +area: Client +type: breaking-java +summary: Remove `SecurityClient` from x-pack +versions: + - v8.0.0 +breaking: + notable: false + title: Remove `SecurityClient` from x-pack + anchor: remove_securityclient_from_x_pack + body: |- + This commit removes the SecurityClient class from x-pack. This client + class is a relic of the transport client, which is in the process of + being removed. Some tests were changed to use the high level rest + client and others use a client directly without the security client + wrapping it. diff --git a/docs/changelog/42489.yaml b/docs/changelog/42489.yaml new file mode 100644 index 0000000000000..54ae4fa0f77e8 --- /dev/null +++ b/docs/changelog/42489.yaml @@ -0,0 +1,18 @@ +pr: 42489 +issues: [] +area: Infra/Core +type: breaking +summary: Remove "nodes/0" folder prefix from data path +versions: + - v8.0.0 +breaking: + notable: false + title: Remove "nodes/0" folder prefix from data path + anchor: remove_nodes_0_folder_prefix_from_data_path + body: >- + With the removal of node.max_local_storage_nodes, there is no need anymore + to keep the data in subfolders indexed by a node ordinal. This PR makes it + so that ES 8.0 will store data directly in $DATA_DIR instead of + $DATA_DIR/nodes/$nodeOrdinal. + + Upon startup, Elasticsearch will check to see if there is data in the old location, and automatically move it to the new location. This automatic migration only works if $nodeOrdinal is 0, i.e., multiple node instances have not previously run on the same data path, which required for node.max_local_storage_nodes to explicitly be configured. diff --git a/docs/changelog/42538.yaml b/docs/changelog/42538.yaml new file mode 100644 index 0000000000000..a3e753d415ee5 --- /dev/null +++ b/docs/changelog/42538.yaml @@ -0,0 +1,12 @@ +pr: 42538 +issues: [] +area: Infra/Core +type: breaking-java +summary: Remove the transport client +versions: + - v8.0.0 +breaking: + notable: false + title: Remove the transport client + anchor: remove_the_transport_client + body: This commit removes the transport client and all remaining uses in the code. diff --git a/docs/changelog/42654.yaml b/docs/changelog/42654.yaml new file mode 100644 index 0000000000000..a6101f9c83670 --- /dev/null +++ b/docs/changelog/42654.yaml @@ -0,0 +1,17 @@ +pr: 42654 +issues: + - 37096 +area: Search +type: breaking +summary: Remove `CommonTermsQuery` and `cutoff_frequency` param +versions: + - v8.0.0 +breaking: + notable: false + title: Remove `CommonTermsQuery` and `cutoff_frequency` param + anchor: remove_commontermsquery_and_cutoff_frequency_param + body: |- + Remove common query and cutoff_frequency parameter of + match and multi_match queries. Both have already been + deprecated in 7.x. + Closes: #37096 diff --git a/docs/changelog/42729.yaml b/docs/changelog/42729.yaml new file mode 100644 index 0000000000000..4fa533de0fa30 --- /dev/null +++ b/docs/changelog/42729.yaml @@ -0,0 +1,17 @@ +pr: 42729 +issues: [] +area: Infra/Core +type: breaking-java +summary: Remove `XPackClient` from x-pack +versions: + - v8.0.0 +breaking: + notable: false + title: Remove `XPackClient` from x-pack + anchor: remove_xpackclient_from_x_pack + body: |- + This commit removes the XPackClient class from x-pack. This class is a + relic of the TransportClient and simply a wrapper around it. Calls are + replaced with direct usage of a client. Additionally, the + XPackRestHandler class has been removed as it only served to provide + the XPackClient to implementing rest handlers. diff --git a/docs/changelog/42770.yaml b/docs/changelog/42770.yaml new file mode 100644 index 0000000000000..049f30bbd64f0 --- /dev/null +++ b/docs/changelog/42770.yaml @@ -0,0 +1,14 @@ +pr: 42770 +issues: [] +area: Features/Monitoring +type: breaking-java +summary: Remove `MonitoringClient` from x-pack +versions: + - v8.0.0 +breaking: + notable: false + title: Remove `MonitoringClient` from x-pack + anchor: remove_monitoringclient_from_x_pack + body: |- + This commit removes the monitoring client from x-pack. This class is a + relic of the TransportClient and was only used in a test. diff --git a/docs/changelog/42809.yaml b/docs/changelog/42809.yaml new file mode 100644 index 0000000000000..379a756ea9a8f --- /dev/null +++ b/docs/changelog/42809.yaml @@ -0,0 +1,21 @@ +pr: 42809 +issues: + - 27098 +area: Search +type: breaking +summary: "Remove deprecated sort options: `nested_path` and `nested_filter`" +versions: + - v8.0.0 +breaking: + notable: false + title: "Remove deprecated sort options: `nested_path` and `nested_filter`" + anchor: remove_deprecated_sort_options_nested_path_and_nested_filter_ + body: >- + 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 diff --git a/docs/changelog/42815.yaml b/docs/changelog/42815.yaml new file mode 100644 index 0000000000000..d6f9b4aabb7ba --- /dev/null +++ b/docs/changelog/42815.yaml @@ -0,0 +1,17 @@ +pr: 42815 +issues: [] +area: Features/Watcher +type: breaking-java +summary: Remove `WatcherClient` from x-pack +versions: + - v8.0.0 +breaking: + notable: false + title: Remove `WatcherClient` from x-pack + anchor: remove_watcherclient_from_x_pack + body: |- + This commit removes the WatcherClient and WatcherRestHandler from the + codebase. The WatcherClient was a convenience wrapper around the + transport client, which is being removed so the client no longer serves + a purpose. The WatcherRestHandler is no longer needed as its primary + purpose was to provide a WatcherClient to the implementing handlers. diff --git a/docs/changelog/42816.yaml b/docs/changelog/42816.yaml new file mode 100644 index 0000000000000..8a8f018e6d991 --- /dev/null +++ b/docs/changelog/42816.yaml @@ -0,0 +1,15 @@ +pr: 42816 +issues: [] +area: CCR +type: breaking-java +summary: Remove the `CcrClient` +versions: + - v8.0.0 +breaking: + notable: false + title: Remove the `CcrClient` + anchor: remove_the_ccrclient_ + body: |- + This commit removes the CcrClient class, which is a wrapper around the + transport client. The transport client is being removed so the client + is no longer needed. diff --git a/docs/changelog/42817.yaml b/docs/changelog/42817.yaml new file mode 100644 index 0000000000000..cbf03a3ce24bd --- /dev/null +++ b/docs/changelog/42817.yaml @@ -0,0 +1,15 @@ +pr: 42817 +issues: [] +area: Features/ILM+SLM +type: breaking-java +summary: Remove the ILMClient +versions: + - v8.0.0 +breaking: + notable: false + title: Remove the ILMClient + anchor: remove_the_ilmclient + body: |- + This commit removes the ILMClient class, which is a wrapper around the + transport client. This class is not used in the codebase and the + transport client is being removed. diff --git a/docs/changelog/43099.yaml b/docs/changelog/43099.yaml new file mode 100644 index 0000000000000..d3d1e6bf3943c --- /dev/null +++ b/docs/changelog/43099.yaml @@ -0,0 +1,7 @@ +pr: 43099 +issues: [] +area: Transform +type: bug +summary: "`[DataFrame]` Fix compile error in `DataFrameTransformProgressIT`" +versions: + - v8.0.0 diff --git a/docs/changelog/43108.yaml b/docs/changelog/43108.yaml new file mode 100644 index 0000000000000..ea1c1fb4b6e20 --- /dev/null +++ b/docs/changelog/43108.yaml @@ -0,0 +1,16 @@ +pr: 43108 +issues: [] +area: Machine Learning +type: breaking-java +summary: Remove the `MachineLearningClient` +versions: + - v8.0.0 +breaking: + notable: false + title: Remove the `MachineLearningClient` + anchor: remove_the_machinelearningclient_ + body: |- + The transport client has been removed and this follow up change removes + the MachineLearningClient as we no longer need this wrapper class since + we have a user facing MachineLearningClient within the rest high level + client. diff --git a/docs/changelog/43164.yaml b/docs/changelog/43164.yaml new file mode 100644 index 0000000000000..e6aa9c99baaa0 --- /dev/null +++ b/docs/changelog/43164.yaml @@ -0,0 +1,7 @@ +pr: 43164 +issues: [] +area: Infra/Core +type: enhancement +summary: Remove indices exists action +versions: + - v8.0.0 diff --git a/docs/changelog/43236.yaml b/docs/changelog/43236.yaml new file mode 100644 index 0000000000000..64058a09f7da2 --- /dev/null +++ b/docs/changelog/43236.yaml @@ -0,0 +1,15 @@ +pr: 43236 +issues: [] +area: TLS +type: breaking +summary: Remove the client transport profile filter +versions: + - v8.0.0 +breaking: + notable: false + title: Remove the client transport profile filter + anchor: remove_the_client_transport_profile_filter + body: |- + Now that the transport client has been removed, the client transport + profile filter can be removed from security. This filter prevented node + actions from being executed using a transport client. diff --git a/docs/changelog/43344.yaml b/docs/changelog/43344.yaml new file mode 100644 index 0000000000000..99ec8eef8af10 --- /dev/null +++ b/docs/changelog/43344.yaml @@ -0,0 +1,7 @@ +pr: 43344 +issues: [] +area: Infra/Core +type: enhancement +summary: Remove types exists action +versions: + - v8.0.0 diff --git a/docs/changelog/43373.yaml b/docs/changelog/43373.yaml new file mode 100644 index 0000000000000..e2914b917c809 --- /dev/null +++ b/docs/changelog/43373.yaml @@ -0,0 +1,21 @@ +pr: 43373 +issues: + - 41894 + - 24344 +area: Reindex +type: breaking, enhancement +summary: Reindex remove outer level size +versions: + - v8.0.0 +breaking: + notable: false + title: Reindex remove outer level size + anchor: reindex_remove_outer_level_size + body: |- + This commit finalizes the work done to rename size to max_docs in + reindex and update/delete by query. size is no longer supported in URL + or outer level body for the 3 APIs (though size in update/delete-by-query + will and has always been interpreted as scroll_size, it is not to be relied + upon). + Continuation of #41894 + Closes #24344 diff --git a/docs/changelog/43382.yaml b/docs/changelog/43382.yaml new file mode 100644 index 0000000000000..d6065ccab7f1a --- /dev/null +++ b/docs/changelog/43382.yaml @@ -0,0 +1,8 @@ +pr: 43382 +issues: + - 42612 +area: Reindex +type: enhancement +summary: Make reindexing managed by a persistent task +versions: + - v8.0.0 diff --git a/docs/changelog/43430.yaml b/docs/changelog/43430.yaml new file mode 100644 index 0000000000000..a01b9484b3579 --- /dev/null +++ b/docs/changelog/43430.yaml @@ -0,0 +1,7 @@ +pr: 43430 +issues: [] +area: Infra/Core +type: enhancement +summary: Remove aliases exist action +versions: + - v8.0.0 diff --git a/docs/changelog/43536.yaml b/docs/changelog/43536.yaml new file mode 100644 index 0000000000000..04d97c0a38655 --- /dev/null +++ b/docs/changelog/43536.yaml @@ -0,0 +1,7 @@ +pr: 43536 +issues: [] +area: Analysis +type: enhancement +summary: "[Docs] Move mentions of updateable synonyms flag" +versions: + - v8.0.0 diff --git a/docs/changelog/43558.yaml b/docs/changelog/43558.yaml new file mode 100644 index 0000000000000..563a67a636487 --- /dev/null +++ b/docs/changelog/43558.yaml @@ -0,0 +1,8 @@ +pr: 43558 +issues: + - 43547 +area: Snapshot/Restore +type: bug +summary: Fix GET /_snapshot/_all/_all if there are no repos +versions: + - v8.0.0 diff --git a/docs/changelog/43559.yaml b/docs/changelog/43559.yaml new file mode 100644 index 0000000000000..67e2f0ffab8c9 --- /dev/null +++ b/docs/changelog/43559.yaml @@ -0,0 +1,7 @@ +pr: 43559 +issues: [] +area: Analysis +type: enhancement +summary: Moving `reload_analyzers` endpoint to xpack +versions: + - v8.0.0 diff --git a/docs/changelog/43686.yaml b/docs/changelog/43686.yaml new file mode 100644 index 0000000000000..322aab4174453 --- /dev/null +++ b/docs/changelog/43686.yaml @@ -0,0 +1,17 @@ +pr: 43686 +issues: + - 41560 + - 43684 +area: Analysis +type: breaking +summary: Remove preconfigured `delimited_payload_filter` +versions: + - v8.0.0 +breaking: + notable: false + title: Remove preconfigured `delimited_payload_filter` + anchor: remove_preconfigured_delimited_payload_filter_ + body: |- + #41560 removed the delimited_payload_filter as part of a general + cleanup of pre-version 7 restrictions, but missed removing the + preconfigured version due to #43684. diff --git a/docs/changelog/43781.yaml b/docs/changelog/43781.yaml new file mode 100644 index 0000000000000..c55c5805a180e --- /dev/null +++ b/docs/changelog/43781.yaml @@ -0,0 +1,10 @@ +pr: 43781 +issues: + - 42409 + - 39169 +area: Features/Watcher +type: UNKNOWN +summary: "`SmokeTestWatcherWithSecurityIT:` Retry if failures searching + .watcher-history" +versions: + - v8.0.0 diff --git a/docs/changelog/44090.yaml b/docs/changelog/44090.yaml new file mode 100644 index 0000000000000..a84247d48bd96 --- /dev/null +++ b/docs/changelog/44090.yaml @@ -0,0 +1,23 @@ +pr: 44090 +issues: + - 40353 +area: Authentication +type: breaking +summary: Do not set a NameID format in Policy by default +versions: + - v8.0.0 +breaking: + notable: false + title: Do not set a NameID format in Policy by default + anchor: do_not_set_a_nameid_format_in_policy_by_default + body: |- + This commit changes the behavior of our SAML realm to not set a + Format element in the NameIDPolicy of a SAML Authentication + request if one has not been explicitly configured by the user + with nameid_format. We select to not include a format, rather + than setting it to + urn:oasis:names:tc:SAML:2.0:nameid-format:unspecified which would + have the same effect, in order to maximize interoperability with + IdP implementations. AllowCreate is not removed as this has a + default value (false) in the specification. + Relates: #40353 diff --git a/docs/changelog/44133.yaml b/docs/changelog/44133.yaml new file mode 100644 index 0000000000000..63570b006c64c --- /dev/null +++ b/docs/changelog/44133.yaml @@ -0,0 +1,9 @@ +pr: 44133 +issues: + - 43045 + - 44132 +area: Machine Learning +type: bug +summary: Relax the test assertion so that the test always passes +versions: + - v8.0.0 diff --git a/docs/changelog/44264.yaml b/docs/changelog/44264.yaml new file mode 100644 index 0000000000000..c31532e535dc2 --- /dev/null +++ b/docs/changelog/44264.yaml @@ -0,0 +1,48 @@ +pr: 44264 +issues: + - 41731 + - 41731 + - 21830 + - 44230 +area: Infra/Resiliency +type: breaking, bug +summary: Fail node containing ancient closed index +versions: + - v8.0.0 +breaking: + notable: false + title: Fail node containing ancient closed index + anchor: fail_node_containing_ancient_closed_index + body: >- + Today we fail the node at startup if it contains an index that is too old to + be + + compatible with the current version, unless that index is closed. If the index + + is closed then the node will start up and this puts us into a bad state: the + + index cannot be opened and must be reindexed using an earlier version, but we + + offer no way to get that index into a node running an earlier version so that + + it can be reindexed. Downgrading the node in-place is decidedly unsupported and + + cannot be expected to work since the node already started up and upgraded the + + rest of its metadata. Since #41731 we actively reject downgrades to versions ≥ + + v7.2.0 too. + + This commit prevents the node from starting in the presence of any too-old + + indices (closed or not). In particular, it does not write any upgraded metadata + + in this situation, increasing the chances an in-place downgrade might be + + successful. We still actively reject the downgrade using #41731, because we + + wrote the node metadata file before checking the index metadata, but at least + + there is a way to override this check. + + Relates #21830, #44230 diff --git a/docs/changelog/44642.yaml b/docs/changelog/44642.yaml new file mode 100644 index 0000000000000..ec4ee7fcad44a --- /dev/null +++ b/docs/changelog/44642.yaml @@ -0,0 +1,7 @@ +pr: 44642 +issues: [] +area: Infra/Logging +type: UNKNOWN +summary: Fix stats in slow logs to be a escaped JSON +versions: + - v8.0.0 diff --git a/docs/changelog/44752.yaml b/docs/changelog/44752.yaml new file mode 100644 index 0000000000000..7b71cd14c875a --- /dev/null +++ b/docs/changelog/44752.yaml @@ -0,0 +1,20 @@ +pr: 44752 +issues: + - 44691 + - 44616 +area: Machine Learning +type: breaking, deprecation +summary: Remove the ability to update datafeed's job_id. +versions: + - v8.0.0 +breaking: + notable: false + title: Remove the ability to update datafeed's job_id. + anchor: remove_the_ability_to_update_datafeed_s_job_id_ + body: >- + This PR is a followup to #44691. It disables the possibility to update + job_id on a datafeed. + + DatafeedUpdate.jobId field can be set in the _update request as long as it is the same as the current value of DatafeedConfig.jobId. + + Closes #44616 diff --git a/docs/changelog/44761.yaml b/docs/changelog/44761.yaml new file mode 100644 index 0000000000000..b27947d135017 --- /dev/null +++ b/docs/changelog/44761.yaml @@ -0,0 +1,24 @@ +pr: 44761 +issues: + - 43102 +area: Engine +type: breaking, bug +summary: Force Merge should reject requests with `only_expunge_deletes` and + `max_num_segments` set +versions: + - v8.0.0 +breaking: + notable: false + title: Force Merge should reject requests with `only_expunge_deletes` and + `max_num_segments` set + anchor: force_merge_should_reject_requests_with_only_expunge_deletes_and_max_num_segments_set + body: >- + This pull request 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. This PR 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. Once this is merged I'll open a follow up PR to add deprecation logging in 7.x. + + Closes #43102 diff --git a/docs/changelog/44894.yaml b/docs/changelog/44894.yaml new file mode 100644 index 0000000000000..8158d764bfe8b --- /dev/null +++ b/docs/changelog/44894.yaml @@ -0,0 +1,17 @@ +pr: 44894 +issues: + - 44889 +area: Infra/Core +type: breaking +summary: Limit processors by available processors +versions: + - v8.0.0 +breaking: + notable: false + title: Limit processors by available processors + anchor: limit_processors_by_available_processors + body: >- + This commit limits the processors setting to be more than the number of + available processors. + + Relates #44889 diff --git a/docs/changelog/44902.yaml b/docs/changelog/44902.yaml new file mode 100644 index 0000000000000..0345267421e4d --- /dev/null +++ b/docs/changelog/44902.yaml @@ -0,0 +1,8 @@ +pr: 44902 +issues: + - 37504 +area: Infra/REST API +type: bug +summary: "`RestController` should not consume request content" +versions: + - v8.0.0 diff --git a/docs/changelog/44905.yaml b/docs/changelog/44905.yaml new file mode 100644 index 0000000000000..03ce8bff83c99 --- /dev/null +++ b/docs/changelog/44905.yaml @@ -0,0 +1,9 @@ +pr: 44905 +issues: + - 44897 + - 29857 +area: Machine Learning +type: enhancement +summary: Change version in serialization code in `TimingStats.java` to 7.4.0 +versions: + - v8.0.0 diff --git a/docs/changelog/44929.yaml b/docs/changelog/44929.yaml new file mode 100644 index 0000000000000..e8171dbcebdac --- /dev/null +++ b/docs/changelog/44929.yaml @@ -0,0 +1,29 @@ +pr: 44929 +issues: + - 31020 + - 42538 + - 44667 +area: Network +type: breaking +summary: Remove client feature tracking +versions: + - v8.0.0 +breaking: + notable: false + title: Remove client feature tracking + anchor: remove_client_feature_tracking + body: >- + This commit removes the infrastructure for client feature tracking. We + introduced this functionality to support clients that do not necessarily + understand all the features that the server might support, for example, + customs in the cluster state provided by plugins that a client might not + have. This can arise in situations such as rolling upgrades from the OSS + distribution to the default distribution. With the removal of the transport + client, this infrastructure is no longer needed. This commit removes client + feature tracking from the server in 8.0.0. + + Relates #31020 + + Relates #42538 + + Relates #44667 diff --git a/docs/changelog/44982.yaml b/docs/changelog/44982.yaml new file mode 100644 index 0000000000000..f80051dc9d175 --- /dev/null +++ b/docs/changelog/44982.yaml @@ -0,0 +1,16 @@ +pr: 44982 +issues: + - 44917 + - 44725 +area: Features/ILM+SLM, Features/Java High Level REST Client +type: breaking-java +summary: Rename HLRC 'indexlifecycle' components to 'ilm' +versions: + - v8.0.0 +breaking: + notable: false + title: Rename HLRC 'indexlifecycle' components to 'ilm' + anchor: rename_hlrc_indexlifecycle_components_to_ilm_ + body: |- + Related to #44917 and #44725, this commit renames the HLRC components + for indexlifecycle to ilm. diff --git a/docs/changelog/45497.yaml b/docs/changelog/45497.yaml new file mode 100644 index 0000000000000..adde5002e7062 --- /dev/null +++ b/docs/changelog/45497.yaml @@ -0,0 +1,9 @@ +pr: 45497 +issues: + - 42612 + - 43187 +area: Reindex +type: enhancement +summary: Reindex search resiliency +versions: + - v8.0.0 diff --git a/docs/changelog/45586.yaml b/docs/changelog/45586.yaml new file mode 100644 index 0000000000000..09abdcd273dbe --- /dev/null +++ b/docs/changelog/45586.yaml @@ -0,0 +1,8 @@ +pr: 45586 +issues: + - 43260 +area: Infra/Core +type: bug +summary: "CLI tools: write errors to stderr instead of stdout" +versions: + - v8.0.0 diff --git a/docs/changelog/45675.yaml b/docs/changelog/45675.yaml new file mode 100644 index 0000000000000..f220899c2f13d --- /dev/null +++ b/docs/changelog/45675.yaml @@ -0,0 +1,12 @@ +pr: 45675 +issues: [] +area: Mapping +type: breaking +summary: Remove support for string in unmapped_type. +versions: + - v8.0.0 +breaking: + notable: false + title: Remove support for string in unmapped_type. + anchor: remove_support_for_string_in_unmapped_type_ + body: This deprecated option was added in 0d8e399 and can now be removed. diff --git a/docs/changelog/45735.yaml b/docs/changelog/45735.yaml new file mode 100644 index 0000000000000..09563812b6722 --- /dev/null +++ b/docs/changelog/45735.yaml @@ -0,0 +1,29 @@ +pr: 45735 +issues: + - 43453 +area: Search +type: breaking, enhancement +summary: Decouple shard allocation awareness from search and get requests +versions: + - v8.0.0 +breaking: + notable: false + title: Decouple shard allocation awareness from search and get requests + anchor: decouple_shard_allocation_awareness_from_search_and_get_requests + body: >- + 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 diff --git a/docs/changelog/45878.yaml b/docs/changelog/45878.yaml new file mode 100644 index 0000000000000..d98729c9b4de0 --- /dev/null +++ b/docs/changelog/45878.yaml @@ -0,0 +1,8 @@ +pr: 45878 +issues: + - 19069 +area: Infra/Core +type: UNKNOWN +summary: Remove `ExceptionHelper.detailedMessage` +versions: + - v8.0.0 diff --git a/docs/changelog/45892.yaml b/docs/changelog/45892.yaml new file mode 100644 index 0000000000000..36d64290f0394 --- /dev/null +++ b/docs/changelog/45892.yaml @@ -0,0 +1,23 @@ +pr: 45892 +issues: [] +area: TLS +type: breaking, enhancement +summary: Reject misconfigured/ambiguous SSL server config +versions: + - v8.0.0 +breaking: + notable: false + title: Reject misconfigured/ambiguous SSL server config + anchor: reject_misconfigured_ambiguous_ssl_server_config + body: |- + This commit makes it an error to start a node where either of the + server contexts (xpack.security.transport.ssl and + xpack.security.http.ssl) meet either of these conditions: + + The server lacks a certificate/key pair (i.e. neither + ssl.keystore.path nor ssl.certificate are configured) + The server has some ssl configuration, but ssl.enabled is not + specified. This new validation does not care whether ssl.enabled is + true or false (though other validation might), it simply makes it + an error to configure server SSL without being explicit about + whether to enable that configuration. diff --git a/docs/changelog/45905.yaml b/docs/changelog/45905.yaml new file mode 100644 index 0000000000000..ca7801b780a9e --- /dev/null +++ b/docs/changelog/45905.yaml @@ -0,0 +1,17 @@ +pr: 45905 +issues: + - 45855 +area: Infra/Core +type: breaking +summary: Remove processors setting +versions: + - v8.0.0 +breaking: + notable: false + title: Remove processors setting + anchor: remove_processors_setting + body: >- + The processors setting was deprecated in version 7.4.0 of Elasticsearch for + removal in Elasticsearch 8.0.0. This commit removes the processors setting. + + Relates #45855 diff --git a/docs/changelog/45940.yaml b/docs/changelog/45940.yaml new file mode 100644 index 0000000000000..4ba7de89356a7 --- /dev/null +++ b/docs/changelog/45940.yaml @@ -0,0 +1,17 @@ +pr: 45940 +issues: + - 45938 +area: Infra/Core +type: breaking +summary: Remove the pidfile setting +versions: + - v8.0.0 +breaking: + notable: false + title: Remove the pidfile setting + anchor: remove_the_pidfile_setting + body: >- + The pidfile setting was deprecated in version 7.4.0 of Elasticsearch for + removal in Elasticsearch 8.0.0. This commit removes the pidfile setting. + + Relates #45938 diff --git a/docs/changelog/45945.yaml b/docs/changelog/45945.yaml new file mode 100644 index 0000000000000..4d5d24a457cc2 --- /dev/null +++ b/docs/changelog/45945.yaml @@ -0,0 +1,32 @@ +pr: 45945 +issues: [] +area: Infra/REST API +type: breaking-java, enhancement +summary: Copy http headers to `ThreadContext` strictly +versions: + - v8.0.0 +breaking: + notable: false + title: Copy http headers to `ThreadContext` strictly + anchor: copy_http_headers_to_threadcontext_strictly + body: |- + Previous behavior while copying HTTP headers to the ThreadContext, + would allow multiple HTTP headers with the same name, handling only + the first occurrence and disregarding the rest of the values. This + can be confusing when dealing with multiple Headers as it is not + obvious which value is read and which ones are silently dropped. + According to RFC-7230, a client must not send multiple header fields + with the same field name in a HTTP message, unless the entire field + value for this header is defined as a comma separated list or this + specific header is a well-known exception. + This commits changes the behavior in order to be more compliant to + the aforementioned RFC by requiring the classes that implement + ActionPlugin to declare if a header can be multi-valued or not when + registering this header to be copied over to the ThreadContext in + ActionPlugin#getRestHeaders. + If the header is allowed to be multivalued, then all such headers + are read from the HTTP request and their values get concatenated in + a comma-separated string. + If the header is not allowed to be multivalued, and the HTTP + request contains multiple such Headers with different values, the + request is rejected with a 400 status. diff --git a/docs/changelog/45947.yaml b/docs/changelog/45947.yaml new file mode 100644 index 0000000000000..5f89a6ade7c55 --- /dev/null +++ b/docs/changelog/45947.yaml @@ -0,0 +1,20 @@ +pr: 45947 +issues: + - 45905 + - 45940 +area: Infra/Settings +type: breaking +summary: Forbid settings without a namespace +versions: + - v8.0.0 +breaking: + notable: false + title: Forbid settings without a namespace + anchor: forbid_settings_without_a_namespace + body: >- + This commit forbids settings that are not in any namespace, all setting + names must now contain a dot. + + Relates #45905 + + Relates #45940 diff --git a/docs/changelog/46055.yaml b/docs/changelog/46055.yaml new file mode 100644 index 0000000000000..cdca853d0b971 --- /dev/null +++ b/docs/changelog/46055.yaml @@ -0,0 +1,8 @@ +pr: 46055 +issues: + - 42612 +area: Reindex +type: enhancement +summary: Reindex restart from checkpoint +versions: + - v8.0.0 diff --git a/docs/changelog/46147.yaml b/docs/changelog/46147.yaml new file mode 100644 index 0000000000000..8979f0b03be25 --- /dev/null +++ b/docs/changelog/46147.yaml @@ -0,0 +1,22 @@ +pr: 46147 +issues: + - 45947 +area: Infra/Settings, Snapshot/Restore +type: breaking +summary: Remove insecure settings +versions: + - v8.0.0 +breaking: + notable: false + title: Remove insecure settings + anchor: remove_insecure_settings + body: >- + This commit removes the oxymoron of insecure secure settings from the code + base. In particular, we remove the ability to set the access_key and + secret_key for S3 repositories inside the repository definition (in the + cluster state). Instead, these settings now must be in the keystore. Thus, + it also removes some leniency where these settings could be placed in the + elasticsearch.yml, would not be rejected there, but would not be consumed + for any purpose. + + Relates #45947 diff --git a/docs/changelog/46327.yaml b/docs/changelog/46327.yaml new file mode 100644 index 0000000000000..ec6adb73a1e9d --- /dev/null +++ b/docs/changelog/46327.yaml @@ -0,0 +1,9 @@ +pr: 46327 +issues: + - 46257 + - 46324 +area: Aggregations +type: UNKNOWN +summary: Remove `Adjacency_matrix` setting +versions: + - v8.0.0 diff --git a/docs/changelog/46603.yaml b/docs/changelog/46603.yaml new file mode 100644 index 0000000000000..1703012d5df5b --- /dev/null +++ b/docs/changelog/46603.yaml @@ -0,0 +1,8 @@ +pr: 46603 +issues: + - 41830 +area: Infra/Settings +type: enhancement +summary: Fixed inconsistent Setting.exist() +versions: + - v8.0.0 diff --git a/docs/changelog/46702.yaml b/docs/changelog/46702.yaml new file mode 100644 index 0000000000000..d0c0a394ac344 --- /dev/null +++ b/docs/changelog/46702.yaml @@ -0,0 +1,8 @@ +pr: 46702 +issues: + - 46119 +area: Infra/Logging +type: UNKNOWN +summary: Refactor `ESLogMessage` to not define fields upfront +versions: + - v8.0.0 diff --git a/docs/changelog/46749.yaml b/docs/changelog/46749.yaml new file mode 100644 index 0000000000000..173f1903d7af8 --- /dev/null +++ b/docs/changelog/46749.yaml @@ -0,0 +1,8 @@ +pr: 46749 +issues: + - 46748 +area: Transform +type: UNKNOWN +summary: Muting tests for PR https://github.com/elastic/elasticsearch/pull/46414 +versions: + - v8.0.0 diff --git a/docs/changelog/46967.yaml b/docs/changelog/46967.yaml new file mode 100644 index 0000000000000..265ad5ce38d82 --- /dev/null +++ b/docs/changelog/46967.yaml @@ -0,0 +1,9 @@ +pr: 46967 +issues: + - 46763 + - 42612 +area: Reindex +type: enhancement +summary: Reindex v2 rethrottle sliced fix +versions: + - v8.0.0 diff --git a/docs/changelog/46983.yaml b/docs/changelog/46983.yaml new file mode 100644 index 0000000000000..175ef06646fc8 --- /dev/null +++ b/docs/changelog/46983.yaml @@ -0,0 +1,16 @@ +pr: 46983 +issues: + - 41059 +area: CRUD +type: breaking-java +summary: Remove types from `BulkRequest` +versions: + - v8.0.0 +breaking: + notable: false + title: Remove types from `BulkRequest` + anchor: remove_types_from_bulkrequest_ + body: |- + This commit removes types entirely from BulkRequest, both as a global + parameter and as individual entries on update/index/delete lines. + Relates to #41059 diff --git a/docs/changelog/47105.yaml b/docs/changelog/47105.yaml new file mode 100644 index 0000000000000..53e989f60c0f0 --- /dev/null +++ b/docs/changelog/47105.yaml @@ -0,0 +1,8 @@ +pr: 47105 +issues: + - 46119 +area: Infra/Logging +type: UNKNOWN +summary: Make Elasticsearch JSON logs ECS compliant +versions: + - v8.0.0 diff --git a/docs/changelog/47203.yaml b/docs/changelog/47203.yaml new file mode 100644 index 0000000000000..f1904070615c8 --- /dev/null +++ b/docs/changelog/47203.yaml @@ -0,0 +1,17 @@ +pr: 47203 +issues: + - 41059 +area: Engine +type: breaking +summary: Remove per-type indexing stats +versions: + - v8.0.0 +breaking: + notable: false + title: Remove per-type indexing stats + anchor: remove_per_type_indexing_stats + body: >- + With only a single type, the per-type filters for indexing stats are no + longer useful. + + Relates to #41059 diff --git a/docs/changelog/47207.yaml b/docs/changelog/47207.yaml new file mode 100644 index 0000000000000..de3f704479c24 --- /dev/null +++ b/docs/changelog/47207.yaml @@ -0,0 +1,19 @@ +pr: 47207 +issues: + - 41059 +area: Search +type: breaking +summary: Remove `type` query +versions: + - v8.0.0 +breaking: + notable: false + title: Remove `type` query + anchor: remove_type_query + body: >- + Running type queries in 7x already emits deprecation warnings. We can + remove it + + altogether in 8x. + + Part of #41059 diff --git a/docs/changelog/47364.yaml b/docs/changelog/47364.yaml new file mode 100644 index 0000000000000..0b76ff2510d3e --- /dev/null +++ b/docs/changelog/47364.yaml @@ -0,0 +1,25 @@ +pr: 47364 +issues: + - 41059 +area: Mapping +type: breaking-java +summary: Remove type filter from `GetMappings` API +versions: + - v8.0.0 +breaking: + notable: false + title: Remove type filter from `GetMappings` API + anchor: remove_type_filter_from_getmappings_api + body: >- + This commit removes the types filter from the GetMappings API, which is no + longer + + useful seeing as we can only have a single mapping type per index. It also changes + + the structure of GetMappingsResponse and GetIndexResponse to remove the extra + + nesting of mappings below the no-longer-relevant type name, and removes the types + + methods from the equivalent request classes. + + Relates to #41059 diff --git a/docs/changelog/47650.yaml b/docs/changelog/47650.yaml new file mode 100644 index 0000000000000..0e7148fbf699a --- /dev/null +++ b/docs/changelog/47650.yaml @@ -0,0 +1,7 @@ +pr: 47650 +issues: [] +area: Packaging +type: UNKNOWN +summary: Update docker-compose.yml to fix bootstrap check error +versions: + - v8.0.0 diff --git a/docs/changelog/47651.yaml b/docs/changelog/47651.yaml new file mode 100644 index 0000000000000..dafa226374284 --- /dev/null +++ b/docs/changelog/47651.yaml @@ -0,0 +1,7 @@ +pr: 47651 +issues: [] +area: Packaging +type: UNKNOWN +summary: Update `docker.asciidoc` +versions: + - v8.0.0 diff --git a/docs/changelog/47717.yaml b/docs/changelog/47717.yaml new file mode 100644 index 0000000000000..0b80983e3420a --- /dev/null +++ b/docs/changelog/47717.yaml @@ -0,0 +1,19 @@ +pr: 47717 +issues: + - 46079 + - 47443 +area: Allocation +type: breaking +summary: Remove `include_relocations` setting +versions: + - v8.0.0 +breaking: + notable: false + title: Remove `include_relocations` setting + anchor: remove_include_relocations_setting + body: >- + Setting cluster.routing.allocation.disk.include_relocations to false is a + + bad idea since it will lead to the kinds of overshoot that were otherwise fixed + + in #46079. This setting was deprecated in #47443. This commit removes it. diff --git a/docs/changelog/48170.yaml b/docs/changelog/48170.yaml new file mode 100644 index 0000000000000..7398b29f3b13b --- /dev/null +++ b/docs/changelog/48170.yaml @@ -0,0 +1,35 @@ +pr: 48170 +issues: + - 35958 +area: Infra/REST API +type: breaking +summary: Remove deprecated endpoints containing _xpack. +versions: + - v8.0.0 +breaking: + notable: false + title: Remove deprecated endpoints containing _xpack. + anchor: remove_deprecated_endpoints_containing_xpack_ + body: >- + 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 + + + Relates to #35958. diff --git a/docs/changelog/48443.yaml b/docs/changelog/48443.yaml new file mode 100644 index 0000000000000..2ada4f11f85d4 --- /dev/null +++ b/docs/changelog/48443.yaml @@ -0,0 +1,26 @@ +pr: 48443 +issues: [] +area: Infra/Transport API, CRUD +type: breaking-java +summary: Remove `Client.prepareIndex(index,` type, id) method +versions: + - v8.0.0 +breaking: + notable: false + title: Remove `Client.prepareIndex(index,` type, id) method + anchor: remove_client_prepareindex_index_type_id_method + body: >- + As types are no longer used in index requests, we can remove the type + parameter + + from prepareIndex methods in the Client interface. However, just changing the signature + + of prepareIndex(index, type, id) to prepareIndex(index, id) risks confusion when + + upgrading with the previous (now removed) prepareIndex(index, type) method - + + just changing the dependency version of java code would end up silently changing the + + semantics of the method call. Instead we should just remove this method entirely, and + + replace it by calling prepareIndex(index).setId(id) diff --git a/docs/changelog/48471.yaml b/docs/changelog/48471.yaml new file mode 100644 index 0000000000000..a70ba2960ce2c --- /dev/null +++ b/docs/changelog/48471.yaml @@ -0,0 +1,18 @@ +pr: 48471 +issues: [] +area: Features/Indices APIs, Features/Java High Level REST Client +type: breaking-java +summary: Remove deprecated include-type methods from HLRC indices client +versions: + - v8.0.0 +breaking: + notable: false + title: Remove deprecated include-type methods from HLRC indices client + anchor: remove_deprecated_include_type_methods_from_hlrc_indices_client + body: |- + We have a number of deprecated methods on the high-level Rest client's + IndicesClient that take server-side object classes and allow users to pass + the include_type_name parameter. These all have equivalent methods that + use HLRC classes instead, the only difference being the lack of the types + parameter. + This commit removes these deprecated methods. diff --git a/docs/changelog/48632.yaml b/docs/changelog/48632.yaml new file mode 100644 index 0000000000000..a7c6c1eebd949 --- /dev/null +++ b/docs/changelog/48632.yaml @@ -0,0 +1,16 @@ +pr: 48632 +issues: + - 41059 +area: Features/Indices APIs, Mapping +type: breaking +summary: Remove `include_type_name` parameter from REST layer +versions: + - v8.0.0 +breaking: + notable: false + title: Remove `include_type_name` parameter from REST layer + anchor: remove_include_type_name_parameter_from_rest_layer + body: |- + This commit removes support for the include_type_name parameter from all + REST actions that receive or return mapping configurations. + Relates to #41059 diff --git a/docs/changelog/48725.yaml b/docs/changelog/48725.yaml new file mode 100644 index 0000000000000..72df7ef68d1ac --- /dev/null +++ b/docs/changelog/48725.yaml @@ -0,0 +1,17 @@ +pr: 48725 +issues: + - 48604 +area: Search +type: breaking +summary: Remove deprecated vector functions. +versions: + - v8.0.0 +breaking: + notable: false + title: Remove deprecated vector functions. + anchor: remove_deprecated_vector_functions_ + body: >- + Follow up to #48604. This PR removes the deprecated vector function + signatures + + of the form cosineSimilarity(query, doc['field']). diff --git a/docs/changelog/48781.yaml b/docs/changelog/48781.yaml new file mode 100644 index 0000000000000..02da99414e52a --- /dev/null +++ b/docs/changelog/48781.yaml @@ -0,0 +1,16 @@ +pr: 48781 +issues: + - 48368 +area: Search +type: breaking +summary: Remove support for sparse vectors. +versions: + - v8.0.0 +breaking: + notable: false + title: Remove support for sparse vectors. + anchor: remove_support_for_sparse_vectors_ + body: |- + 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. diff --git a/docs/changelog/48927.yaml b/docs/changelog/48927.yaml new file mode 100644 index 0000000000000..f0285f771f9ab --- /dev/null +++ b/docs/changelog/48927.yaml @@ -0,0 +1,8 @@ +pr: 48927 +issues: + - 40366 +area: Infra/Core +type: UNKNOWN +summary: "[#40366] Silence some lint warnings in server project" +versions: + - v8.0.0 diff --git a/docs/changelog/48949.yaml b/docs/changelog/48949.yaml new file mode 100644 index 0000000000000..586587358d510 --- /dev/null +++ b/docs/changelog/48949.yaml @@ -0,0 +1,7 @@ +pr: 48949 +issues: [] +area: Features/ILM+SLM +type: UNKNOWN +summary: Add ILM package info documentation +versions: + - v8.0.0 diff --git a/docs/changelog/49079.yaml b/docs/changelog/49079.yaml new file mode 100644 index 0000000000000..38a675ca69400 --- /dev/null +++ b/docs/changelog/49079.yaml @@ -0,0 +1,7 @@ +pr: 49079 +issues: [] +area: Packaging +type: UNKNOWN +summary: Migrate some of the Docker tests from old repository +versions: + - v8.0.0 diff --git a/docs/changelog/49460.yaml b/docs/changelog/49460.yaml new file mode 100644 index 0000000000000..602a304381e6c --- /dev/null +++ b/docs/changelog/49460.yaml @@ -0,0 +1,16 @@ +pr: 49460 +issues: + - 21009 +area: Features/Indices APIs, Features/Java High Level REST Client +type: breaking +summary: Remove the 'template' field in index templates. +versions: + - v8.0.0 +breaking: + notable: false + title: Remove the 'template' field in index templates. + anchor: remove_the_template_field_in_index_templates_ + body: |- + The template field was deprecated in 6.0 in favor of index_patterns, and can + now be removed. + Relates to #21009. diff --git a/docs/changelog/49728.yaml b/docs/changelog/49728.yaml new file mode 100644 index 0000000000000..e7b95073609b0 --- /dev/null +++ b/docs/changelog/49728.yaml @@ -0,0 +1,8 @@ +pr: 49728 +issues: + - 40366 +area: Infra/Core +type: UNKNOWN +summary: Silence lint warnings in server project - part 2 +versions: + - v8.0.0 diff --git a/docs/changelog/50067.yaml b/docs/changelog/50067.yaml new file mode 100644 index 0000000000000..ea695be84c442 --- /dev/null +++ b/docs/changelog/50067.yaml @@ -0,0 +1,8 @@ +pr: 50067 +issues: + - 49474 +area: License +type: enhancement +summary: Support "accept_enterprise" param in get license +versions: + - v8.0.0 diff --git a/docs/changelog/50277.yaml b/docs/changelog/50277.yaml new file mode 100644 index 0000000000000..3481b56b39cd7 --- /dev/null +++ b/docs/changelog/50277.yaml @@ -0,0 +1,9 @@ +pr: 50277 +issues: + - 49926 + - 46166 +area: Packaging +type: UNKNOWN +summary: Make the Docker build more re-usable in Cloud +versions: + - v8.0.0 diff --git a/docs/changelog/50359.yaml b/docs/changelog/50359.yaml new file mode 100644 index 0000000000000..0a15ad8fcc70c --- /dev/null +++ b/docs/changelog/50359.yaml @@ -0,0 +1,8 @@ +pr: 50359 +issues: + - 50248 +area: Task Management, Mapping +type: bug +summary: Fixes to task result index mapping +versions: + - v8.0.0 diff --git a/docs/changelog/50415.yaml b/docs/changelog/50415.yaml new file mode 100644 index 0000000000000..2ebc4f253ec5c --- /dev/null +++ b/docs/changelog/50415.yaml @@ -0,0 +1,7 @@ +pr: 50415 +issues: [] +area: Engine +type: enhancement +summary: Always use soft-deletes in `InternalEngine` +versions: + - v8.0.0 diff --git a/docs/changelog/50594.yaml b/docs/changelog/50594.yaml new file mode 100644 index 0000000000000..c3cb7d8a54bd1 --- /dev/null +++ b/docs/changelog/50594.yaml @@ -0,0 +1,22 @@ +pr: 50594 +issues: + - 50499 + - 50088 +area: Infra/Core +type: breaking +summary: Remove the 'local' parameter of /_cat/nodes +versions: + - v8.0.0 +breaking: + notable: false + title: Remove the 'local' parameter of /_cat/nodes + anchor: remove_the_local_parameter_of_cat_nodes + body: |- + 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 diff --git a/docs/changelog/50739.yaml b/docs/changelog/50739.yaml new file mode 100644 index 0000000000000..7bd2a5039084b --- /dev/null +++ b/docs/changelog/50739.yaml @@ -0,0 +1,25 @@ +pr: 50739 +issues: + - 41059 +area: CRUD, Mapping +type: breaking-java +summary: Remove type parameter from CIR.mapping(type, object...) +versions: + - v8.0.0 +breaking: + notable: false + title: Remove type parameter from CIR.mapping(type, object...) + anchor: remove_type_parameter_from_cir_mapping_type_object_ + body: >- + This commit removes the type parameter from CreateIndexRequest.mapping(type, + object...), + + and the associated delegating method on CreateIndexRequestBuilder. To make migration + + simpler, the method on CreateIndexRequest is renamed to mappingFromSimplifiedDef, and + + on CreateIndexRequestBuilder to setMapping; this should help the compiler catch all + + necessary changes on upgrades. + + Relates to #41059 diff --git a/docs/changelog/50844.yaml b/docs/changelog/50844.yaml new file mode 100644 index 0000000000000..b9d22ab0dc7cb --- /dev/null +++ b/docs/changelog/50844.yaml @@ -0,0 +1,23 @@ +pr: 50844 +issues: + - 41059 +area: Mapping +type: breaking-java +summary: Remove type parameter from `PutMappingRequest.buildFromSimplifiedDef()` +versions: + - v8.0.0 +breaking: + notable: false + title: Remove type parameter from `PutMappingRequest.buildFromSimplifiedDef()` + anchor: remove_type_parameter_from_putmappingrequest_buildfromsimplifieddef_ + body: >- + Mappings built by this method should all be wrapped with _doc, so there's no + need + + to pass the type any more. This also renames the method to simpleMapping, in line + + with CreateIndexRequest, to help migration by causing compilation errors; and changes + + the signature to take a String... rather than an Object.... + + Relates to #41059 diff --git a/docs/changelog/50882.yaml b/docs/changelog/50882.yaml new file mode 100644 index 0000000000000..6d7a8a1791be4 --- /dev/null +++ b/docs/changelog/50882.yaml @@ -0,0 +1,22 @@ +pr: 50882 +issues: + - 50835 + - 50776 +area: Distributed +type: breaking, breaking-java +summary: Goodbye and thank you synced flush! +versions: + - v8.0.0 +breaking: + notable: false + title: Goodbye and thank you synced flush! + anchor: goodbye_and_thank_you_synced_flush_ + body: >- + 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. + + Depends on #50835 + + Relates #50776 diff --git a/docs/changelog/51189.yaml b/docs/changelog/51189.yaml new file mode 100644 index 0000000000000..ccba715ccc895 --- /dev/null +++ b/docs/changelog/51189.yaml @@ -0,0 +1,8 @@ +pr: 51189 +issues: + - 50775 +area: Recovery +type: enhancement +summary: Use Lucene index in peer recovery and resync +versions: + - v8.0.0 diff --git a/docs/changelog/51195.yaml b/docs/changelog/51195.yaml new file mode 100644 index 0000000000000..f396c9fb6ebb4 --- /dev/null +++ b/docs/changelog/51195.yaml @@ -0,0 +1,16 @@ +pr: 51195 +issues: + - 37614 +area: Authentication +type: breaking +summary: Make order setting mandatory for Realm config +versions: + - v8.0.0 +breaking: + notable: false + title: Make order setting mandatory for Realm config + anchor: make_order_setting_mandatory_for_realm_config + body: |- + The order parameter must be explicitly specified for each realm. + This is a breaking change and will start take effect in 8.0 + Resolves: #37614 diff --git a/docs/changelog/51219.yaml b/docs/changelog/51219.yaml new file mode 100644 index 0000000000000..51ef27be9bf35 --- /dev/null +++ b/docs/changelog/51219.yaml @@ -0,0 +1,20 @@ +pr: 51219 +issues: [] +area: Mapping +type: breaking-java +summary: Remove unused parameter from `MetadataFieldMapper.TypeParser#getDefault()` +versions: + - v8.0.0 +breaking: + notable: false + title: Remove unused parameter from `MetadataFieldMapper.TypeParser#getDefault()` + anchor: remove_unused_parameter_from_metadatafieldmapper_typeparser_getdefault_ + body: >- + This addresses a very old TODO comment in MetadataFieldMapper.TypeParser; + passing + + in a previously constructed field mapper here was a hack in order to provide access to + + prebuilt analyzers for the AllFieldType; this has now been removed, so we can remove + + the parameter from this method signature. diff --git a/docs/changelog/51417.yaml b/docs/changelog/51417.yaml new file mode 100644 index 0000000000000..f0e41bed5adce --- /dev/null +++ b/docs/changelog/51417.yaml @@ -0,0 +1,8 @@ +pr: 51417 +issues: + - 50775 +area: Engine +type: enhancement +summary: Remove translog retention policy +versions: + - v8.0.0 diff --git a/docs/changelog/51421.yaml b/docs/changelog/51421.yaml new file mode 100644 index 0000000000000..0d062a2f3efad --- /dev/null +++ b/docs/changelog/51421.yaml @@ -0,0 +1,8 @@ +pr: 51421 +issues: + - 49581 +area: EQL +type: UNKNOWN +summary: Merge EQL dev branch to master +versions: + - v8.0.0 diff --git a/docs/changelog/51697.yaml b/docs/changelog/51697.yaml new file mode 100644 index 0000000000000..c800d9258d9ba --- /dev/null +++ b/docs/changelog/51697.yaml @@ -0,0 +1,18 @@ +pr: 51697 +issues: + - 50775 +area: Engine +type: breaking +summary: Remove translog retention settings +versions: + - v8.0.0 +breaking: + notable: false + title: Remove translog retention settings + anchor: remove_translog_retention_settings + body: >- + 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 diff --git a/docs/changelog/51704.yaml b/docs/changelog/51704.yaml new file mode 100644 index 0000000000000..7450395c9b623 --- /dev/null +++ b/docs/changelog/51704.yaml @@ -0,0 +1,8 @@ +pr: 51704 +issues: + - 51703 +area: Docs Infrastructure +type: UNKNOWN +summary: Remove docs related to index time boosting +versions: + - v8.0.0 diff --git a/docs/changelog/51716.yaml b/docs/changelog/51716.yaml new file mode 100644 index 0000000000000..f7f99a14c0a94 --- /dev/null +++ b/docs/changelog/51716.yaml @@ -0,0 +1,17 @@ +pr: 51716 +issues: + - 51480 +area: Packaging +type: breaking +summary: Remove SysV init support +versions: + - v8.0.0 +breaking: + notable: false + title: Remove SysV init support + anchor: remove_sysv_init_support + body: |- + With the removal of support for older OSes, we no longer have any + supported systems which use SysV init. This commit removes support for + that legacy init system. + relates #51480 diff --git a/docs/changelog/52208.yaml b/docs/changelog/52208.yaml new file mode 100644 index 0000000000000..3cc7871395a16 --- /dev/null +++ b/docs/changelog/52208.yaml @@ -0,0 +1,9 @@ +pr: 52208 +issues: + - 50536 + - 47345 +area: Features/Stats +type: enhancement +summary: Add Bulk stats track the bulk per shard +versions: + - v8.0.0 diff --git a/docs/changelog/52257.yaml b/docs/changelog/52257.yaml new file mode 100644 index 0000000000000..0b2ac76c38209 --- /dev/null +++ b/docs/changelog/52257.yaml @@ -0,0 +1,16 @@ +pr: 52257 +issues: + - 51871 +area: Aggregations +type: breaking +summary: "Percentiles aggregation: disallow specifying same percentile values twice" +versions: + - v8.0.0 +breaking: + notable: false + title: "Percentiles aggregation: disallow specifying same percentile values twice" + anchor: percentiles_aggregation_disallow_specifying_same_percentile_values_twice + body: |- + disallows specifying same percentile values twice and throws an exception. + Note: As this is a breaking change, it goes only into 8.0 + Related: #51871 diff --git a/docs/changelog/52280.yaml b/docs/changelog/52280.yaml new file mode 100644 index 0000000000000..65b486e35221a --- /dev/null +++ b/docs/changelog/52280.yaml @@ -0,0 +1,20 @@ +pr: 52280 +issues: [] +area: Infra/Core +type: breaking +summary: Remove `fixed_auto_queue_size` threadpool type +versions: + - v8.0.0 +breaking: + notable: false + title: Remove `fixed_auto_queue_size` threadpool type + anchor: remove_fixed_auto_queue_size_threadpool_type + body: >- + The fixed_auto_queue_size thread pool holds a fixed size of threads to + handle the requests with a bounded queue for pending requests that have no + threads to service them. It's similar to the fixed threadpool, however, the + queue_size automatically adjusts according to calculations based on + + Little's Law. This dynamic adjustment was, by default, disabled for the two fixed_auto_queue_size thread pools (search and search_throttled). + + As this feature was marked as experimental, and we are unaware of any users explicitly configuring this, we intent to deprecate it in ES 7 and remove it in ES 8. diff --git a/docs/changelog/52987.yaml b/docs/changelog/52987.yaml new file mode 100644 index 0000000000000..e373a2d1208a2 --- /dev/null +++ b/docs/changelog/52987.yaml @@ -0,0 +1,7 @@ +pr: 52987 +issues: [] +area: Unknown +type: UNKNOWN +summary: Fix Javadoc comments in `QueryBuilders` +versions: + - v8.0.0 diff --git a/docs/changelog/53314.yaml b/docs/changelog/53314.yaml new file mode 100644 index 0000000000000..02da5dfc851f5 --- /dev/null +++ b/docs/changelog/53314.yaml @@ -0,0 +1,20 @@ +pr: 53314 +issues: + - 53049 +area: Infra/Core +type: breaking +summary: Remove the listener thread pool +versions: + - v8.0.0 +breaking: + notable: false + title: Remove the listener thread pool + anchor: remove_the_listener_thread_pool + body: >- + This commit completes the work to remove the listener thread pool, having + removed all uses of it in the server codebase, and deprecated it in 7.x. + With this commit, we also remove the infrastructgure to deprecate a fixed + thread pool, which was added as part of this work, since it is easy to bring + back if needed. + + Closes #53049 diff --git a/docs/changelog/53715.yaml b/docs/changelog/53715.yaml new file mode 100644 index 0000000000000..bbd82cad67dcd --- /dev/null +++ b/docs/changelog/53715.yaml @@ -0,0 +1,8 @@ +pr: 53715 +issues: + - 46702 +area: Infra/Logging +type: bug +summary: Fix NPE when logging null values in JSON +versions: + - v8.0.0 diff --git a/docs/changelog/53785.yaml b/docs/changelog/53785.yaml new file mode 100644 index 0000000000000..078ac9bff0af5 --- /dev/null +++ b/docs/changelog/53785.yaml @@ -0,0 +1,8 @@ +pr: 53785 +issues: + - 53751 +area: Cluster Coordination +type: bug +summary: Apply cluster states in system context +versions: + - v8.0.0 diff --git a/docs/changelog/53845.yaml b/docs/changelog/53845.yaml new file mode 100644 index 0000000000000..935b35e5c3870 --- /dev/null +++ b/docs/changelog/53845.yaml @@ -0,0 +1,22 @@ +pr: 53845 +issues: + - 51806 +area: Cluster Coordination +type: breaking +summary: Remove support for delaying state recovery pending master +versions: + - v8.0.0 +breaking: + notable: false + title: Remove support for delaying state recovery pending master + anchor: remove_support_for_delaying_state_recovery_pending_master + body: |- + The following settings are deprecated: + + gateway.expected_nodes + gateway.expected_master_nodes + gateway.recover_after_nodes + gateway.recover_after_master_nodes + This pull request removed these settings. + + Closes #51806 diff --git a/docs/changelog/54175.yaml b/docs/changelog/54175.yaml new file mode 100644 index 0000000000000..d9651fefe7b8e --- /dev/null +++ b/docs/changelog/54175.yaml @@ -0,0 +1,18 @@ +pr: 54175 +issues: + - 53924 +area: Infra/Core, Distributed +type: breaking +summary: Remove the `cluster.remote.connect` setting +versions: + - v8.0.0 +breaking: + notable: false + title: Remove the `cluster.remote.connect` setting + anchor: remove_the_cluster_remote_connect_setting + body: >- + In Elasticsearch 7.7.0, the setting cluster.remote.connect was deprecated. + In this commit, we remote the setting permanently in favor of setting + node.remote_cluster_client. + + Relates #53924 diff --git a/docs/changelog/54381.yaml b/docs/changelog/54381.yaml new file mode 100644 index 0000000000000..9a17051a3968e --- /dev/null +++ b/docs/changelog/54381.yaml @@ -0,0 +1,18 @@ +pr: 54381 +issues: + - 54374 +area: Infra/Core +type: breaking +summary: Remove the node local storage setting +versions: + - v8.0.0 +breaking: + notable: false + title: Remove the node local storage setting + anchor: remove_the_node_local_storage_setting + body: >- + In 7.8.0 the node.local_storage setting was deprecated in favor of requiring + all nodes to have a form of persistent storage. This commit removes the + node.local_storage setting. + + Relates #54374 diff --git a/docs/changelog/54753.yaml b/docs/changelog/54753.yaml new file mode 100644 index 0000000000000..c8175231873cb --- /dev/null +++ b/docs/changelog/54753.yaml @@ -0,0 +1,8 @@ +pr: 54753 +issues: + - 54744 +area: Aggregations +type: bug +summary: Fix `t_test` usage stats +versions: + - v8.0.0 diff --git a/docs/changelog/54904.yaml b/docs/changelog/54904.yaml new file mode 100644 index 0000000000000..a5c8ecca9778c --- /dev/null +++ b/docs/changelog/54904.yaml @@ -0,0 +1,8 @@ +pr: 54904 +issues: + - 54825 +area: Features/ILM+SLM +type: UNKNOWN +summary: Fix `IndexLifecycleExplainResponse` serialization version checks +versions: + - v8.0.0 diff --git a/docs/changelog/54953.yaml b/docs/changelog/54953.yaml new file mode 100644 index 0000000000000..808ca86da9ddd --- /dev/null +++ b/docs/changelog/54953.yaml @@ -0,0 +1,8 @@ +pr: 54953 +issues: + - 54897 +area: Search +type: bug +summary: Check for negative "from" values in search request body +versions: + - v8.0.0 diff --git a/docs/changelog/55078.yaml b/docs/changelog/55078.yaml new file mode 100644 index 0000000000000..c3b8826dad24a --- /dev/null +++ b/docs/changelog/55078.yaml @@ -0,0 +1,12 @@ +pr: 55078 +issues: [] +area: Search +type: breaking +summary: Remove the object format for indices_boost. +versions: + - v8.0.0 +breaking: + notable: false + title: Remove the object format for indices_boost. + anchor: remove_the_object_format_for_indices_boost_ + body: This format has been deprecated since version 5.2. diff --git a/docs/changelog/55100.yaml b/docs/changelog/55100.yaml new file mode 100644 index 0000000000000..3af7ae1105ab6 --- /dev/null +++ b/docs/changelog/55100.yaml @@ -0,0 +1,16 @@ +pr: 55100 +issues: [] +area: Features/Indices APIs +type: breaking, deprecation +summary: Remove local parameter for get field mapping request +versions: + - v8.0.0 +breaking: + notable: false + title: Remove local parameter for get field mapping request + anchor: remove_local_parameter_for_get_field_mapping_request + body: >- + The local parameter of get field mapping request is marked as deprecated in + 7.x. + + This PR removes it for the next major. diff --git a/docs/changelog/55109.yaml b/docs/changelog/55109.yaml new file mode 100644 index 0000000000000..9a051bafa9dd4 --- /dev/null +++ b/docs/changelog/55109.yaml @@ -0,0 +1,8 @@ +pr: 55109 +issues: + - 52640 +area: Infra/REST API +type: UNKNOWN +summary: Remove deprecated endpoints of hot threads API +versions: + - v8.0.0 diff --git a/docs/changelog/55181.yaml b/docs/changelog/55181.yaml new file mode 100644 index 0000000000000..cdb66ae1dd612 --- /dev/null +++ b/docs/changelog/55181.yaml @@ -0,0 +1,8 @@ +pr: 55181 +issues: + - 54847 +area: Aggregations +type: bug +summary: Fix BWC issues for x_pack/usage +versions: + - v8.0.0 diff --git a/docs/changelog/55399.yaml b/docs/changelog/55399.yaml new file mode 100644 index 0000000000000..6739eb5390032 --- /dev/null +++ b/docs/changelog/55399.yaml @@ -0,0 +1,8 @@ +pr: 55399 +issues: + - 55378 +area: Search +type: bug +summary: Fix `VectorsFeatureSetUsage` serialization in BWC mode +versions: + - v8.0.0 diff --git a/docs/changelog/55489.yaml b/docs/changelog/55489.yaml new file mode 100644 index 0000000000000..3abf591bc122d --- /dev/null +++ b/docs/changelog/55489.yaml @@ -0,0 +1,20 @@ +pr: 55489 +issues: + - 55411 + - 53101 +area: Features/Indices APIs +type: breaking +summary: Change prefer_v2_templates parameter to default to true +versions: + - v8.0.0 +breaking: + notable: false + title: Change prefer_v2_templates parameter to default to true + anchor: change_prefer_v2_templates_parameter_to_default_to_true + body: >- + As a followup to #55411, this commit changes the default for the + ?prefer_v2_templates querystring + + parameter to be true. This means that V2 templates will take precedence by default in 8.0+ + + Relates to #53101 diff --git a/docs/changelog/55544.yaml b/docs/changelog/55544.yaml new file mode 100644 index 0000000000000..97ec8aa767279 --- /dev/null +++ b/docs/changelog/55544.yaml @@ -0,0 +1,7 @@ +pr: 55544 +issues: [] +area: Security +type: enhancement +summary: Change default hashing algorithm for FIPS 140 +versions: + - v8.0.0 diff --git a/docs/changelog/55622.yaml b/docs/changelog/55622.yaml new file mode 100644 index 0000000000000..88ab184ab4bbb --- /dev/null +++ b/docs/changelog/55622.yaml @@ -0,0 +1,16 @@ +pr: 55622 +issues: [] +area: Search +type: breaking +summary: Remove `use_field_mapping` format option for docvalue fields. +versions: + - v8.0.0 +breaking: + notable: false + title: Remove `use_field_mapping` format option for docvalue fields. + anchor: remove_use_field_mapping_format_option_for_docvalue_fields_ + body: |- + 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. diff --git a/docs/changelog/55673.yaml b/docs/changelog/55673.yaml new file mode 100644 index 0000000000000..3650b3da0be84 --- /dev/null +++ b/docs/changelog/55673.yaml @@ -0,0 +1,20 @@ +pr: 55673 +issues: + - 50836 + - 47990 +area: Cluster Coordination +type: breaking +summary: Remove node filters for voting config exclusions +versions: + - v8.0.0 +breaking: + notable: false + title: Remove node filters for voting config exclusions + anchor: remove_node_filters_for_voting_config_exclusions + body: >- + 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 diff --git a/docs/changelog/55736.yaml b/docs/changelog/55736.yaml new file mode 100644 index 0000000000000..e199e52ab5eb8 --- /dev/null +++ b/docs/changelog/55736.yaml @@ -0,0 +1,8 @@ +pr: 55736 +issues: + - 54478 +area: Features/CAT APIs +type: UNKNOWN +summary: _cat/threadpool remove "size" and add "time" params +versions: + - v8.0.0 diff --git a/docs/changelog/56149.yaml b/docs/changelog/56149.yaml new file mode 100644 index 0000000000000..e663610b52295 --- /dev/null +++ b/docs/changelog/56149.yaml @@ -0,0 +1,8 @@ +pr: 56149 +issues: + - 52103 +area: Infra/Scripting +type: enhancement +summary: Update `DeprecationMap` to `DynamicMap` +versions: + - v8.0.0 diff --git a/docs/changelog/56211.yaml b/docs/changelog/56211.yaml new file mode 100644 index 0000000000000..0b78ead11448e --- /dev/null +++ b/docs/changelog/56211.yaml @@ -0,0 +1,19 @@ +pr: 56211 +issues: + - 54745 +area: Infra/Plugins +type: breaking +summary: Remove deprecated basic license feature enablement settings from 8.0 +versions: + - v8.0.0 +breaking: + notable: false + title: Remove deprecated basic license feature enablement settings from 8.0 + anchor: remove_deprecated_basic_license_feature_enablement_settings_from_8_0 + body: >- + In 7.8.0, we deprecated the settings for disabling basic license feature + APIs. This PR removes those settings altogether for 8.0. This is a breaking + change: if these options appear in elasticsearch.yml, they will no longer be + recognized. + + Meta issue: #54745 diff --git a/docs/changelog/57200.yaml b/docs/changelog/57200.yaml new file mode 100644 index 0000000000000..c4ad5e335e33a --- /dev/null +++ b/docs/changelog/57200.yaml @@ -0,0 +1,7 @@ +pr: 57200 +issues: [] +area: Search +type: UNKNOWN +summary: Remove deprecated `SimpleQueryStringBuilder` parameters +versions: + - v8.0.0 diff --git a/docs/changelog/57591.yaml b/docs/changelog/57591.yaml new file mode 100644 index 0000000000000..9a106b9414ce5 --- /dev/null +++ b/docs/changelog/57591.yaml @@ -0,0 +1,21 @@ +pr: 57591 +issues: + - 56171 +area: Infra/Logging +type: breaking +summary: Remove slowlog level +versions: + - v8.0.0 +breaking: + notable: false + title: Remove slowlog level + anchor: remove_slowlog_level + body: >- + Setting a slow log level requires an unnecessary conditional logic in + SearchSlowLog and IndexingSlowLog + + The behaviour of setting a level on a slow logger can be achieved with correct slow log threshold settings. + + This PR is removing slow log and modifies tests to achieve the same behaviour with changing threshold. + + relates #56171 diff --git a/docs/changelog/57594.yaml b/docs/changelog/57594.yaml new file mode 100644 index 0000000000000..e267512cfff0b --- /dev/null +++ b/docs/changelog/57594.yaml @@ -0,0 +1,7 @@ +pr: 57594 +issues: [] +area: SQL +type: enhancement +summary: Use java String methods for LTRIM/RTRIM +versions: + - v8.0.0 diff --git a/docs/changelog/58220.yaml b/docs/changelog/58220.yaml new file mode 100644 index 0000000000000..11e5d923a3f88 --- /dev/null +++ b/docs/changelog/58220.yaml @@ -0,0 +1,8 @@ +pr: 58220 +issues: + - 58217 +area: License +type: enhancement +summary: Add deprecated `accept_enterprise` param to /_xpack +versions: + - v8.0.0 diff --git a/docs/changelog/58387.yaml b/docs/changelog/58387.yaml new file mode 100644 index 0000000000000..88abfc185c579 --- /dev/null +++ b/docs/changelog/58387.yaml @@ -0,0 +1,7 @@ +pr: 58387 +issues: [] +area: Features/Data streams +type: UNKNOWN +summary: "Adjust version after backporting #57675" +versions: + - v8.0.0 diff --git a/docs/changelog/58732.yaml b/docs/changelog/58732.yaml new file mode 100644 index 0000000000000..0725b96304ce9 --- /dev/null +++ b/docs/changelog/58732.yaml @@ -0,0 +1,8 @@ +pr: 58732 +issues: + - 58682 +area: Machine Learning +type: bug +summary: Remove erroneous licence +versions: + - v8.0.0 diff --git a/docs/changelog/58779.yaml b/docs/changelog/58779.yaml new file mode 100644 index 0000000000000..9508cb941f01d --- /dev/null +++ b/docs/changelog/58779.yaml @@ -0,0 +1,8 @@ +pr: 58779 +issues: + - 58521 +area: Mapping +type: bug +summary: Remove assertions that mappings have one top-level key. +versions: + - v8.0.0 diff --git a/docs/changelog/59262.yaml b/docs/changelog/59262.yaml new file mode 100644 index 0000000000000..87e4a761fe17e --- /dev/null +++ b/docs/changelog/59262.yaml @@ -0,0 +1,20 @@ +pr: 59262 +issues: + - 50152 +area: Infra/Scripting +type: breaking +summary: Remove general cache settings +versions: + - v8.0.0 +breaking: + notable: false + title: Remove general cache settings + anchor: remove_general_cache_settings + body: |- + Removed settings: + + script.cache.max_size + script.cache.expire + script.max_compilations_rate + + Refs: #50152 diff --git a/docs/changelog/59265.yaml b/docs/changelog/59265.yaml new file mode 100644 index 0000000000000..d80da990e8282 --- /dev/null +++ b/docs/changelog/59265.yaml @@ -0,0 +1,34 @@ +pr: 59265 +issues: + - 59262 + - 50152 +area: Infra/Scripting +type: breaking +summary: Move `script_cache` into _nodes/stats +versions: + - v8.0.0 +breaking: + notable: false + title: Move `script_cache` into _nodes/stats + anchor: move_script_cache_into_nodes_stats + body: |- + Pending: #59262 + Updated _nodes/stats: + + Remove script_cache + Update script in _node/stats to include stats per context: + + "script": { + "compilations": 1, + "cache_evictions": 0, + "compilation_limit_triggered": 0, + "contexts":[ + { + "context": "aggregation_selector", + "compilations": 0, + "cache_evictions": 0, + "compilation_limit_triggered": 0 + }, + + + Refs: #50152 diff --git a/docs/changelog/59336.yaml b/docs/changelog/59336.yaml new file mode 100644 index 0000000000000..ed385d6715a9c --- /dev/null +++ b/docs/changelog/59336.yaml @@ -0,0 +1,7 @@ +pr: 59336 +issues: [] +area: Unknown +type: UNKNOWN +summary: "Re-enable bwc from #59265" +versions: + - v8.0.0 diff --git a/docs/changelog/59349.yaml b/docs/changelog/59349.yaml new file mode 100644 index 0000000000000..03e1a71615d65 --- /dev/null +++ b/docs/changelog/59349.yaml @@ -0,0 +1,8 @@ +pr: 59349 +issues: + - 44505 +area: Rollup +type: enhancement +summary: Adds support for `date_nanos` in Rollup Metric and `DateHistogram` Configs +versions: + - v8.0.0 diff --git a/docs/changelog/59475.yaml b/docs/changelog/59475.yaml new file mode 100644 index 0000000000000..abbb828d95520 --- /dev/null +++ b/docs/changelog/59475.yaml @@ -0,0 +1,7 @@ +pr: 59475 +issues: [] +area: Aggregations +type: bug +summary: Fix `DoubleBounds` null serialization +versions: + - v8.0.0 diff --git a/docs/changelog/59501.yaml b/docs/changelog/59501.yaml new file mode 100644 index 0000000000000..58c7185db5b2a --- /dev/null +++ b/docs/changelog/59501.yaml @@ -0,0 +1,9 @@ +pr: 59501 +issues: + - 59386 + - 54441 +area: Geo +type: bug +summary: Preprocess polygon rings before processing it for decomposition. +versions: + - v8.0.0 diff --git a/docs/changelog/59507.yaml b/docs/changelog/59507.yaml new file mode 100644 index 0000000000000..df70308b5762b --- /dev/null +++ b/docs/changelog/59507.yaml @@ -0,0 +1,20 @@ +pr: 59507 +issues: + - 59391 +area: Infra/Scripting +type: breaking +summary: Consolidate script parsing from object +versions: + - v8.0.0 +breaking: + notable: false + title: Consolidate script parsing from object + anchor: consolidate_script_parsing_from_object + body: >- + The update by query action parses a script from an object (map or string). + We will need to do the same for runtime fields as they are parsed as part of + mappings (#59391). + + This commit moves the existing parsing of a script from an object from RestUpdateByQueryAction to the Script class. It also adds tests and adjusts some error messages that are incorrect. Also, options were not parsed before and they are now. And unsupported fields are no longer silently ignored. + + I plan on backporting this change to 7.x without the handling for unsupported fields, as that is a breaking change. diff --git a/docs/changelog/59698.yaml b/docs/changelog/59698.yaml new file mode 100644 index 0000000000000..7c4cc20f0712c --- /dev/null +++ b/docs/changelog/59698.yaml @@ -0,0 +1,15 @@ +pr: 59698 +issues: + - 48366 +area: Recovery +type: breaking +summary: Remove dangling index auto import functionality +versions: + - v8.0.0 +breaking: + notable: false + title: Remove dangling index auto import functionality + anchor: remove_dangling_index_auto_import_functionality + body: "Closes #48366. Remove all traces of automatically importing dangling + indices. This change will not be backported, though this functionality is + deprecated as of 7.9.0." diff --git a/docs/changelog/59870.yaml b/docs/changelog/59870.yaml new file mode 100644 index 0000000000000..5e93e23f72bb6 --- /dev/null +++ b/docs/changelog/59870.yaml @@ -0,0 +1,9 @@ +pr: 59870 +issues: + - 48170 + - 35958 +area: Machine Learning +type: deprecation +summary: Remove deprecated `_xpack` endpoints +versions: + - v8.0.0 diff --git a/docs/changelog/59949.yaml b/docs/changelog/59949.yaml new file mode 100644 index 0000000000000..2ed095e778e4c --- /dev/null +++ b/docs/changelog/59949.yaml @@ -0,0 +1,8 @@ +pr: 59949 +issues: + - 59555 +area: Infra/Core +type: UNKNOWN +summary: Remove unused deprecate method in `FormatNames` +versions: + - v8.0.0 diff --git a/docs/changelog/60044.yaml b/docs/changelog/60044.yaml new file mode 100644 index 0000000000000..13d5b7857279e --- /dev/null +++ b/docs/changelog/60044.yaml @@ -0,0 +1,8 @@ +pr: 60044 +issues: + - 59555 +area: Infra/Core +type: UNKNOWN +summary: Remove camel case named formats +versions: + - v8.0.0 diff --git a/docs/changelog/60158.yaml b/docs/changelog/60158.yaml new file mode 100644 index 0000000000000..df4f89c7e2ddd --- /dev/null +++ b/docs/changelog/60158.yaml @@ -0,0 +1,8 @@ +pr: 60158 +issues: + - 60001 +area: Infra/Scripting +type: UNKNOWN +summary: Expose all doc field str const accesses +versions: + - v8.0.0 diff --git a/docs/changelog/60351.yaml b/docs/changelog/60351.yaml new file mode 100644 index 0000000000000..ff1440201604f --- /dev/null +++ b/docs/changelog/60351.yaml @@ -0,0 +1,8 @@ +pr: 60351 +issues: + - 59683 +area: Search +type: bug +summary: Improve error msg for CCS request on node without remote cluster role +versions: + - v8.0.0 diff --git a/docs/changelog/60505.yaml b/docs/changelog/60505.yaml new file mode 100644 index 0000000000000..f83f0a7ba744a --- /dev/null +++ b/docs/changelog/60505.yaml @@ -0,0 +1,7 @@ +pr: 60505 +issues: [] +area: Recovery, Snapshot/Restore +type: enhancement +summary: Add recovery state tracking for Searchable Snapshots +versions: + - v8.0.0 diff --git a/docs/changelog/60873.yaml b/docs/changelog/60873.yaml new file mode 100644 index 0000000000000..bfaa746bfba70 --- /dev/null +++ b/docs/changelog/60873.yaml @@ -0,0 +1,18 @@ +pr: 60873 +issues: + - 60872 +area: Cluster Coordination +type: breaking, enhancement +summary: Remove join timeout +versions: + - v8.0.0 +breaking: + notable: false + title: Remove join timeout + anchor: remove_join_timeout + body: |- + There is no point in timing out a join attempt any more. Timing out and + retrying with the same master is pointless, and an in-flight join + attempt to one master no longer blocks attempts to join other masters. + This commit removes this unnecessary setting. + Relates #60872 in which this setting was deprecated. diff --git a/docs/changelog/61043.yaml b/docs/changelog/61043.yaml new file mode 100644 index 0000000000000..f1a4fc1d3d959 --- /dev/null +++ b/docs/changelog/61043.yaml @@ -0,0 +1,16 @@ +pr: 61043 +issues: [] +area: Infra/REST API +type: breaking, enhancement +summary: Remove content type required setting +versions: + - v8.0.0 +breaking: + notable: false + title: Remove content type required setting + anchor: remove_content_type_required_setting + body: |- + This change removes the HTTP content type required setting, which was + deprecated in 6.0 and only existed for users upgrading from 5.x so that + they did not need to remove the setting immediately. The setting has no + effect on behavior. diff --git a/docs/changelog/61259.yaml b/docs/changelog/61259.yaml new file mode 100644 index 0000000000000..684f847a5090a --- /dev/null +++ b/docs/changelog/61259.yaml @@ -0,0 +1,8 @@ +pr: 61259 +issues: + - 60889 +area: Features/Java High Level REST Client, Infra/Logging +type: UNKNOWN +summary: Avoid `StackOverflowError` due to regex alternate paths +versions: + - v8.0.0 diff --git a/docs/changelog/61427.yaml b/docs/changelog/61427.yaml new file mode 100644 index 0000000000000..e64ae0f6c3234 --- /dev/null +++ b/docs/changelog/61427.yaml @@ -0,0 +1,25 @@ +pr: 61427 +issues: + - 61987 + - 60516 +area: Infra/REST API, SQL +type: breaking +summary: Allow parsing Content-Type and Accept headers with version +versions: + - v8.0.0 +breaking: + notable: false + title: Allow parsing Content-Type and Accept headers with version + anchor: allow_parsing_content_type_and_accept_headers_with_version + body: >- + Content-Type and Accept headers expect a versioned form of media types + + like application/vnd.elasticsearch+json;compatible-with=7 + + when previously it was simple application/json or (cbor, yaml..) - it is still + + supported + + next step after #61987 + + relates #60516 diff --git a/docs/changelog/61428.yaml b/docs/changelog/61428.yaml new file mode 100644 index 0000000000000..ad9c16ca6bdbf --- /dev/null +++ b/docs/changelog/61428.yaml @@ -0,0 +1,9 @@ +pr: 61428 +issues: + - 59764 + - 59779 +area: EQL +type: UNKNOWN +summary: Replace `SearchHit` in response with Event +versions: + - v8.0.0 diff --git a/docs/changelog/61508.yaml b/docs/changelog/61508.yaml new file mode 100644 index 0000000000000..53a9043ae7f5d --- /dev/null +++ b/docs/changelog/61508.yaml @@ -0,0 +1,7 @@ +pr: 61508 +issues: [] +area: Infra/Scripting +type: bug +summary: Fixes casting in constant folding +versions: + - v8.0.0 diff --git a/docs/changelog/61594.yaml b/docs/changelog/61594.yaml new file mode 100644 index 0000000000000..4f523a60f5960 --- /dev/null +++ b/docs/changelog/61594.yaml @@ -0,0 +1,7 @@ +pr: 61594 +issues: [] +area: Infra/Scripting +type: bug +summary: Several minor Painless fixes +versions: + - v8.0.0 diff --git a/docs/changelog/61825.yaml b/docs/changelog/61825.yaml new file mode 100644 index 0000000000000..aeb5e9bc419a2 --- /dev/null +++ b/docs/changelog/61825.yaml @@ -0,0 +1,8 @@ +pr: 61825 +issues: + - 61755 +area: Infra/Scripting +type: bug +summary: Change compound assignment structure to support String concatenation +versions: + - v8.0.0 diff --git a/docs/changelog/62156.yaml b/docs/changelog/62156.yaml new file mode 100644 index 0000000000000..eead4d3acf54f --- /dev/null +++ b/docs/changelog/62156.yaml @@ -0,0 +1,7 @@ +pr: 62156 +issues: [] +area: Infra/Logging +type: UNKNOWN +summary: Populate data stream fields when `xOpaqueId` not provided +versions: + - v8.0.0 diff --git a/docs/changelog/62309.yaml b/docs/changelog/62309.yaml new file mode 100644 index 0000000000000..dd43fb11409ae --- /dev/null +++ b/docs/changelog/62309.yaml @@ -0,0 +1,17 @@ +pr: 62309 +issues: + - 62297 +area: Snapshot/Restore +type: breaking +summary: Remove Repository Stats API +versions: + - v8.0.0 +breaking: + notable: false + title: Remove Repository Stats API + anchor: remove_repository_stats_api + body: >- + Now the Repository Stats API is deprecated in 7.10.0 (#62297) we can remove + it in 8.0.0. + + I'm labeling this as >breaking to respect the development process but we're talking about an experimental API that was never released(behind a feature flag). diff --git a/docs/changelog/62468.yaml b/docs/changelog/62468.yaml new file mode 100644 index 0000000000000..1ae02e606fb8b --- /dev/null +++ b/docs/changelog/62468.yaml @@ -0,0 +1,8 @@ +pr: 62468 +issues: + - 62153 +area: Infra/REST API +type: UNKNOWN +summary: Adds quotes to timestamp values in runtime_fields/40_date YAML test +versions: + - v8.0.0 diff --git a/docs/changelog/62639.yaml b/docs/changelog/62639.yaml new file mode 100644 index 0000000000000..13aee779a9b83 --- /dev/null +++ b/docs/changelog/62639.yaml @@ -0,0 +1,8 @@ +pr: 62639 +issues: + - 62623 +area: Mapping +type: deprecation +summary: Remove mapping boost parameter entirely +versions: + - v8.0.0 diff --git a/docs/changelog/62646.yaml b/docs/changelog/62646.yaml new file mode 100644 index 0000000000000..1f9c46055090c --- /dev/null +++ b/docs/changelog/62646.yaml @@ -0,0 +1,7 @@ +pr: 62646 +issues: [] +area: Mapping +type: enhancement +summary: Sparse vector to throw exception consistently +versions: + - v8.0.0 diff --git a/docs/changelog/63038.yaml b/docs/changelog/63038.yaml new file mode 100644 index 0000000000000..365affec62754 --- /dev/null +++ b/docs/changelog/63038.yaml @@ -0,0 +1,7 @@ +pr: 63038 +issues: [] +area: Features/ILM+SLM +type: UNKNOWN +summary: Move SLM history to data stream +versions: + - v8.0.0 diff --git a/docs/changelog/63384.yaml b/docs/changelog/63384.yaml new file mode 100644 index 0000000000000..90f1df5ab6902 --- /dev/null +++ b/docs/changelog/63384.yaml @@ -0,0 +1,9 @@ +pr: 63384 +issues: + - 63307 + - 60707 +area: Infra/Core +type: UNKNOWN +summary: Removes `week_year` date format +versions: + - v8.0.0 diff --git a/docs/changelog/63660.yaml b/docs/changelog/63660.yaml new file mode 100644 index 0000000000000..29464f827c8b9 --- /dev/null +++ b/docs/changelog/63660.yaml @@ -0,0 +1,8 @@ +pr: 63660 +issues: + - 63545 +area: Infra/REST API +type: UNKNOWN +summary: "Wraps values containing : in `runtime_fields` test in quotes" +versions: + - v8.0.0 diff --git a/docs/changelog/63692.yaml b/docs/changelog/63692.yaml new file mode 100644 index 0000000000000..7b55a0548aa04 --- /dev/null +++ b/docs/changelog/63692.yaml @@ -0,0 +1,27 @@ +pr: 63692 +issues: + - 63680 +area: Search +type: breaking, bug +summary: Fix range query on date fields for number inputs +versions: + - v8.0.0 +breaking: + notable: false + title: Fix range query on date fields for number inputs + anchor: fix_range_query_on_date_fields_for_number_inputs + body: >- + 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. We should change this to always + + interpret and parse numbers in this case with the second option "epoch_millis" + + if no other formatter was provided. + + Closes #63680 diff --git a/docs/changelog/64252.yaml b/docs/changelog/64252.yaml new file mode 100644 index 0000000000000..1f55e85435cd8 --- /dev/null +++ b/docs/changelog/64252.yaml @@ -0,0 +1,12 @@ +pr: 64252 +issues: [] +area: Features/Watcher +type: breaking, enhancement +summary: Move watcher history to data stream +versions: + - v8.0.0 +breaking: + notable: false + title: Move watcher history to data stream + anchor: move_watcher_history_to_data_stream + body: This change moves watcher history to data stream. diff --git a/docs/changelog/64327.yaml b/docs/changelog/64327.yaml new file mode 100644 index 0000000000000..f8940c3cc23af --- /dev/null +++ b/docs/changelog/64327.yaml @@ -0,0 +1,9 @@ +pr: 64327 +issues: + - 63813 + - 868 +area: Machine Learning +type: bug +summary: Handle null value of `FieldCapabilitiesResponse` +versions: + - v8.0.0 diff --git a/docs/changelog/64406.yaml b/docs/changelog/64406.yaml new file mode 100644 index 0000000000000..796dd65ff48f5 --- /dev/null +++ b/docs/changelog/64406.yaml @@ -0,0 +1,8 @@ +pr: 64406 +issues: + - 51816 +area: Infra/REST API +type: UNKNOWN +summary: Introduce per REST endpoint media types +versions: + - v8.0.0 diff --git a/docs/changelog/64423.yaml b/docs/changelog/64423.yaml new file mode 100644 index 0000000000000..72748dac59694 --- /dev/null +++ b/docs/changelog/64423.yaml @@ -0,0 +1,8 @@ +pr: 64423 +issues: + - 51816 +area: Infra/REST API +type: UNKNOWN +summary: Allow registering compatible handlers +versions: + - v8.0.0 diff --git a/docs/changelog/64472.yaml b/docs/changelog/64472.yaml new file mode 100644 index 0000000000000..9d2356f1cab07 --- /dev/null +++ b/docs/changelog/64472.yaml @@ -0,0 +1,34 @@ +pr: 64472 +issues: + - 63843 +area: Infra/Logging, Audit +type: breaking +summary: Compress audit logs +versions: + - v8.0.0 +breaking: + notable: false + title: Compress audit logs + anchor: compress_audit_logs + body: >- + audit logs should be compressed when rolling over due to size based + + triggering policy breaching 1GB. + + Files are not being deleted. + + closes #63843 + + + + Have you signed the contributor license agreement? + + Have you followed the contributor guidelines? + + If submitting code, have you built your formula locally prior to submission with gradle check? + + If submitting code, is your pull request against master? Unless there is a good reason otherwise, we prefer pull requests against master and will backport as needed. + + If submitting code, have you checked that your submission is for an OS and architecture that we support? + + If you are submitting this code for a class then read our policy for that. diff --git a/docs/changelog/64481.yaml b/docs/changelog/64481.yaml new file mode 100644 index 0000000000000..eda678367bd62 --- /dev/null +++ b/docs/changelog/64481.yaml @@ -0,0 +1,8 @@ +pr: 64481 +issues: + - 51816 +area: Infra/REST API +type: UNKNOWN +summary: Introduce Compatible Version plugin +versions: + - v8.0.0 diff --git a/docs/changelog/64650.yaml b/docs/changelog/64650.yaml new file mode 100644 index 0000000000000..e26f39b90eb24 --- /dev/null +++ b/docs/changelog/64650.yaml @@ -0,0 +1,9 @@ +pr: 64650 +issues: + - 64406 + - 51816 +area: Infra/REST API +type: UNKNOWN +summary: Do not allow spaces within `MediaType's` parameters +versions: + - v8.0.0 diff --git a/docs/changelog/64708.yaml b/docs/changelog/64708.yaml new file mode 100644 index 0000000000000..daeff9b68b9a6 --- /dev/null +++ b/docs/changelog/64708.yaml @@ -0,0 +1,9 @@ +pr: 64708 +issues: + - 64689 + - 51816 +area: Infra/REST API +type: UNKNOWN +summary: Handle incorrect header values +versions: + - v8.0.0 diff --git a/docs/changelog/64721.yaml b/docs/changelog/64721.yaml new file mode 100644 index 0000000000000..c8f726400df6a --- /dev/null +++ b/docs/changelog/64721.yaml @@ -0,0 +1,9 @@ +pr: 64721 +issues: + - 64689 + - 51816 +area: Infra/REST API +type: UNKNOWN +summary: Ignore media ranges when parsing +versions: + - v8.0.0 diff --git a/docs/changelog/64732.yaml b/docs/changelog/64732.yaml new file mode 100644 index 0000000000000..38c36bf7bdf0a --- /dev/null +++ b/docs/changelog/64732.yaml @@ -0,0 +1,17 @@ +pr: 64732 +issues: + - 21337 +area: Features/Indices APIs +type: breaking +summary: Remove deprecated `_upgrade` API +versions: + - v8.0.0 +breaking: + notable: false + title: Remove deprecated `_upgrade` API + anchor: remove_deprecated_upgrade_api + body: >- + The _upgrade API has been superseded by the _reindex API and was deprecated + in 7.11.0. This commit removes it completely for the 8.0.0 release. + + Resolves #21337 diff --git a/docs/changelog/64794.yaml b/docs/changelog/64794.yaml new file mode 100644 index 0000000000000..2213a3153f7df --- /dev/null +++ b/docs/changelog/64794.yaml @@ -0,0 +1,8 @@ +pr: 64794 +issues: + - 62198 +area: Features/CAT APIs +type: deprecation +summary: Adjust deprecation version after backport +versions: + - v8.0.0 diff --git a/docs/changelog/64867.yaml b/docs/changelog/64867.yaml new file mode 100644 index 0000000000000..75982fb2f8cf0 --- /dev/null +++ b/docs/changelog/64867.yaml @@ -0,0 +1,20 @@ +pr: 64867 +issues: [] +area: Features/CAT APIs +type: breaking +summary: Remove the deprecated local parameter for _cat/shards +versions: + - v8.0.0 +breaking: + notable: false + title: Remove the deprecated local parameter for _cat/shards + anchor: remove_the_deprecated_local_parameter_for_cat_shards + body: >- + The cat shards API performs a ClusterStateAction and then an + IndicesStatsAction. Today it accepts the ?local parameter and passes this to + the ClusterStateAction but this parameter has no effect on the + IndicesStatsAction. This can be surprising because GET _cat/shards?local + looks like it might be a completely local call but in fact it still depends + on every node in the cluster. + + The local parameter was deprecated in 7.x and this commit removes it for 8.x. diff --git a/docs/changelog/64868.yaml b/docs/changelog/64868.yaml new file mode 100644 index 0000000000000..f123a9e0822f0 --- /dev/null +++ b/docs/changelog/64868.yaml @@ -0,0 +1,20 @@ +pr: 64868 +issues: [] +area: Features/CAT APIs +type: breaking +summary: Remove the deprecated local parameter for _cat/indices +versions: + - v8.0.0 +breaking: + notable: false + title: Remove the deprecated local parameter for _cat/indices + anchor: remove_the_deprecated_local_parameter_for_cat_indices + body: >- + The cat indices API performs several actions including an + IndicesStatsAction. Today it accepts the ?local parameter and passes it to + the actions that support it but this parameter has no effect on the + IndicesStatsAction. This can be surprising because GET _cat/indices?local + looks like it might be a completely local call but in fact it still depends + on every node in the cluster. + + The local parameter was deprecated in 7.x and this commit removes it for 8.x. diff --git a/docs/changelog/64869.yaml b/docs/changelog/64869.yaml new file mode 100644 index 0000000000000..2ce02574aaf9b --- /dev/null +++ b/docs/changelog/64869.yaml @@ -0,0 +1,8 @@ +pr: 64869 +issues: + - 58646 +area: EQL +type: UNKNOWN +summary: Add option for returning results from the tail of the stream +versions: + - v8.0.0 diff --git a/docs/changelog/65255.yaml b/docs/changelog/65255.yaml new file mode 100644 index 0000000000000..60ca48ebfd0cd --- /dev/null +++ b/docs/changelog/65255.yaml @@ -0,0 +1,7 @@ +pr: 65255 +issues: [] +area: Infra/REST API, SQL +type: UNKNOWN +summary: Adding back a validation of incorrect response header +versions: + - v8.0.0 diff --git a/docs/changelog/65259.yaml b/docs/changelog/65259.yaml new file mode 100644 index 0000000000000..1646a57d87367 --- /dev/null +++ b/docs/changelog/65259.yaml @@ -0,0 +1,7 @@ +pr: 65259 +issues: [] +area: Analysis +type: UNKNOWN +summary: "Phonetic: Remove class that is part of commons-codec" +versions: + - v8.0.0 diff --git a/docs/changelog/65500.yaml b/docs/changelog/65500.yaml new file mode 100644 index 0000000000000..2d5b892e20a40 --- /dev/null +++ b/docs/changelog/65500.yaml @@ -0,0 +1,8 @@ +pr: 65500 +issues: + - 51816 +area: Infra/REST API +type: UNKNOWN +summary: Support response content-type with versioned media type +versions: + - v8.0.0 diff --git a/docs/changelog/65590.yaml b/docs/changelog/65590.yaml new file mode 100644 index 0000000000000..8353cff3febf6 --- /dev/null +++ b/docs/changelog/65590.yaml @@ -0,0 +1,9 @@ +pr: 65590 +issues: + - 61884 + - 61884 +area: Security +type: deprecation +summary: Remove support of creating CA on the fly when generating certificates +versions: + - v8.0.0 diff --git a/docs/changelog/65753.yaml b/docs/changelog/65753.yaml new file mode 100644 index 0000000000000..170b2765506ad --- /dev/null +++ b/docs/changelog/65753.yaml @@ -0,0 +1,19 @@ +pr: 65753 +issues: + - 65601 + - 65249 +area: Network +type: breaking +summary: Remove escape hatch permitting incompatible builds +versions: + - v8.0.0 +breaking: + notable: false + title: Remove escape hatch permitting incompatible builds + anchor: remove_escape_hatch_permitting_incompatible_builds + body: |- + Today in 7.x there is a deprecated system property that bypasses the + check that prevents nodes of incompatible builds from communicating. + This commit removes the system property in master so that the check is + always enforced. + Relates #65601, #65249 diff --git a/docs/changelog/66297.yaml b/docs/changelog/66297.yaml new file mode 100644 index 0000000000000..58d76e410caf7 --- /dev/null +++ b/docs/changelog/66297.yaml @@ -0,0 +1,8 @@ +pr: 66297 +issues: + - 65725 +area: Infra/Core +type: bug +summary: Add searchable snapshot cache folder to `NodeEnvironment` +versions: + - v8.0.0 diff --git a/docs/changelog/66671.yaml b/docs/changelog/66671.yaml new file mode 100644 index 0000000000000..ca1bc537797c2 --- /dev/null +++ b/docs/changelog/66671.yaml @@ -0,0 +1,8 @@ +pr: 66671 +issues: + - 66317 +area: Security +type: deprecation +summary: Remove the id field from the `InvalidateApiKey` API +versions: + - v8.0.0 diff --git a/docs/changelog/67154.yaml b/docs/changelog/67154.yaml new file mode 100644 index 0000000000000..a52b0384429c8 --- /dev/null +++ b/docs/changelog/67154.yaml @@ -0,0 +1,7 @@ +pr: 67154 +issues: [] +area: Features/Watcher +type: enhancement +summary: Remove watcher history clean up from monitoring +versions: + - v8.0.0 diff --git a/docs/changelog/67158.yaml b/docs/changelog/67158.yaml new file mode 100644 index 0000000000000..368d7e73b5947 --- /dev/null +++ b/docs/changelog/67158.yaml @@ -0,0 +1,8 @@ +pr: 67158 +issues: + - 66419 +area: Distributed +type: bug +summary: Introduce ?wait_for_active_shards=index-setting +versions: + - v8.0.0 diff --git a/docs/changelog/67216.yaml b/docs/changelog/67216.yaml new file mode 100644 index 0000000000000..ccd725571edef --- /dev/null +++ b/docs/changelog/67216.yaml @@ -0,0 +1,8 @@ +pr: 67216 +issues: + - 56713 +area: SQL +type: enhancement +summary: Improve alias resolution in sub-queries +versions: + - v8.0.0 diff --git a/docs/changelog/67374.yaml b/docs/changelog/67374.yaml new file mode 100644 index 0000000000000..a667d33794d21 --- /dev/null +++ b/docs/changelog/67374.yaml @@ -0,0 +1,9 @@ +pr: 67374 +issues: + - 67246 + - 67158 +area: Distributed +type: bug +summary: Respect `CloseIndexRequest#waitForActiveShards` in HLRC +versions: + - v8.0.0 diff --git a/docs/changelog/67409.yaml b/docs/changelog/67409.yaml new file mode 100644 index 0000000000000..49d60b5869541 --- /dev/null +++ b/docs/changelog/67409.yaml @@ -0,0 +1,8 @@ +pr: 67409 +issues: + - 65500 +area: Infra/Core +type: bug +summary: Precompute `ParsedMediaType` for `XContentType` +versions: + - v8.0.0 diff --git a/docs/changelog/67552.yaml b/docs/changelog/67552.yaml new file mode 100644 index 0000000000000..8cd8018c02488 --- /dev/null +++ b/docs/changelog/67552.yaml @@ -0,0 +1,8 @@ +pr: 67552 +issues: + - 67545 +area: Infra/REST API +type: UNKNOWN +summary: Make `ParsedMediaType` truly immutable +versions: + - v8.0.0 diff --git a/docs/changelog/67672.yaml b/docs/changelog/67672.yaml new file mode 100644 index 0000000000000..7f1273f537b12 --- /dev/null +++ b/docs/changelog/67672.yaml @@ -0,0 +1,7 @@ +pr: 67672 +issues: [] +area: EQL, SQL +type: UNKNOWN +summary: Refactor function resolution strategy +versions: + - v8.0.0 diff --git a/docs/changelog/67677.yaml b/docs/changelog/67677.yaml new file mode 100644 index 0000000000000..11fabc272d2f5 --- /dev/null +++ b/docs/changelog/67677.yaml @@ -0,0 +1,9 @@ +pr: 67677 +issues: + - 66986 +area: Infra/Scripting +type: UNKNOWN +summary: Make scripted search templates work with new `mediaType` from + `XContentType.JSON` +versions: + - v8.0.0 diff --git a/docs/changelog/67923.yaml b/docs/changelog/67923.yaml new file mode 100644 index 0000000000000..5988cf53081b0 --- /dev/null +++ b/docs/changelog/67923.yaml @@ -0,0 +1,8 @@ +pr: 67923 +issues: + - 51816 +area: Infra/Core +type: UNKNOWN +summary: "`SecurityRestFilter` to delegate `compatibleWith` method" +versions: + - v8.0.0 diff --git a/docs/changelog/68113.yaml b/docs/changelog/68113.yaml new file mode 100644 index 0000000000000..e61bf6d967494 --- /dev/null +++ b/docs/changelog/68113.yaml @@ -0,0 +1,8 @@ +pr: 68113 +issues: + - 51816 +area: Infra/REST API +type: UNKNOWN +summary: Make `XContentParser` aware of compatible API version +versions: + - v8.0.0 diff --git a/docs/changelog/68157.yaml b/docs/changelog/68157.yaml new file mode 100644 index 0000000000000..a7bb817a15f0d --- /dev/null +++ b/docs/changelog/68157.yaml @@ -0,0 +1,9 @@ +pr: 68157 +issues: + - 68101 + - 68101 +area: Infra/Scripting +type: UNKNOWN +summary: "[DOCS] Fixing Painless tests" +versions: + - v8.0.0 diff --git a/docs/changelog/68176.yaml b/docs/changelog/68176.yaml new file mode 100644 index 0000000000000..7a2b26f26ff1c --- /dev/null +++ b/docs/changelog/68176.yaml @@ -0,0 +1,8 @@ +pr: 68176 +issues: + - 68172 +area: EQL +type: enhancement +summary: Introduce case insensitive variant in~ +versions: + - v8.0.0 diff --git a/docs/changelog/68214.yaml b/docs/changelog/68214.yaml new file mode 100644 index 0000000000000..e9e4497cec1f1 --- /dev/null +++ b/docs/changelog/68214.yaml @@ -0,0 +1,9 @@ +pr: 68214 +issues: + - 68198 + - 67666 +area: SQL +type: UNKNOWN +summary: Update supported version for `date_nanos` +versions: + - v8.0.0 diff --git a/docs/changelog/68564.yaml b/docs/changelog/68564.yaml new file mode 100644 index 0000000000000..6eda4bcc16e4b --- /dev/null +++ b/docs/changelog/68564.yaml @@ -0,0 +1,18 @@ +pr: 68564 +issues: + - 41059 + - 68311 +area: Search +type: breaking +summary: Remove support for `_type` in searches +versions: + - v8.0.0 +breaking: + notable: false + title: Remove support for `_type` in searches + anchor: remove_support_for_type_in_searches + body: |- + Types are no longer allowed in requests in 8.0, so we can remove support for + using the _type field within a search request. + Relates to #41059. + Closes #68311. diff --git a/docs/changelog/68606.yaml b/docs/changelog/68606.yaml new file mode 100644 index 0000000000000..0de02e2d6ea03 --- /dev/null +++ b/docs/changelog/68606.yaml @@ -0,0 +1,7 @@ +pr: 68606 +issues: [] +area: SQL +type: UNKNOWN +summary: Add text formatting support for multivalue +versions: + - v8.0.0 diff --git a/docs/changelog/68648.yaml b/docs/changelog/68648.yaml new file mode 100644 index 0000000000000..f7da9a38591a3 --- /dev/null +++ b/docs/changelog/68648.yaml @@ -0,0 +1,8 @@ +pr: 68648 +issues: + - 68100 +area: Infra/REST API +type: UNKNOWN +summary: Refactor usage of compatible version +versions: + - v8.0.0 diff --git a/docs/changelog/68754.yaml b/docs/changelog/68754.yaml new file mode 100644 index 0000000000000..62bb5f87045cc --- /dev/null +++ b/docs/changelog/68754.yaml @@ -0,0 +1,7 @@ +pr: 68754 +issues: [] +area: EQL, SQL +type: UNKNOWN +summary: Improve exact match detection in `StringPattern` +versions: + - v8.0.0 diff --git a/docs/changelog/68808.yaml b/docs/changelog/68808.yaml new file mode 100644 index 0000000000000..e73165d8b0593 --- /dev/null +++ b/docs/changelog/68808.yaml @@ -0,0 +1,8 @@ +pr: 68808 +issues: [] +area: Infra/REST API +type: UNKNOWN +summary: Refactor `ObjectParser` and `CompatibleObjectParser` to support REST + Compatible API +versions: + - v8.0.0 diff --git a/docs/changelog/68966.yaml b/docs/changelog/68966.yaml new file mode 100644 index 0000000000000..7ec1fdbb76631 --- /dev/null +++ b/docs/changelog/68966.yaml @@ -0,0 +1,7 @@ +pr: 68966 +issues: [] +area: SQL +type: UNKNOWN +summary: Add xDBC and CLI support. QA CSV specs +versions: + - v8.0.0 diff --git a/docs/changelog/69029.yaml b/docs/changelog/69029.yaml new file mode 100644 index 0000000000000..aac93fed490a9 --- /dev/null +++ b/docs/changelog/69029.yaml @@ -0,0 +1,9 @@ +pr: 69029 +issues: + - 69016 + - 67325 +area: Highlighting +type: UNKNOWN +summary: Update versions after backport of `max_analyzed_offset` +versions: + - v8.0.0 diff --git a/docs/changelog/69131.yaml b/docs/changelog/69131.yaml new file mode 100644 index 0000000000000..a1b9133b7907c --- /dev/null +++ b/docs/changelog/69131.yaml @@ -0,0 +1,10 @@ +pr: 69131 +issues: + - 47671 + - 46587 + - 54160 +area: Infra/REST API +type: UNKNOWN +summary: "[REST Compatible API] Typed endpoints for Index and Get APIs" +versions: + - v8.0.0 diff --git a/docs/changelog/69149.yaml b/docs/changelog/69149.yaml new file mode 100644 index 0000000000000..b60964d0c5a66 --- /dev/null +++ b/docs/changelog/69149.yaml @@ -0,0 +1,20 @@ +pr: 69149 +issues: + - 55820 +area: Packaging +type: breaking +summary: Remove support for `JAVA_HOME` +versions: + - v8.0.0 +breaking: + notable: false + title: Remove support for `JAVA_HOME` + anchor: remove_support_for_java_home_ + body: >- + This commit removes support for JAVA_HOME. As we previously deprecated usage + of JAVA_HOME to override the path for the JDK, this commit follows up by + removing support for JAVA_HOME. Note that we do not treat JAVA_HOME being + set as a failure, as it is perfectly reasonable for a user to have JAVA_HOME + configured at the system level. + + Closes #55820 diff --git a/docs/changelog/69512.yaml b/docs/changelog/69512.yaml new file mode 100644 index 0000000000000..008ed8bf5afa3 --- /dev/null +++ b/docs/changelog/69512.yaml @@ -0,0 +1,7 @@ +pr: 69512 +issues: [] +area: SQL +type: enhancement +summary: Export array values through result sets +versions: + - v8.0.0 diff --git a/docs/changelog/69606.yaml b/docs/changelog/69606.yaml new file mode 100644 index 0000000000000..9fe2f4b290f65 --- /dev/null +++ b/docs/changelog/69606.yaml @@ -0,0 +1,9 @@ +pr: 69606 +issues: + - 69037 + - 43373 +area: Infra/REST API +type: UNKNOWN +summary: "[Rest Compatible Api] update and delete by query using size field" +versions: + - v8.0.0 diff --git a/docs/changelog/69710.yaml b/docs/changelog/69710.yaml new file mode 100644 index 0000000000000..651532373697a --- /dev/null +++ b/docs/changelog/69710.yaml @@ -0,0 +1,8 @@ +pr: 69710 +issues: + - 69377 +area: Unknown +type: UNKNOWN +summary: Update skip after backport +versions: + - v8.0.0 diff --git a/docs/changelog/69774.yaml b/docs/changelog/69774.yaml new file mode 100644 index 0000000000000..d92ab5d808d42 --- /dev/null +++ b/docs/changelog/69774.yaml @@ -0,0 +1,8 @@ +pr: 69774 +issues: + - 51816 +area: Infra/REST API +type: UNKNOWN +summary: Allow for field declaration for future compatible versions +versions: + - v8.0.0 diff --git a/docs/changelog/69901.yaml b/docs/changelog/69901.yaml new file mode 100644 index 0000000000000..15a6e25965657 --- /dev/null +++ b/docs/changelog/69901.yaml @@ -0,0 +1,8 @@ +pr: 69901 +issues: + - 69895 +area: SQL +type: bug +summary: Make `RestSqlQueryAction` thread-safe +versions: + - v8.0.0 diff --git a/docs/changelog/70209.yaml b/docs/changelog/70209.yaml new file mode 100644 index 0000000000000..f2dc841ca18e7 --- /dev/null +++ b/docs/changelog/70209.yaml @@ -0,0 +1,9 @@ +pr: 70209 +issues: + - 69548 + - 69548 +area: Search +type: enhancement +summary: Completely disallow setting negative size in search +versions: + - v8.0.0 diff --git a/docs/changelog/70243.yaml b/docs/changelog/70243.yaml new file mode 100644 index 0000000000000..f49bfcbb9a2fe --- /dev/null +++ b/docs/changelog/70243.yaml @@ -0,0 +1,7 @@ +pr: 70243 +issues: [] +area: Infra/REST API +type: UNKNOWN +summary: "Parsing: Validate that fields are not registered twice" +versions: + - v8.0.0 diff --git a/docs/changelog/70878.yaml b/docs/changelog/70878.yaml new file mode 100644 index 0000000000000..b59f3a1b3b342 --- /dev/null +++ b/docs/changelog/70878.yaml @@ -0,0 +1,8 @@ +pr: 70878 +issues: + - 51816 +area: Infra/REST API +type: UNKNOWN +summary: Make `restApiVersion` on `XContentBuilder` final +versions: + - v8.0.0 diff --git a/elasticsearch b/elasticsearch new file mode 100644 index 0000000000000..e69de29bb2d1d diff --git a/server/src/main/java/org/elasticsearch/Version.java b/server/src/main/java/org/elasticsearch/Version.java index 20af6c989fda7..0ac891f042ded 100644 --- a/server/src/main/java/org/elasticsearch/Version.java +++ b/server/src/main/java/org/elasticsearch/Version.java @@ -146,7 +146,8 @@ public class Version implements Comparable, ToXContentFragment { public static final Version V_7_12_0 = new Version(7120099, org.apache.lucene.util.Version.LUCENE_8_8_0); public static final Version V_7_12_1 = new Version(7120199, org.apache.lucene.util.Version.LUCENE_8_8_0); public static final Version V_7_13_0 = new Version(7130099, org.apache.lucene.util.Version.LUCENE_8_8_2); - public static final Version CURRENT = V_7_13_0; + public static final Version V_7_14_0 = new Version(7140099, org.apache.lucene.util.Version.LUCENE_8_8_2); + public static final Version CURRENT = V_7_14_0; private static final ImmutableOpenIntMap idToVersion; private static final ImmutableOpenMap stringToVersion;