diff --git a/src/ApiGenerator/Domain/Specification/Documentation.cs b/src/ApiGenerator/Domain/Specification/Documentation.cs
index c5aa43fc40b..208e79c86a0 100644
--- a/src/ApiGenerator/Domain/Specification/Documentation.cs
+++ b/src/ApiGenerator/Domain/Specification/Documentation.cs
@@ -8,7 +8,13 @@ namespace ApiGenerator.Domain.Specification
 	public class Documentation
 	{
 		public string Description { get; set; }
-		public string Url { get; set; }
+
+		private string _url;
+		public string Url
+		{
+			get => _url;
+			set => _url = value?.Replace("http://", "https://");
+		}
 	}
 
 	public class DocumentationConverter : JsonConverter
diff --git a/src/ApiGenerator/RestSpecification/Core/root.html b/src/ApiGenerator/RestSpecification/Core/root.html
index 18af002f31d..65711f667ce 100644
--- a/src/ApiGenerator/RestSpecification/Core/root.html
+++ b/src/ApiGenerator/RestSpecification/Core/root.html
@@ -18,9 +18,9 @@
 
 
 
-  <link crossorigin="anonymous" media="all" integrity="sha512-Wr5yTs8gD42bv1Ll5KLXr7cXzuVcbKOcuHmifgt/6YlZuluDTyAJnfnYhNYKpgVK1F51ks8Y2QA+XENQoMp/PA==" rel="stylesheet" href="https://github.githubassets.com/assets/frameworks-5abe724ecf200f8d9bbf52e5e4a2d7af.css" />
-  <link crossorigin="anonymous" media="all" integrity="sha512-DnBQhWGJ7icZU4LPhD6FlaZ9IrBOmbP4/4bEfpGQRbCLwutaFNqbuAaM8Y/w7IygRCMuOybM7fLDGe+UV9TEjQ==" rel="stylesheet" href="https://github.githubassets.com/assets/site-0e7050856189ee27195382cf843e8595.css" />
-    <link crossorigin="anonymous" media="all" integrity="sha512-/Kdj6P6WRk2SG1AIisQL1y+ZbNnTv1a+pX/4yP0e13VjZ5s+uYXnQOx+NKpXpBPqzyB/JscjxW7D30/a5DneZA==" rel="stylesheet" href="https://github.githubassets.com/assets/github-fca763e8fe96464d921b50088ac40bd7.css" />
+  <link crossorigin="anonymous" media="all" integrity="sha512-ZUjVod2EvYMDbGqRSyW0rpfgBq3i+gnR/4PfrzLsy5f20oIcRfgFQFVKgi3Ztp917bP1K/kdP5q8+nAlJ3+cFA==" rel="stylesheet" href="https://github.githubassets.com/assets/frameworks-6548d5a1dd84bd83036c6a914b25b4ae.css" />
+  <link crossorigin="anonymous" media="all" integrity="sha512-HNV7VuXI98SSFimaE7r8eVsgrmzC37AMNXw1GrNbOl4wN3ATov+SdHusRTAAf4NPoRsUcOOQyYsOCA0AcN4m0w==" rel="stylesheet" href="https://github.githubassets.com/assets/site-1cd57b56e5c8f7c49216299a13bafc79.css" />
+    <link crossorigin="anonymous" media="all" integrity="sha512-CKBn/UfyE+yEuqeavkB8Y5xld809yQJ0Evsa+pOoHP8jlBS0TGBeKIiOs17M57SuJMEZl3wjXuB2pexW8oEeuA==" rel="stylesheet" href="https://github.githubassets.com/assets/github-08a067fd47f213ec84baa79abe407c63.css" />
     
     
     
@@ -42,7 +42,7 @@
   
   
 
-    <meta name="request-id" content="ADE8:11791:36B04A5:52268EE:5E41B8BA" data-pjax-transient="true" /><meta name="html-safe-nonce" content="8084a447b2d9837b8602eefe5519e5477b1a43fd" data-pjax-transient="true" /><meta name="visitor-payload" content="eyJyZWZlcnJlciI6bnVsbCwicmVxdWVzdF9pZCI6IkFERTg6MTE3OTE6MzZCMDRBNTo1MjI2OEVFOjVFNDFCOEJBIiwidmlzaXRvcl9pZCI6IjMzNTcyMzk0NTcwMzYxODc0NyIsInJlZ2lvbl9lZGdlIjoiYW1zIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9" data-pjax-transient="true" /><meta name="visitor-hmac" content="84a4a8bb1d16ac86b395a2e21249c0ab91dcdf2bffd9d72e51094f2f46100021" data-pjax-transient="true" />
+  <meta name="request-id" content="8924:11184:12C825C:1BB68B0:5E4D15D7" data-pjax-transient="true"/><meta name="html-safe-nonce" content="b05eaad04e514d72be91f91c653258ac6885187b" data-pjax-transient="true"/><meta name="visitor-payload" content="eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiI4OTI0OjExMTg0OjEyQzgyNUM6MUJCNjhCMDo1RTREMTVENyIsInZpc2l0b3JfaWQiOiI2NDgzNjg3OTgzMTUyOTYwOTgzIiwicmVnaW9uX2VkZ2UiOiJhbXMiLCJyZWdpb25fcmVuZGVyIjoiYW1zIn0=" data-pjax-transient="true"/><meta name="visitor-hmac" content="c8cb6e1eaa01c0895b9c3d3665febddb66d87f6ab43de27c5950d569704c13bc" data-pjax-transient="true"/>
 
 
 
@@ -78,7 +78,7 @@
 
     <meta name="enabled-features" content="MARKETPLACE_FEATURED_BLOG_POSTS,MARKETPLACE_INVOICED_BILLING,MARKETPLACE_SOCIAL_PROOF_CUSTOMERS,MARKETPLACE_TRENDING_SOCIAL_PROOF,MARKETPLACE_RECOMMENDATIONS,MARKETPLACE_PENDING_INSTALLATIONS,RELATED_ISSUES">
 
-  <meta http-equiv="x-pjax-version" content="b41dafcb41e2ceb6409cd7968585d6e9">
+  <meta http-equiv="x-pjax-version" content="2e63e6bd8ece9826eb61af0c1a5496f1">
   
 
       <link href="https://github.com/elastic/elasticsearch/commits/master.atom" rel="alternate" title="Recent Commits to elasticsearch:master" type="application/atom+xml">
@@ -260,7 +260,7 @@ <h4 class="text-gray-light text-normal text-mono f5 mb-2  border-top pt-3">Conne
           spellcheck="false"
           autocomplete="off"
           >
-            <input type="hidden" value="vxSHabnmy3daIokGPhCjyZZXfepDCNfE1W0hBIWXTv9hEaYdwqeHHpssn0BQcrY7f9llaQUSpAtfNC62pwRfPw==" data-csrf="true" class="js-data-jump-to-suggestions-path-csrf" />
+          <input type="hidden" data-csrf="true" class="js-data-jump-to-suggestions-path-csrf" value="Wn/IrgAExDrU3XDVRmdbGPloEsOOEsi3rTYDAsl0JOG889odN1/vAYgtLx10LMM4QdiF7nghT6OZTv+MZbfFlw==" />
           <input type="hidden" class="js-site-search-type-field" name="type" >
             <img src="https://github.githubassets.com/images/search-key-slash.svg" alt="" class="mr-2 header-search-key-slash">
 
@@ -409,6 +409,11 @@ <h4 class="text-gray-light text-normal text-mono f5 mb-2  border-top pt-3">Conne
 </div>
 
 
+      
+
+  <div class="js-notification-shelf-not-found-error" hidden></div>
+
+
 
 
   <div class="application-main " data-commit-hovercards-enabled>
@@ -419,6 +424,7 @@ <h4 class="text-gray-light text-normal text-mono f5 mb-2  border-top pt-3">Conne
 
 
 
+
   
 
 
@@ -429,7 +435,7 @@ <h4 class="text-gray-light text-normal text-mono f5 mb-2  border-top pt-3">Conne
 
 
 
-  <div class="pagehead repohead readability-menu bg-gray-light pb-0 pt-3  pb-0">
+  <div class="pagehead repohead hx_repohead readability-menu bg-gray-light pb-0 pt-3  pb-0">
 
     <div class="container-lg mb-4 px-3 d-flex">
 
@@ -460,7 +466,7 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
     <svg class="octicon octicon-eye v-align-text-bottom" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M8.06 2C3 2 0 8 0 8s3 6 8.06 6C13 14 16 8 16 8s-3-6-7.94-6zM8 12c-2.2 0-4-1.78-4-4 0-2.2 1.8-4 4-4 2.22 0 4 1.8 4 4 0 2.22-1.78 4-4 4zm2-4c0 1.11-.89 2-2 2-1.11 0-2-.89-2-2 0-1.11.89-2 2-2 1.11 0 2 .89 2 2z"/></svg>
     Watch
 </a>    <a class="social-count" href="/elastic/elasticsearch/watchers"
-       aria-label="2785 users are watching this repository">
+       aria-label="2782 users are watching this repository">
       2.8k
     </a>
 
@@ -473,8 +479,8 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
       Star
 </a>
     <a class="social-count js-social-count" href="/elastic/elasticsearch/stargazers"
-      aria-label="46944 users starred this repository">
-      46.9k
+      aria-label="47080 users starred this repository">
+      47.1k
     </a>
 
   </li>
@@ -485,8 +491,8 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
         Fork
 </a>
     <a href="/elastic/elasticsearch/network/members" class="social-count"
-       aria-label="15937 users forked this repository">
-      15.9k
+       aria-label="16000 users forked this repository">
+      16k
     </a>
   </li>
 </ul>
@@ -510,7 +516,7 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
       <a itemprop="url" data-hotkey="g i" class="js-selected-navigation-item reponav-item" data-selected-links="repo_issues repo_labels repo_milestones /elastic/elasticsearch/issues" href="/elastic/elasticsearch/issues">
         <div class="d-inline"><svg class="octicon octicon-issue-opened" viewBox="0 0 14 16" version="1.1" width="14" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 011.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"/></svg></div>
         <span itemprop="name">Issues</span>
-        <span class="Counter">2,166</span>
+        <span class="Counter">2,197</span>
         <meta itemprop="position" content="2">
 </a>    </span>
 
@@ -519,7 +525,7 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
     <a data-hotkey="g p" data-skip-pjax="true" itemprop="url" class="js-selected-navigation-item reponav-item" data-selected-links="repo_pulls checks /elastic/elasticsearch/pulls" href="/elastic/elasticsearch/pulls">
       <div class="d-inline"><svg class="octicon octicon-git-pull-request" viewBox="0 0 12 16" version="1.1" width="12" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0010 15a1.993 1.993 0 001-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 00-1 3.72v6.56A1.993 1.993 0 002 15a1.993 1.993 0 001-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"/></svg></div>
       <span itemprop="name">Pull requests</span>
-      <span class="Counter">311</span>
+      <span class="Counter">315</span>
       <meta itemprop="position" content="4">
 </a>  </span>
 
@@ -549,6 +555,8 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
 
 
   </div>
+
+
 <div class="container-lg clearfix new-discussion-timeline  px-3">
   <div class="repository-content ">
 
@@ -596,10 +604,10 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
 
   
 
-<include-fragment src="/elastic/elasticsearch/tree-commit/bb62ebfa3dd2a199182154b2bbadb076b31c1eb0/rest-api-spec/src/main/resources/rest-api-spec/api" class="commit-tease commit-loader">
+<include-fragment src="/elastic/elasticsearch/tree-commit/a2c1f2d1219f481a46b001d15b6454dd65c958d7/rest-api-spec/src/main/resources/rest-api-spec/api" class="commit-tease commit-loader">
   <div class="blank loader-loading">
-      <img alt="" class="loader" src="https://github.githubassets.com/images/spinners/octocat-spinner-32-EAF2F5.gif" width="16" height="16" />
-      Fetching latest commit…
+    <img alt="" class="loader" src="https://github.githubassets.com/images/spinners/octocat-spinner-32-EAF2F5.gif" width="16" height="16" />
+    Fetching latest commit…
   </div>
   <div class="loader-error">
     Cannot retrieve the latest commit at this time.
@@ -608,7 +616,7 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
 
 
 <include-fragment class="file-wrap" src="/elastic/elasticsearch/file-list/master/rest-api-spec/src/main/resources/rest-api-spec/api">
-  <a class="d-none js-permalink-shortcut" data-hotkey="y" href="/elastic/elasticsearch/tree/bb62ebfa3dd2a199182154b2bbadb076b31c1eb0/rest-api-spec/src/main/resources/rest-api-spec/api">Permalink</a>
+  <a class="d-none js-permalink-shortcut" data-hotkey="y" href="/elastic/elasticsearch/tree/a2c1f2d1219f481a46b001d15b6454dd65c958d7/rest-api-spec/src/main/resources/rest-api-spec/api">Permalink</a>
 
   <table class="files js-navigation-container js-active-navigation-container" data-pjax>
     <thead>
@@ -643,10 +651,23 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="update _common.json format (#46872)
+
+API spec now use an object for the documentation field. _common was not updated yet. This commit updates _common.json and its corresponding parser.
+
+Closes #46744
+
+Co-Authored-By: Tomas Della Vedova &lt;delvedor@users.noreply.github.com&gt;" class="link-gray" href="/elastic/elasticsearch/commit/74e3af5c9edae1d46f3fd838de1e73f449d8ec9b">update _common.json format (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="495817301" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/46872" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/46872/hovercard" href="https://github.com/elastic/elasticsearch/pull/46872">#46872</a><a data-pjax="true" title="update _common.json format (#46872)
+
+API spec now use an object for the documentation field. _common was not updated yet. This commit updates _common.json and its corresponding parser.
+
+Closes #46744
+
+Co-Authored-By: Tomas Della Vedova &lt;delvedor@users.noreply.github.com&gt;" class="link-gray" href="/elastic/elasticsearch/commit/74e3af5c9edae1d46f3fd838de1e73f449d8ec9b">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-09-23T15:00:37Z" class="no-wrap">Sep 23, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -659,10 +680,15 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="[DOCS] Fix typos in several REST API specs (#51197)
+
+Changes `effected` to `affected` in several REST API spec files." class="link-gray" href="/elastic/elasticsearch/commit/c3b5f713e2a9fdfc6a9f05892aa7647d905b55d4">[DOCS] Fix typos in several REST API specs (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="551934955" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/51197" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/51197/hovercard" href="https://github.com/elastic/elasticsearch/pull/51197">#51197</a><a data-pjax="true" title="[DOCS] Fix typos in several REST API specs (#51197)
+
+Changes `effected` to `affected` in several REST API spec files." class="link-gray" href="/elastic/elasticsearch/commit/c3b5f713e2a9fdfc6a9f05892aa7647d905b55d4">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2020-01-22T17:17:33Z" class="no-wrap">Jan 22, 2020</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -691,10 +717,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -707,10 +782,11 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="[DOCS] Remove unsupported `local` and `master_timeout` parms from cat API docs (#47933)" class="link-gray" href="/elastic/elasticsearch/commit/64c1dfa72773ece2c9d1936d9f0c1280ecd21a21">[DOCS] Remove unsupported `local` and `master_timeout` parms from cat…</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-10-14T15:38:46Z" class="no-wrap">Oct 14, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -723,10 +799,11 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="[DOCS] Remove unsupported `local` and `master_timeout` parms from cat API docs (#47933)" class="link-gray" href="/elastic/elasticsearch/commit/64c1dfa72773ece2c9d1936d9f0c1280ecd21a21">[DOCS] Remove unsupported `local` and `master_timeout` parms from cat…</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-10-14T15:38:46Z" class="no-wrap">Oct 14, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -739,10 +816,11 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="[DOCS] Remove unsupported `local` and `master_timeout` parms from cat API docs (#47933)" class="link-gray" href="/elastic/elasticsearch/commit/64c1dfa72773ece2c9d1936d9f0c1280ecd21a21">[DOCS] Remove unsupported `local` and `master_timeout` parms from cat…</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-10-14T15:38:46Z" class="no-wrap">Oct 14, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -755,10 +833,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -771,10 +898,25 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Time parameter includes description (#49368)
+
+* Time parameter includes description
+
+In option enumeration causing codegenerators to pick up the description
+as a value to send.
+
+* cat.shards missing ending quotes" class="link-gray" href="/elastic/elasticsearch/commit/1c3b341960e3b70555927bdbab325d26382f68b2">Time parameter includes description (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="525742844" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/49368" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/49368/hovercard" href="https://github.com/elastic/elasticsearch/pull/49368">#49368</a><a data-pjax="true" title="Time parameter includes description (#49368)
+
+* Time parameter includes description
+
+In option enumeration causing codegenerators to pick up the description
+as a value to send.
+
+* cat.shards missing ending quotes" class="link-gray" href="/elastic/elasticsearch/commit/1c3b341960e3b70555927bdbab325d26382f68b2">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2020-02-06T16:18:22Z" class="no-wrap">Feb 6, 2020</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -787,10 +929,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -803,10 +994,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -835,10 +1075,25 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Time parameter includes description (#49368)
+
+* Time parameter includes description
+
+In option enumeration causing codegenerators to pick up the description
+as a value to send.
+
+* cat.shards missing ending quotes" class="link-gray" href="/elastic/elasticsearch/commit/1c3b341960e3b70555927bdbab325d26382f68b2">Time parameter includes description (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="525742844" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/49368" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/49368/hovercard" href="https://github.com/elastic/elasticsearch/pull/49368">#49368</a><a data-pjax="true" title="Time parameter includes description (#49368)
+
+* Time parameter includes description
+
+In option enumeration causing codegenerators to pick up the description
+as a value to send.
+
+* cat.shards missing ending quotes" class="link-gray" href="/elastic/elasticsearch/commit/1c3b341960e3b70555927bdbab325d26382f68b2">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2020-02-06T16:18:22Z" class="no-wrap">Feb 6, 2020</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -851,10 +1106,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -867,10 +1171,25 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Time parameter includes description (#49368)
+
+* Time parameter includes description
+
+In option enumeration causing codegenerators to pick up the description
+as a value to send.
+
+* cat.shards missing ending quotes" class="link-gray" href="/elastic/elasticsearch/commit/1c3b341960e3b70555927bdbab325d26382f68b2">Time parameter includes description (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="525742844" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/49368" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/49368/hovercard" href="https://github.com/elastic/elasticsearch/pull/49368">#49368</a><a data-pjax="true" title="Time parameter includes description (#49368)
+
+* Time parameter includes description
+
+In option enumeration causing codegenerators to pick up the description
+as a value to send.
+
+* cat.shards missing ending quotes" class="link-gray" href="/elastic/elasticsearch/commit/1c3b341960e3b70555927bdbab325d26382f68b2">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2020-02-06T16:18:22Z" class="no-wrap">Feb 6, 2020</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -883,10 +1202,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -899,10 +1267,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -915,10 +1332,25 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Time parameter includes description (#49368)
+
+* Time parameter includes description
+
+In option enumeration causing codegenerators to pick up the description
+as a value to send.
+
+* cat.shards missing ending quotes" class="link-gray" href="/elastic/elasticsearch/commit/1c3b341960e3b70555927bdbab325d26382f68b2">Time parameter includes description (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="525742844" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/49368" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/49368/hovercard" href="https://github.com/elastic/elasticsearch/pull/49368">#49368</a><a data-pjax="true" title="Time parameter includes description (#49368)
+
+* Time parameter includes description
+
+In option enumeration causing codegenerators to pick up the description
+as a value to send.
+
+* cat.shards missing ending quotes" class="link-gray" href="/elastic/elasticsearch/commit/1c3b341960e3b70555927bdbab325d26382f68b2">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2020-02-06T16:18:22Z" class="no-wrap">Feb 6, 2020</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -931,10 +1363,25 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Time parameter includes description (#49368)
+
+* Time parameter includes description
+
+In option enumeration causing codegenerators to pick up the description
+as a value to send.
+
+* cat.shards missing ending quotes" class="link-gray" href="/elastic/elasticsearch/commit/1c3b341960e3b70555927bdbab325d26382f68b2">Time parameter includes description (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="525742844" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/49368" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/49368/hovercard" href="https://github.com/elastic/elasticsearch/pull/49368">#49368</a><a data-pjax="true" title="Time parameter includes description (#49368)
+
+* Time parameter includes description
+
+In option enumeration causing codegenerators to pick up the description
+as a value to send.
+
+* cat.shards missing ending quotes" class="link-gray" href="/elastic/elasticsearch/commit/1c3b341960e3b70555927bdbab325d26382f68b2">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2020-02-06T16:18:22Z" class="no-wrap">Feb 6, 2020</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -947,10 +1394,25 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Time parameter includes description (#49368)
+
+* Time parameter includes description
+
+In option enumeration causing codegenerators to pick up the description
+as a value to send.
+
+* cat.shards missing ending quotes" class="link-gray" href="/elastic/elasticsearch/commit/1c3b341960e3b70555927bdbab325d26382f68b2">Time parameter includes description (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="525742844" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/49368" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/49368/hovercard" href="https://github.com/elastic/elasticsearch/pull/49368">#49368</a><a data-pjax="true" title="Time parameter includes description (#49368)
+
+* Time parameter includes description
+
+In option enumeration causing codegenerators to pick up the description
+as a value to send.
+
+* cat.shards missing ending quotes" class="link-gray" href="/elastic/elasticsearch/commit/1c3b341960e3b70555927bdbab325d26382f68b2">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2020-02-06T16:18:22Z" class="no-wrap">Feb 6, 2020</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -963,10 +1425,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -979,10 +1490,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -995,10 +1555,15 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Fixes for API specification (#46522)
+
+Follow-up of #42346" class="link-gray" href="/elastic/elasticsearch/commit/a2a502b330468f8f18202b37eebeb473212b510a">Fixes for API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="491529992" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/46522" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/46522/hovercard" href="https://github.com/elastic/elasticsearch/pull/46522">#46522</a><a data-pjax="true" title="Fixes for API specification (#46522)
+
+Follow-up of #42346" class="link-gray" href="/elastic/elasticsearch/commit/a2a502b330468f8f18202b37eebeb473212b510a">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-09-16T09:23:57Z" class="no-wrap">Sep 16, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1011,10 +1576,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1027,10 +1641,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1043,10 +1706,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
-            </span>
-          </td>
-          <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
+            </span>
+          </td>
+          <td class="age">
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1059,10 +1771,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1075,10 +1836,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1091,10 +1901,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1107,10 +1966,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1123,10 +2031,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1139,10 +2096,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1155,10 +2161,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1171,10 +2226,21 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title='Use optype CREATE for single auto-id index requests (#47353)
+
+Changes auto-id index requests to use optype CREATE, making it compliant with our docs.
+This will also make these auto-id index requests compatible with the new "create-doc" index
+privilege (which is based on the optype), the default optype is changed to create, just as it is
+already documented.' class="link-gray" href="/elastic/elasticsearch/commit/e1012efbd1d5ef5acb002a41418137a96fe23aac">Use optype CREATE for single auto-id index requests (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="500836538" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/47353" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/47353/hovercard" href="https://github.com/elastic/elasticsearch/pull/47353">#47353</a><a data-pjax="true" title='Use optype CREATE for single auto-id index requests (#47353)
+
+Changes auto-id index requests to use optype CREATE, making it compliant with our docs.
+This will also make these auto-id index requests compatible with the new "create-doc" index
+privilege (which is based on the optype), the default optype is changed to create, just as it is
+already documented.' class="link-gray" href="/elastic/elasticsearch/commit/e1012efbd1d5ef5acb002a41418137a96fe23aac">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-10-02T09:04:19Z" class="no-wrap">Oct 2, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1187,10 +2253,15 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="[DOCS] Fix typos in several REST API specs (#51197)
+
+Changes `effected` to `affected` in several REST API spec files." class="link-gray" href="/elastic/elasticsearch/commit/c3b5f713e2a9fdfc6a9f05892aa7647d905b55d4">[DOCS] Fix typos in several REST API specs (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="551934955" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/51197" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/51197/hovercard" href="https://github.com/elastic/elasticsearch/pull/51197">#51197</a><a data-pjax="true" title="[DOCS] Fix typos in several REST API specs (#51197)
+
+Changes `effected` to `affected` in several REST API spec files." class="link-gray" href="/elastic/elasticsearch/commit/c3b5f713e2a9fdfc6a9f05892aa7647d905b55d4">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2020-01-22T17:17:33Z" class="no-wrap">Jan 22, 2020</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1203,10 +2274,17 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Fix the type for &quot;slices&quot; in the Delete By Query REST API specification (#51792)
+
+The previous patch in c1d9966d35d incorrectly set the `type` to `number|auto`,
+which is incorrect — the &quot;polymorphic&quot; type, denoted with the `|` sign,
+should contain only other types, ie. number, string, bool, etc.
+
+Fixes #51535" class="link-gray" href="/elastic/elasticsearch/commit/68db7fc611622ca0e418f454249e376e01f80587">Fix the type for "slices" in the Delete By Query REST API specificati…</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2020-02-02T17:09:07Z" class="no-wrap">Feb 2, 2020</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1219,10 +2297,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1235,10 +2362,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1251,10 +2427,15 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Remove force from version_type enum in rest-spec (#49370)
+
+As per #47228 `force` is no longer a valid option" class="link-gray" href="/elastic/elasticsearch/commit/8098276b7ffb72c31967c726d490c3950c40bdf2">Remove force from version_type enum in rest-spec (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="525745740" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/49370" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/49370/hovercard" href="https://github.com/elastic/elasticsearch/pull/49370">#49370</a><a data-pjax="true" title="Remove force from version_type enum in rest-spec (#49370)
+
+As per #47228 `force` is no longer a valid option" class="link-gray" href="/elastic/elasticsearch/commit/8098276b7ffb72c31967c726d490c3950c40bdf2">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-11-26T08:58:33Z" class="no-wrap">Nov 26, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1267,10 +2448,15 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Remove force from version_type enum in rest-spec (#49370)
+
+As per #47228 `force` is no longer a valid option" class="link-gray" href="/elastic/elasticsearch/commit/8098276b7ffb72c31967c726d490c3950c40bdf2">Remove force from version_type enum in rest-spec (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="525745740" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/49370" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/49370/hovercard" href="https://github.com/elastic/elasticsearch/pull/49370">#49370</a><a data-pjax="true" title="Remove force from version_type enum in rest-spec (#49370)
+
+As per #47228 `force` is no longer a valid option" class="link-gray" href="/elastic/elasticsearch/commit/8098276b7ffb72c31967c726d490c3950c40bdf2">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-11-26T08:58:33Z" class="no-wrap">Nov 26, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1283,10 +2469,21 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Remove types from explain API (#46926)
+
+We no longer need a type to get the source of a document, so we can remove it from
+the explain API as well.
+
+Relates to #41059" class="link-gray" href="/elastic/elasticsearch/commit/b733f9e80300edd434c0a449eccfa6f921a704ba">Remove types from explain API (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="496373649" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/46926" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/46926/hovercard" href="https://github.com/elastic/elasticsearch/pull/46926">#46926</a><a data-pjax="true" title="Remove types from explain API (#46926)
+
+We no longer need a type to get the source of a document, so we can remove it from
+the explain API as well.
+
+Relates to #41059" class="link-gray" href="/elastic/elasticsearch/commit/b733f9e80300edd434c0a449eccfa6f921a704ba">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-09-23T16:55:09Z" class="no-wrap">Sep 23, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1299,10 +2496,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1315,10 +2561,15 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Remove force from version_type enum in rest-spec (#49370)
+
+As per #47228 `force` is no longer a valid option" class="link-gray" href="/elastic/elasticsearch/commit/8098276b7ffb72c31967c726d490c3950c40bdf2">Remove force from version_type enum in rest-spec (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="525745740" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/49370" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/49370/hovercard" href="https://github.com/elastic/elasticsearch/pull/49370">#49370</a><a data-pjax="true" title="Remove force from version_type enum in rest-spec (#49370)
+
+As per #47228 `force` is no longer a valid option" class="link-gray" href="/elastic/elasticsearch/commit/8098276b7ffb72c31967c726d490c3950c40bdf2">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-11-26T08:58:33Z" class="no-wrap">Nov 26, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1331,10 +2582,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1347,10 +2647,41 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title='Scripting: get context names REST API (#48026)
+
+Adds `GET /_script_context`, returning a `contexts` object with each
+available context as a key whose value is an empty object. eg.
+```
+{
+  "contexts": {
+    "aggregation_selector": {},
+    "aggs": {},
+    "aggs_combine": {},
+...
+  }
+}
+```
+
+refs: #47411' class="link-gray" href="/elastic/elasticsearch/commit/c6037dc93bcda984e903999e182181cd725b01b9">Scripting: get context names REST API (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="506897118" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/48026" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/48026/hovercard" href="https://github.com/elastic/elasticsearch/pull/48026">#48026</a><a data-pjax="true" title='Scripting: get context names REST API (#48026)
+
+Adds `GET /_script_context`, returning a `contexts` object with each
+available context as a key whose value is an empty object. eg.
+```
+{
+  "contexts": {
+    "aggregation_selector": {},
+    "aggs": {},
+    "aggs_combine": {},
+...
+  }
+}
+```
+
+refs: #47411' class="link-gray" href="/elastic/elasticsearch/commit/c6037dc93bcda984e903999e182181cd725b01b9">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-10-16T22:44:47Z" class="no-wrap">Oct 16, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1363,10 +2694,95 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
-            </span>
-          </td>
-          <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+                  <a data-pjax="true" title='Scripting: add available languages &amp; contexts API (#49652)
+
+Adds `GET /_script_language` to support Kibana dynamic scripting
+language selection.
+
+Response contains whether `inline` and/or `stored` scripts are
+enabled as determined by the `script.allowed_types` settings.
+
+For each scripting language registered, such as `painless`,
+`expression`, `mustache` or custom, available contexts for the language
+are included as determined by the `script.allowed_contexts` setting.
+
+Response format:
+```
+{
+  "types_allowed": [
+    "inline",
+    "stored"
+  ],
+  "language_contexts": [
+    {
+      "language": "expression",
+      "contexts": [
+        "aggregation_selector",
+        "aggs"
+        ...
+      ]
+    },
+    {
+      "language": "painless",
+      "contexts": [
+        "aggregation_selector",
+        "aggs",
+        "aggs_combine",
+        ...
+      ]
+    }
+...
+  ]
+}
+```
+
+Fixes: #49463' class="link-gray" href="/elastic/elasticsearch/commit/4a078029ed2d7eebe1507ca9bf0a3289df554eb2">Scripting: add available languages &amp; contexts API (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="529436256" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/49652" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/49652/hovercard" href="https://github.com/elastic/elasticsearch/pull/49652">#49652</a><a data-pjax="true" title='Scripting: add available languages &amp; contexts API (#49652)
+
+Adds `GET /_script_language` to support Kibana dynamic scripting
+language selection.
+
+Response contains whether `inline` and/or `stored` scripts are
+enabled as determined by the `script.allowed_types` settings.
+
+For each scripting language registered, such as `painless`,
+`expression`, `mustache` or custom, available contexts for the language
+are included as determined by the `script.allowed_contexts` setting.
+
+Response format:
+```
+{
+  "types_allowed": [
+    "inline",
+    "stored"
+  ],
+  "language_contexts": [
+    {
+      "language": "expression",
+      "contexts": [
+        "aggregation_selector",
+        "aggs"
+        ...
+      ]
+    },
+    {
+      "language": "painless",
+      "contexts": [
+        "aggregation_selector",
+        "aggs",
+        "aggs_combine",
+        ...
+      ]
+    }
+...
+  ]
+}
+```
+
+Fixes: #49463' class="link-gray" href="/elastic/elasticsearch/commit/4a078029ed2d7eebe1507ca9bf0a3289df554eb2">)</a>
+            </span>
+          </td>
+          <td class="age">
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-12-04T01:55:48Z" class="no-wrap">Dec 4, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1379,10 +2795,15 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Remove force from version_type enum in rest-spec (#49370)
+
+As per #47228 `force` is no longer a valid option" class="link-gray" href="/elastic/elasticsearch/commit/8098276b7ffb72c31967c726d490c3950c40bdf2">Remove force from version_type enum in rest-spec (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="525745740" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/49370" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/49370/hovercard" href="https://github.com/elastic/elasticsearch/pull/49370">#49370</a><a data-pjax="true" title="Remove force from version_type enum in rest-spec (#49370)
+
+As per #47228 `force` is no longer a valid option" class="link-gray" href="/elastic/elasticsearch/commit/8098276b7ffb72c31967c726d490c3950c40bdf2">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-11-26T08:58:33Z" class="no-wrap">Nov 26, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1395,10 +2816,16 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Remove type field from DocWriteRequest and associated Response objects (#47671)
+
+This commit removes the type field from index, update and delete requests, and their
+associated responses.
+
+Relates to #41059" class="link-gray" href="/elastic/elasticsearch/commit/566e1b7d33ec62e2f6011245782cd65d6381ee43">Remove type field from DocWriteRequest and associated Response objects (</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-10-11T09:23:55Z" class="no-wrap">Oct 11, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1411,26 +2838,124 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
-            </span>
-          </td>
-          <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
-          </td>
-        </tr>
-        <tr class="js-navigation-item">
-          <td class="icon">
-            <svg aria-label="file" class="octicon octicon-file" viewBox="0 0 12 16" version="1.1" width="12" height="16" role="img"><path fill-rule="evenodd" d="M6 5H2V4h4v1zM2 8h7V7H2v1zm0 2h7V9H2v1zm0 2h7v-1H2v1zm10-7.5V14c0 .55-.45 1-1 1H1c-.55 0-1-.45-1-1V2c0-.55.45-1 1-1h7.5L12 4.5zM11 5L8 2H1v12h10V5z"/></svg>
-            <img width="16" height="16" class="spinner" alt="" src="https://github.githubassets.com/images/spinners/octocat-spinner-32.gif" />
-          </td>
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
+            </span>
+          </td>
+          <td class="age">
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
+          </td>
+        </tr>
+        <tr class="js-navigation-item">
+          <td class="icon">
+            <svg aria-label="file" class="octicon octicon-file" viewBox="0 0 12 16" version="1.1" width="12" height="16" role="img"><path fill-rule="evenodd" d="M6 5H2V4h4v1zM2 8h7V7H2v1zm0 2h7V9H2v1zm0 2h7v-1H2v1zm10-7.5V14c0 .55-.45 1-1 1H1c-.55 0-1-.45-1-1V2c0-.55.45-1 1-1h7.5L12 4.5zM11 5L8 2H1v12h10V5z"/></svg>
+            <img width="16" height="16" class="spinner" alt="" src="https://github.githubassets.com/images/spinners/octocat-spinner-32.gif" />
+          </td>
           <td class="content">
             <span class="css-truncate css-truncate-target"><a class="js-navigation-open" title="indices.clear_cache.json" id="2c9d7dd90e792d3063a65d93493a8d3e-b1b1d8214c47d14716ae18d5553c322fcffbc947" href="/elastic/elasticsearch/blob/master/rest-api-spec/src/main/resources/rest-api-spec/api/indices.clear_cache.json">indices.clear_cache.json</a></span>
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1443,10 +2968,15 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Fixes for API specification (#46522)
+
+Follow-up of #42346" class="link-gray" href="/elastic/elasticsearch/commit/a2a502b330468f8f18202b37eebeb473212b510a">Fixes for API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="491529992" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/46522" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/46522/hovercard" href="https://github.com/elastic/elasticsearch/pull/46522">#46522</a><a data-pjax="true" title="Fixes for API specification (#46522)
+
+Follow-up of #42346" class="link-gray" href="/elastic/elasticsearch/commit/a2a502b330468f8f18202b37eebeb473212b510a">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-09-16T09:23:57Z" class="no-wrap">Sep 16, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1459,10 +2989,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1475,10 +3054,17 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Remove include_type_name from the REST API spec and docs. (#48828)
+
+In #48632 we removed support for `include_type_name` in the REST API. This PR
+removes it from the API spec and documentation." class="link-gray" href="/elastic/elasticsearch/commit/33a7f066e134be1e004759408e9c620f9fa6748b">Remove include_type_name from the REST API spec and docs. (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="516398744" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/48828" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/48828/hovercard" href="https://github.com/elastic/elasticsearch/pull/48828">#48828</a><a data-pjax="true" title="Remove include_type_name from the REST API spec and docs. (#48828)
+
+In #48632 we removed support for `include_type_name` in the REST API. This PR
+removes it from the API spec and documentation." class="link-gray" href="/elastic/elasticsearch/commit/33a7f066e134be1e004759408e9c620f9fa6748b">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-11-12T17:42:46Z" class="no-wrap">Nov 12, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1491,10 +3077,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1507,10 +3142,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1523,10 +3207,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1539,10 +3272,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1555,10 +3337,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1571,10 +3402,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1587,10 +3467,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1603,10 +3532,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1619,10 +3597,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1635,10 +3662,17 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Remove include_type_name from the REST API spec and docs. (#48828)
+
+In #48632 we removed support for `include_type_name` in the REST API. This PR
+removes it from the API spec and documentation." class="link-gray" href="/elastic/elasticsearch/commit/33a7f066e134be1e004759408e9c620f9fa6748b">Remove include_type_name from the REST API spec and docs. (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="516398744" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/48828" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/48828/hovercard" href="https://github.com/elastic/elasticsearch/pull/48828">#48828</a><a data-pjax="true" title="Remove include_type_name from the REST API spec and docs. (#48828)
+
+In #48632 we removed support for `include_type_name` in the REST API. This PR
+removes it from the API spec and documentation." class="link-gray" href="/elastic/elasticsearch/commit/33a7f066e134be1e004759408e9c620f9fa6748b">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-11-12T17:42:46Z" class="no-wrap">Nov 12, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1651,10 +3685,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1667,10 +3750,17 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Remove include_type_name from the REST API spec and docs. (#48828)
+
+In #48632 we removed support for `include_type_name` in the REST API. This PR
+removes it from the API spec and documentation." class="link-gray" href="/elastic/elasticsearch/commit/33a7f066e134be1e004759408e9c620f9fa6748b">Remove include_type_name from the REST API spec and docs. (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="516398744" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/48828" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/48828/hovercard" href="https://github.com/elastic/elasticsearch/pull/48828">#48828</a><a data-pjax="true" title="Remove include_type_name from the REST API spec and docs. (#48828)
+
+In #48632 we removed support for `include_type_name` in the REST API. This PR
+removes it from the API spec and documentation." class="link-gray" href="/elastic/elasticsearch/commit/33a7f066e134be1e004759408e9c620f9fa6748b">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-11-12T17:42:46Z" class="no-wrap">Nov 12, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1683,10 +3773,15 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Removes typed URLs from mapping APIs (#41676)
+
+Relates to #41059" class="link-gray" href="/elastic/elasticsearch/commit/a574a66a21fb96dadf814a1ec1f1715e8b3b2145">Removes typed URLs from mapping APIs (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="438714835" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/41676" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/41676/hovercard" href="https://github.com/elastic/elasticsearch/pull/41676">#41676</a><a data-pjax="true" title="Removes typed URLs from mapping APIs (#41676)
+
+Relates to #41059" class="link-gray" href="/elastic/elasticsearch/commit/a574a66a21fb96dadf814a1ec1f1715e8b3b2145">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-09-23T17:20:07Z" class="no-wrap">Sep 23, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1699,10 +3794,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1715,10 +3859,17 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Remove include_type_name from the REST API spec and docs. (#48828)
+
+In #48632 we removed support for `include_type_name` in the REST API. This PR
+removes it from the API spec and documentation." class="link-gray" href="/elastic/elasticsearch/commit/33a7f066e134be1e004759408e9c620f9fa6748b">Remove include_type_name from the REST API spec and docs. (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="516398744" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/48828" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/48828/hovercard" href="https://github.com/elastic/elasticsearch/pull/48828">#48828</a><a data-pjax="true" title="Remove include_type_name from the REST API spec and docs. (#48828)
+
+In #48632 we removed support for `include_type_name` in the REST API. This PR
+removes it from the API spec and documentation." class="link-gray" href="/elastic/elasticsearch/commit/33a7f066e134be1e004759408e9c620f9fa6748b">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-11-12T17:42:46Z" class="no-wrap">Nov 12, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1731,10 +3882,35 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Deprecates _upgrade API (#47678) (#50484)
+
+* Deprecates _upgrade API
+
+Ref #47678
+
+* Move deprecation flags to path section. Add deprecation warning tests for _upgrade API.
+
+Ref #47678" class="link-gray" href="/elastic/elasticsearch/commit/09ebc11b066872a5ba03c88168ad86b4eb55ad28">Deprecates _upgrade API (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="503582960" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/47678" data-hovercard-type="issue" data-hovercard-url="/elastic/elasticsearch/issues/47678/hovercard" href="https://github.com/elastic/elasticsearch/issues/47678">#47678</a><a data-pjax="true" title="Deprecates _upgrade API (#47678) (#50484)
+
+* Deprecates _upgrade API
+
+Ref #47678
+
+* Move deprecation flags to path section. Add deprecation warning tests for _upgrade API.
+
+Ref #47678" class="link-gray" href="/elastic/elasticsearch/commit/09ebc11b066872a5ba03c88168ad86b4eb55ad28">) (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="542156948" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/50484" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/50484/hovercard" href="https://github.com/elastic/elasticsearch/pull/50484">#50484</a><a data-pjax="true" title="Deprecates _upgrade API (#47678) (#50484)
+
+* Deprecates _upgrade API
+
+Ref #47678
+
+* Move deprecation flags to path section. Add deprecation warning tests for _upgrade API.
+
+Ref #47678" class="link-gray" href="/elastic/elasticsearch/commit/09ebc11b066872a5ba03c88168ad86b4eb55ad28">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2020-01-17T21:52:46Z" class="no-wrap">Jan 17, 2020</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1747,10 +3923,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1763,10 +3988,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1779,10 +4053,11 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Slash miss in indices.put_mapping url" class="link-gray" href="/elastic/elasticsearch/commit/eeda29ac56db6c70ce5990fcdc0d0a8207c98724">Slash miss in indices.put_mapping url</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-11-21T21:59:02Z" class="no-wrap">Nov 21, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1795,10 +4070,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1811,10 +4135,17 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Remove include_type_name from the REST API spec and docs. (#48828)
+
+In #48632 we removed support for `include_type_name` in the REST API. This PR
+removes it from the API spec and documentation." class="link-gray" href="/elastic/elasticsearch/commit/33a7f066e134be1e004759408e9c620f9fa6748b">Remove include_type_name from the REST API spec and docs. (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="516398744" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/48828" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/48828/hovercard" href="https://github.com/elastic/elasticsearch/pull/48828">#48828</a><a data-pjax="true" title="Remove include_type_name from the REST API spec and docs. (#48828)
+
+In #48632 we removed support for `include_type_name` in the REST API. This PR
+removes it from the API spec and documentation." class="link-gray" href="/elastic/elasticsearch/commit/33a7f066e134be1e004759408e9c620f9fa6748b">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-11-12T17:42:46Z" class="no-wrap">Nov 12, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1827,10 +4158,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1843,10 +4223,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1859,10 +4288,17 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Remove include_type_name from the REST API spec and docs. (#48828)
+
+In #48632 we removed support for `include_type_name` in the REST API. This PR
+removes it from the API spec and documentation." class="link-gray" href="/elastic/elasticsearch/commit/33a7f066e134be1e004759408e9c620f9fa6748b">Remove include_type_name from the REST API spec and docs. (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="516398744" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/48828" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/48828/hovercard" href="https://github.com/elastic/elasticsearch/pull/48828">#48828</a><a data-pjax="true" title="Remove include_type_name from the REST API spec and docs. (#48828)
+
+In #48632 we removed support for `include_type_name` in the REST API. This PR
+removes it from the API spec and documentation." class="link-gray" href="/elastic/elasticsearch/commit/33a7f066e134be1e004759408e9c620f9fa6748b">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-11-12T17:42:46Z" class="no-wrap">Nov 12, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1875,10 +4311,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1891,10 +4376,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1907,10 +4441,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1923,10 +4506,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1939,10 +4571,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1955,10 +4636,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1971,10 +4701,35 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Deprecates _upgrade API (#47678) (#50484)
+
+* Deprecates _upgrade API
+
+Ref #47678
+
+* Move deprecation flags to path section. Add deprecation warning tests for _upgrade API.
+
+Ref #47678" class="link-gray" href="/elastic/elasticsearch/commit/09ebc11b066872a5ba03c88168ad86b4eb55ad28">Deprecates _upgrade API (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="503582960" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/47678" data-hovercard-type="issue" data-hovercard-url="/elastic/elasticsearch/issues/47678/hovercard" href="https://github.com/elastic/elasticsearch/issues/47678">#47678</a><a data-pjax="true" title="Deprecates _upgrade API (#47678) (#50484)
+
+* Deprecates _upgrade API
+
+Ref #47678
+
+* Move deprecation flags to path section. Add deprecation warning tests for _upgrade API.
+
+Ref #47678" class="link-gray" href="/elastic/elasticsearch/commit/09ebc11b066872a5ba03c88168ad86b4eb55ad28">) (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="542156948" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/50484" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/50484/hovercard" href="https://github.com/elastic/elasticsearch/pull/50484">#50484</a><a data-pjax="true" title="Deprecates _upgrade API (#47678) (#50484)
+
+* Deprecates _upgrade API
+
+Ref #47678
+
+* Move deprecation flags to path section. Add deprecation warning tests for _upgrade API.
+
+Ref #47678" class="link-gray" href="/elastic/elasticsearch/commit/09ebc11b066872a5ba03c88168ad86b4eb55ad28">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2020-01-17T21:52:46Z" class="no-wrap">Jan 17, 2020</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -1987,10 +4742,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -2003,10 +4807,15 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Fixes for API specification (#46522)
+
+Follow-up of #42346" class="link-gray" href="/elastic/elasticsearch/commit/a2a502b330468f8f18202b37eebeb473212b510a">Fixes for API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="491529992" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/46522" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/46522/hovercard" href="https://github.com/elastic/elasticsearch/pull/46522">#46522</a><a data-pjax="true" title="Fixes for API specification (#46522)
+
+Follow-up of #42346" class="link-gray" href="/elastic/elasticsearch/commit/a2a502b330468f8f18202b37eebeb473212b510a">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-09-16T09:23:57Z" class="no-wrap">Sep 16, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -2035,10 +4844,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -2051,10 +4909,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -2067,10 +4974,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -2083,10 +5039,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -2099,10 +5104,21 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Remove types from Get/MultiGet (#46587)
+
+This commit removes types from the ShardGetService, and propagates this API change
+up through the Transport and Rest actions for Get and MultiGet
+
+Relates to #41059" class="link-gray" href="/elastic/elasticsearch/commit/7c90801aff398d9b73e4fa24933550d2320a5a4d">Remove types from Get/MultiGet (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="492118524" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/46587" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/46587/hovercard" href="https://github.com/elastic/elasticsearch/pull/46587">#46587</a><a data-pjax="true" title="Remove types from Get/MultiGet (#46587)
+
+This commit removes types from the ShardGetService, and propagates this API change
+up through the Transport and Rest actions for Get and MultiGet
+
+Relates to #41059" class="link-gray" href="/elastic/elasticsearch/commit/7c90801aff398d9b73e4fa24933550d2320a5a4d">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-09-20T13:22:57Z" class="no-wrap">Sep 20, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -2115,10 +5131,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -2131,10 +5196,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -2147,10 +5261,15 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Remove force from version_type enum in rest-spec (#49370)
+
+As per #47228 `force` is no longer a valid option" class="link-gray" href="/elastic/elasticsearch/commit/8098276b7ffb72c31967c726d490c3950c40bdf2">Remove force from version_type enum in rest-spec (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="525745740" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/49370" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/49370/hovercard" href="https://github.com/elastic/elasticsearch/pull/49370">#49370</a><a data-pjax="true" title="Remove force from version_type enum in rest-spec (#49370)
+
+As per #47228 `force` is no longer a valid option" class="link-gray" href="/elastic/elasticsearch/commit/8098276b7ffb72c31967c726d490c3950c40bdf2">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-11-26T08:58:33Z" class="no-wrap">Nov 26, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -2163,10 +5282,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -2179,10 +5347,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -2195,10 +5412,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -2211,10 +5477,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -2227,10 +5542,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -2243,10 +5607,15 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Fixes for API specification (#46522)
+
+Follow-up of #42346" class="link-gray" href="/elastic/elasticsearch/commit/a2a502b330468f8f18202b37eebeb473212b510a">Fixes for API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="491529992" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/46522" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/46522/hovercard" href="https://github.com/elastic/elasticsearch/pull/46522">#46522</a><a data-pjax="true" title="Fixes for API specification (#46522)
+
+Follow-up of #42346" class="link-gray" href="/elastic/elasticsearch/commit/a2a502b330468f8f18202b37eebeb473212b510a">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-09-16T09:23:57Z" class="no-wrap">Sep 16, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -2259,10 +5628,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -2275,10 +5693,25 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Support `search_type` in Rank Evaluation API (#48542)
+
+Adding support for the `search_type` request parameter to the Ranking Evaluation
+API since this parameter can impact the ranking and the metric score and should
+be choosen in the same way when evaluating the search as later in the real
+search.
+
+Closes #48503" class="link-gray" href="/elastic/elasticsearch/commit/e5646fefa34104d45cde6a8d797fe23b9db555bc">Support `search_type` in Rank Evaluation API (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="512598439" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/48542" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/48542/hovercard" href="https://github.com/elastic/elasticsearch/pull/48542">#48542</a><a data-pjax="true" title="Support `search_type` in Rank Evaluation API (#48542)
+
+Adding support for the `search_type` request parameter to the Ranking Evaluation
+API since this parameter can impact the ranking and the metric score and should
+be choosen in the same way when evaluating the search as later in the real
+search.
+
+Closes #48503" class="link-gray" href="/elastic/elasticsearch/commit/e5646fefa34104d45cde6a8d797fe23b9db555bc">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-10-29T12:26:41Z" class="no-wrap">Oct 29, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -2291,10 +5724,13 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Fix the type for &quot;slices&quot; in the Reindex and Update By Query REST API specification (#51908)
+
+This patch supplements #51792 and #51535 where the type of the &quot;slices&quot; parameter has been fixed." class="link-gray" href="/elastic/elasticsearch/commit/2ed9e95100474f3dfbeb7efb0529e237b8f61e53">Fix the type for "slices" in the Reindex and Update By Query REST API…</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2020-02-05T08:50:49Z" class="no-wrap">Feb 5, 2020</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -2307,10 +5743,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -2339,10 +5824,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -2355,10 +5889,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -2371,10 +5954,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -2387,10 +6019,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -2403,10 +6084,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -2419,10 +6149,15 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Fixes for API specification (#46522)
+
+Follow-up of #42346" class="link-gray" href="/elastic/elasticsearch/commit/a2a502b330468f8f18202b37eebeb473212b510a">Fixes for API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="491529992" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/46522" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/46522/hovercard" href="https://github.com/elastic/elasticsearch/pull/46522">#46522</a><a data-pjax="true" title="Fixes for API specification (#46522)
+
+Follow-up of #42346" class="link-gray" href="/elastic/elasticsearch/commit/a2a502b330468f8f18202b37eebeb473212b510a">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-09-16T09:23:57Z" class="no-wrap">Sep 16, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -2435,10 +6170,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -2451,10 +6235,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -2467,10 +6300,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -2483,10 +6365,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -2499,10 +6430,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -2515,10 +6495,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -2531,10 +6560,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -2547,10 +6625,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -2563,10 +6690,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -2579,10 +6755,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -2595,10 +6820,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -2611,10 +6885,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -2627,10 +6950,15 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Remove force from version_type enum in rest-spec (#49370)
+
+As per #47228 `force` is no longer a valid option" class="link-gray" href="/elastic/elasticsearch/commit/8098276b7ffb72c31967c726d490c3950c40bdf2">Remove force from version_type enum in rest-spec (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="525745740" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/49370" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/49370/hovercard" href="https://github.com/elastic/elasticsearch/pull/49370">#49370</a><a data-pjax="true" title="Remove force from version_type enum in rest-spec (#49370)
+
+As per #47228 `force` is no longer a valid option" class="link-gray" href="/elastic/elasticsearch/commit/8098276b7ffb72c31967c726d490c3950c40bdf2">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-11-26T08:58:33Z" class="no-wrap">Nov 26, 2019</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -2643,10 +6971,15 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="[DOCS] Fix typos in several REST API specs (#51197)
+
+Changes `effected` to `affected` in several REST API spec files." class="link-gray" href="/elastic/elasticsearch/commit/c3b5f713e2a9fdfc6a9f05892aa7647d905b55d4">[DOCS] Fix typos in several REST API specs (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="551934955" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/51197" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/51197/hovercard" href="https://github.com/elastic/elasticsearch/pull/51197">#51197</a><a data-pjax="true" title="[DOCS] Fix typos in several REST API specs (#51197)
+
+Changes `effected` to `affected` in several REST API spec files." class="link-gray" href="/elastic/elasticsearch/commit/c3b5f713e2a9fdfc6a9f05892aa7647d905b55d4">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2020-01-22T17:17:33Z" class="no-wrap">Jan 22, 2020</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -2659,10 +6992,13 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Fix the type for &quot;slices&quot; in the Reindex and Update By Query REST API specification (#51908)
+
+This patch supplements #51792 and #51535 where the type of the &quot;slices&quot; parameter has been fixed." class="link-gray" href="/elastic/elasticsearch/commit/2ed9e95100474f3dfbeb7efb0529e237b8f61e53">Fix the type for "slices" in the Reindex and Update By Query REST API…</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2020-02-05T08:50:49Z" class="no-wrap">Feb 5, 2020</time-ago></span>
           </td>
         </tr>
         <tr class="js-navigation-item">
@@ -2675,10 +7011,59 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
           </td>
           <td class="message">
             <span class="css-truncate css-truncate-target">
+                  <a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">Update the schema for the REST API specification (</a><a class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="447092756" data-permission-text="Issue title is private" data-url="https://github.com/elastic/elasticsearch/issues/42346" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/42346/hovercard" href="https://github.com/elastic/elasticsearch/pull/42346">#42346</a><a data-pjax="true" title="Update the schema for the REST API specification (#42346)
+
+* Update the REST API specification
+
+This patch updates the REST API spefication in JSON files to better encode deprecated entities,
+to improve specification of URL paths, and to open up the schema for future extensions.
+
+Notably, it changes the `paths` from a list of strings to a list of objects, where each
+particular object encodes all the information for this particular path: the `parts` and the `methods`.
+
+Among the benefits of this approach is eg. encoding the difference between using the `PUT` and `POST`
+methods in the Index API, to either use a specific document ID, or let Elasticsearch generate one.
+
+Also `documentation` becomes an object that supports an `url` and also a `description` which is a
+new field.
+
+* Adapt YAML runner to new REST API specification format
+
+The logic for choosing the path to use when running tests has been
+simplified, as a consequence of the path parts being listed under each
+path in the spec. The special case for create and index has been removed.
+
+Also the parsing code has been hardened so that errors are thrown earlier
+when the structure of the spec differs from what expected, and their
+error messages should be more helpful." class="link-gray" href="/elastic/elasticsearch/commit/91663116221052b9aa05cc183d80c1e546073371">)</a>
             </span>
           </td>
           <td class="age">
-            <span class="css-truncate css-truncate-target"></span>
+            <span class="css-truncate css-truncate-target"><time-ago datetime="2019-08-15T15:15:30Z" class="no-wrap">Aug 15, 2019</time-ago></span>
           </td>
         </tr>
     </tbody>
@@ -2744,9 +7129,9 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
 
 
     <script crossorigin="anonymous" async="async" integrity="sha512-0ME9ftiuUHsYYdeBdLtPHbeL4j0UjTAy9YxHpX0AaZLPPex/JTS5mmHozk8Bnp2czMkd3FmK8DfVID7zxmD5OA==" type="application/javascript" id="js-conditional-compat" data-src="https://github.githubassets.com/assets/compat-bootstrap-d0c13d7e.js"></script>
-    <script crossorigin="anonymous" integrity="sha512-3H5DpgtWsQ6Fe2vBcKjkSmOXvXzISvus5d4D0vQYirHtOTh6xhTJss0rX+7Vvg8ThKo9vOYAGWzZ/P7N9HFqyQ==" type="application/javascript" src="https://github.githubassets.com/assets/frameworks-dc7e43a6.js"></script>
+    <script crossorigin="anonymous" integrity="sha512-X05w7XvoTXbYlPzf+7O1zoqnJFmcZglL7ScKn3ntB9SmLg/1n8D/cNKIKDk7gtKSJ5PegWSCl44onkA40k4xuA==" type="application/javascript" src="https://github.githubassets.com/assets/frameworks-5f4e70ed.js"></script>
     
-    <script crossorigin="anonymous" async="async" integrity="sha512-sZT18rg46eyF0sqSjPYMbuzxyQcNNTo8yunrsoECEUcgmN5WYG4pGy6TfQenjEb+zp4WsKI4MLqIKf/ZL66QJQ==" type="application/javascript" src="https://github.githubassets.com/assets/github-bootstrap-b194f5f2.js"></script>
+    <script crossorigin="anonymous" async="async" integrity="sha512-ZP7K9qwdVB2XvLqj5YhjAYr14NLGXPrxxYQpRjyUU0tI1WNahUL1fv5i1eWLMviB3G6t/13jD+F8D96vBK30oA==" type="application/javascript" src="https://github.githubassets.com/assets/github-bootstrap-64fecaf6.js"></script>
     
     
     
@@ -2773,9 +7158,6 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
   </div>
 </div>
 
-    
-  <div class="js-notification-shelf-not-found-error" hidden></div>
-
   <div aria-live="polite" class="js-global-screen-reader-notice sr-only"></div>
 
   </body>
diff --git a/src/ApiGenerator/RestSpecification/XPack/cat.ml_data_frame_analytics.json b/src/ApiGenerator/RestSpecification/XPack/cat.ml_data_frame_analytics.json
new file mode 100644
index 00000000000..f8e3f4c46ea
--- /dev/null
+++ b/src/ApiGenerator/RestSpecification/XPack/cat.ml_data_frame_analytics.json
@@ -0,0 +1,89 @@
+{
+  "cat.ml_data_frame_analytics":{
+    "documentation":{
+      "url":"http://www.elastic.co/guide/en/elasticsearch/reference/current/get-dfanalytics-stats.html"
+    },
+    "stability":"stable",
+    "url":{
+      "paths":[
+        {
+          "path":"/_cat/ml/data_frame/analytics",
+          "methods":[
+            "GET"
+          ]
+        },
+        {
+          "path":"/_cat/ml/data_frame/analytics/{id}",
+          "methods":[
+            "GET"
+          ],
+          "parts":{
+            "id":{
+              "type":"string",
+              "description":"The ID of the data frame analytics to fetch"
+            }
+          }
+        }
+      ]
+    },
+    "params":{
+      "allow_no_match":{
+        "type":"boolean",
+        "required":false,
+        "description":"Whether to ignore if a wildcard expression matches no configs. (This includes `_all` string or when no configs have been specified)"
+      },
+      "bytes":{
+        "type":"enum",
+        "description":"The unit in which to display byte values",
+        "options":[
+          "b",
+          "k",
+          "kb",
+          "m",
+          "mb",
+          "g",
+          "gb",
+          "t",
+          "tb",
+          "p",
+          "pb"
+        ]
+      },
+      "format":{
+        "type":"string",
+        "description":"a short version of the Accept header, e.g. json, yaml"
+      },
+      "h":{
+        "type":"list",
+        "description":"Comma-separated list of column names to display"
+      },
+      "help":{
+        "type":"boolean",
+        "description":"Return help information",
+        "default":false
+      },
+      "s":{
+        "type":"list",
+        "description":"Comma-separated list of column names or column aliases to sort by"
+      },
+      "time":{
+        "type":"enum",
+        "description":"The unit in which to display time values",
+        "options":[
+          "d (Days)",
+          "h (Hours)",
+          "m (Minutes)",
+          "s (Seconds)",
+          "ms (Milliseconds)",
+          "micros (Microseconds)",
+          "nanos (Nanoseconds)"
+        ]
+      },
+      "v":{
+        "type":"boolean",
+        "description":"Verbose mode. Display column headers",
+        "default":false
+      }
+    }
+  }
+}
diff --git a/src/ApiGenerator/RestSpecification/XPack/root.html b/src/ApiGenerator/RestSpecification/XPack/root.html
index 0d07728aae3..bdf2ba249ab 100644
--- a/src/ApiGenerator/RestSpecification/XPack/root.html
+++ b/src/ApiGenerator/RestSpecification/XPack/root.html
@@ -18,9 +18,9 @@
 
 
 
-  <link crossorigin="anonymous" media="all" integrity="sha512-Wr5yTs8gD42bv1Ll5KLXr7cXzuVcbKOcuHmifgt/6YlZuluDTyAJnfnYhNYKpgVK1F51ks8Y2QA+XENQoMp/PA==" rel="stylesheet" href="https://github.githubassets.com/assets/frameworks-5abe724ecf200f8d9bbf52e5e4a2d7af.css" />
-  <link crossorigin="anonymous" media="all" integrity="sha512-DnBQhWGJ7icZU4LPhD6FlaZ9IrBOmbP4/4bEfpGQRbCLwutaFNqbuAaM8Y/w7IygRCMuOybM7fLDGe+UV9TEjQ==" rel="stylesheet" href="https://github.githubassets.com/assets/site-0e7050856189ee27195382cf843e8595.css" />
-    <link crossorigin="anonymous" media="all" integrity="sha512-/Kdj6P6WRk2SG1AIisQL1y+ZbNnTv1a+pX/4yP0e13VjZ5s+uYXnQOx+NKpXpBPqzyB/JscjxW7D30/a5DneZA==" rel="stylesheet" href="https://github.githubassets.com/assets/github-fca763e8fe96464d921b50088ac40bd7.css" />
+  <link crossorigin="anonymous" media="all" integrity="sha512-ZUjVod2EvYMDbGqRSyW0rpfgBq3i+gnR/4PfrzLsy5f20oIcRfgFQFVKgi3Ztp917bP1K/kdP5q8+nAlJ3+cFA==" rel="stylesheet" href="https://github.githubassets.com/assets/frameworks-6548d5a1dd84bd83036c6a914b25b4ae.css" />
+  <link crossorigin="anonymous" media="all" integrity="sha512-HNV7VuXI98SSFimaE7r8eVsgrmzC37AMNXw1GrNbOl4wN3ATov+SdHusRTAAf4NPoRsUcOOQyYsOCA0AcN4m0w==" rel="stylesheet" href="https://github.githubassets.com/assets/site-1cd57b56e5c8f7c49216299a13bafc79.css" />
+    <link crossorigin="anonymous" media="all" integrity="sha512-CKBn/UfyE+yEuqeavkB8Y5xld809yQJ0Evsa+pOoHP8jlBS0TGBeKIiOs17M57SuJMEZl3wjXuB2pexW8oEeuA==" rel="stylesheet" href="https://github.githubassets.com/assets/github-08a067fd47f213ec84baa79abe407c63.css" />
     
     
     
@@ -42,7 +42,7 @@
   
   
 
-    <meta name="request-id" content="A224:2C646:8B6F2:DBB09:5E41B8DE" data-pjax-transient="true" /><meta name="html-safe-nonce" content="e945098b1aa2d88fb8afb48d85dfdbb381ec5e9b" data-pjax-transient="true" /><meta name="visitor-payload" content="eyJyZWZlcnJlciI6bnVsbCwicmVxdWVzdF9pZCI6IkEyMjQ6MkM2NDY6OEI2RjI6REJCMDk6NUU0MUI4REUiLCJ2aXNpdG9yX2lkIjoiODM2OTQzMTAwMjY2OTQ5NjU0MiIsInJlZ2lvbl9lZGdlIjoiYW1zIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9" data-pjax-transient="true" /><meta name="visitor-hmac" content="b0ce388244da3043050ac1b08419952a6ad800240d912890ede28140da185f52" data-pjax-transient="true" />
+  <meta name="request-id" content="B1B4:1D25A:1311286:1C18780:5E4D1601" data-pjax-transient="true"/><meta name="html-safe-nonce" content="659d40eeb402494e8daf470bad8968179482055c" data-pjax-transient="true"/><meta name="visitor-payload" content="eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJCMUI0OjFEMjVBOjEzMTEyODY6MUMxODc4MDo1RTREMTYwMSIsInZpc2l0b3JfaWQiOiIxMjE4ODI5Mzk5OTAyODM3NzciLCJyZWdpb25fZWRnZSI6ImFtcyIsInJlZ2lvbl9yZW5kZXIiOiJhbXMifQ==" data-pjax-transient="true"/><meta name="visitor-hmac" content="eec886c3a76a9b3d39981132bb2d0e1864458f583f162f26b25803e798231307" data-pjax-transient="true"/>
 
 
 
@@ -78,7 +78,7 @@
 
     <meta name="enabled-features" content="MARKETPLACE_FEATURED_BLOG_POSTS,MARKETPLACE_INVOICED_BILLING,MARKETPLACE_SOCIAL_PROOF_CUSTOMERS,MARKETPLACE_TRENDING_SOCIAL_PROOF,MARKETPLACE_RECOMMENDATIONS,MARKETPLACE_PENDING_INSTALLATIONS,RELATED_ISSUES">
 
-  <meta http-equiv="x-pjax-version" content="b41dafcb41e2ceb6409cd7968585d6e9">
+  <meta http-equiv="x-pjax-version" content="2e63e6bd8ece9826eb61af0c1a5496f1">
   
 
       <link href="https://github.com/elastic/elasticsearch/commits/master.atom" rel="alternate" title="Recent Commits to elasticsearch:master" type="application/atom+xml">
@@ -260,7 +260,7 @@ <h4 class="text-gray-light text-normal text-mono f5 mb-2  border-top pt-3">Conne
           spellcheck="false"
           autocomplete="off"
           >
-            <input type="hidden" value="meQhfLpqBj+3r0iPC1jzy4zzVRnFWV15lY94/WCPHmiotimjtj4I0uG30/f7jNvk4nhthjXYmngyTOFdgu3WXw==" data-csrf="true" class="js-data-jump-to-suggestions-path-csrf" />
+          <input type="hidden" data-csrf="true" class="js-data-jump-to-suggestions-path-csrf" value="dmqXuZDeqaWhRBrBvfa9tXHeKoEG1adLnCmPqdJQQdTKtqprHB83s4FEOhpmKIMekLpaIqJLGTlBnUgjzELTag==" />
           <input type="hidden" class="js-site-search-type-field" name="type" >
             <img src="https://github.githubassets.com/images/search-key-slash.svg" alt="" class="mr-2 header-search-key-slash">
 
@@ -409,6 +409,11 @@ <h4 class="text-gray-light text-normal text-mono f5 mb-2  border-top pt-3">Conne
 </div>
 
 
+      
+
+  <div class="js-notification-shelf-not-found-error" hidden></div>
+
+
 
 
   <div class="application-main " data-commit-hovercards-enabled>
@@ -419,6 +424,7 @@ <h4 class="text-gray-light text-normal text-mono f5 mb-2  border-top pt-3">Conne
 
 
 
+
   
 
 
@@ -429,7 +435,7 @@ <h4 class="text-gray-light text-normal text-mono f5 mb-2  border-top pt-3">Conne
 
 
 
-  <div class="pagehead repohead readability-menu bg-gray-light pb-0 pt-3  pb-0">
+  <div class="pagehead repohead hx_repohead readability-menu bg-gray-light pb-0 pt-3  pb-0">
 
     <div class="container-lg mb-4 px-3 d-flex">
 
@@ -460,7 +466,7 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
     <svg class="octicon octicon-eye v-align-text-bottom" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M8.06 2C3 2 0 8 0 8s3 6 8.06 6C13 14 16 8 16 8s-3-6-7.94-6zM8 12c-2.2 0-4-1.78-4-4 0-2.2 1.8-4 4-4 2.22 0 4 1.8 4 4 0 2.22-1.78 4-4 4zm2-4c0 1.11-.89 2-2 2-1.11 0-2-.89-2-2 0-1.11.89-2 2-2 1.11 0 2 .89 2 2z"/></svg>
     Watch
 </a>    <a class="social-count" href="/elastic/elasticsearch/watchers"
-       aria-label="2785 users are watching this repository">
+       aria-label="2782 users are watching this repository">
       2.8k
     </a>
 
@@ -473,8 +479,8 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
       Star
 </a>
     <a class="social-count js-social-count" href="/elastic/elasticsearch/stargazers"
-      aria-label="46944 users starred this repository">
-      46.9k
+      aria-label="47080 users starred this repository">
+      47.1k
     </a>
 
   </li>
@@ -485,8 +491,8 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
         Fork
 </a>
     <a href="/elastic/elasticsearch/network/members" class="social-count"
-       aria-label="15937 users forked this repository">
-      15.9k
+       aria-label="16000 users forked this repository">
+      16k
     </a>
   </li>
 </ul>
@@ -510,7 +516,7 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
       <a itemprop="url" data-hotkey="g i" class="js-selected-navigation-item reponav-item" data-selected-links="repo_issues repo_labels repo_milestones /elastic/elasticsearch/issues" href="/elastic/elasticsearch/issues">
         <div class="d-inline"><svg class="octicon octicon-issue-opened" viewBox="0 0 14 16" version="1.1" width="14" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M7 2.3c3.14 0 5.7 2.56 5.7 5.7s-2.56 5.7-5.7 5.7A5.71 5.71 0 011.3 8c0-3.14 2.56-5.7 5.7-5.7zM7 1C3.14 1 0 4.14 0 8s3.14 7 7 7 7-3.14 7-7-3.14-7-7-7zm1 3H6v5h2V4zm0 6H6v2h2v-2z"/></svg></div>
         <span itemprop="name">Issues</span>
-        <span class="Counter">2,166</span>
+        <span class="Counter">2,197</span>
         <meta itemprop="position" content="2">
 </a>    </span>
 
@@ -519,7 +525,7 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
     <a data-hotkey="g p" data-skip-pjax="true" itemprop="url" class="js-selected-navigation-item reponav-item" data-selected-links="repo_pulls checks /elastic/elasticsearch/pulls" href="/elastic/elasticsearch/pulls">
       <div class="d-inline"><svg class="octicon octicon-git-pull-request" viewBox="0 0 12 16" version="1.1" width="12" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M11 11.28V5c-.03-.78-.34-1.47-.94-2.06C9.46 2.35 8.78 2.03 8 2H7V0L4 3l3 3V4h1c.27.02.48.11.69.31.21.2.3.42.31.69v6.28A1.993 1.993 0 0010 15a1.993 1.993 0 001-3.72zm-1 2.92c-.66 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2zM4 3c0-1.11-.89-2-2-2a1.993 1.993 0 00-1 3.72v6.56A1.993 1.993 0 002 15a1.993 1.993 0 001-3.72V4.72c.59-.34 1-.98 1-1.72zm-.8 10c0 .66-.55 1.2-1.2 1.2-.65 0-1.2-.55-1.2-1.2 0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2zM2 4.2C1.34 4.2.8 3.65.8 3c0-.65.55-1.2 1.2-1.2.65 0 1.2.55 1.2 1.2 0 .65-.55 1.2-1.2 1.2z"/></svg></div>
       <span itemprop="name">Pull requests</span>
-      <span class="Counter">311</span>
+      <span class="Counter">315</span>
       <meta itemprop="position" content="4">
 </a>  </span>
 
@@ -549,6 +555,8 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
 
 
   </div>
+
+
 <div class="container-lg clearfix new-discussion-timeline  px-3">
   <div class="repository-content ">
 
@@ -596,10 +604,10 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
 
   
 
-<include-fragment src="/elastic/elasticsearch/tree-commit/bb62ebfa3dd2a199182154b2bbadb076b31c1eb0/x-pack/plugin/src/test/resources/rest-api-spec/api" class="commit-tease commit-loader">
+<include-fragment src="/elastic/elasticsearch/tree-commit/a2c1f2d1219f481a46b001d15b6454dd65c958d7/x-pack/plugin/src/test/resources/rest-api-spec/api" class="commit-tease commit-loader">
   <div class="blank loader-loading">
-      <img alt="" class="loader" src="https://github.githubassets.com/images/spinners/octocat-spinner-32-EAF2F5.gif" width="16" height="16" />
-      Fetching latest commit…
+    <img alt="" class="loader" src="https://github.githubassets.com/images/spinners/octocat-spinner-32-EAF2F5.gif" width="16" height="16" />
+    Fetching latest commit…
   </div>
   <div class="loader-error">
     Cannot retrieve the latest commit at this time.
@@ -608,7 +616,7 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
 
 
 <include-fragment class="file-wrap" src="/elastic/elasticsearch/file-list/master/x-pack/plugin/src/test/resources/rest-api-spec/api">
-  <a class="d-none js-permalink-shortcut" data-hotkey="y" href="/elastic/elasticsearch/tree/bb62ebfa3dd2a199182154b2bbadb076b31c1eb0/x-pack/plugin/src/test/resources/rest-api-spec/api">Permalink</a>
+  <a class="d-none js-permalink-shortcut" data-hotkey="y" href="/elastic/elasticsearch/tree/a2c1f2d1219f481a46b001d15b6454dd65c958d7/x-pack/plugin/src/test/resources/rest-api-spec/api">Permalink</a>
 
   <table class="files js-navigation-container js-active-navigation-container" data-pjax>
     <thead>
@@ -649,6 +657,22 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
             <span class="css-truncate css-truncate-target"></span>
           </td>
         </tr>
+        <tr class="js-navigation-item">
+          <td class="icon">
+            <svg aria-label="file" class="octicon octicon-file" viewBox="0 0 12 16" version="1.1" width="12" height="16" role="img"><path fill-rule="evenodd" d="M6 5H2V4h4v1zM2 8h7V7H2v1zm0 2h7V9H2v1zm0 2h7v-1H2v1zm10-7.5V14c0 .55-.45 1-1 1H1c-.55 0-1-.45-1-1V2c0-.55.45-1 1-1h7.5L12 4.5zM11 5L8 2H1v12h10V5z"/></svg>
+            <img width="16" height="16" class="spinner" alt="" src="https://github.githubassets.com/images/spinners/octocat-spinner-32.gif" />
+          </td>
+          <td class="content">
+            <span class="css-truncate css-truncate-target"><a class="js-navigation-open" title="cat.ml_data_frame_analytics.json" id="6b87ef4808c48f22024d27786251b037-f8e3f4c46ea1ecd0cdfd6d264f2b11f0d8606517" href="/elastic/elasticsearch/blob/master/x-pack/plugin/src/test/resources/rest-api-spec/api/cat.ml_data_frame_analytics.json">cat.ml_data_frame_analytics.json</a></span>
+          </td>
+          <td class="message">
+            <span class="css-truncate css-truncate-target">
+            </span>
+          </td>
+          <td class="age">
+            <span class="css-truncate css-truncate-target"></span>
+          </td>
+        </tr>
         <tr class="js-navigation-item">
           <td class="icon">
             <svg aria-label="file" class="octicon octicon-file" viewBox="0 0 12 16" version="1.1" width="12" height="16" role="img"><path fill-rule="evenodd" d="M6 5H2V4h4v1zM2 8h7V7H2v1zm0 2h7V9H2v1zm0 2h7v-1H2v1zm10-7.5V14c0 .55-.45 1-1 1H1c-.55 0-1-.45-1-1V2c0-.55.45-1 1-1h7.5L12 4.5zM11 5L8 2H1v12h10V5z"/></svg>
@@ -3560,9 +3584,9 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
 
 
     <script crossorigin="anonymous" async="async" integrity="sha512-0ME9ftiuUHsYYdeBdLtPHbeL4j0UjTAy9YxHpX0AaZLPPex/JTS5mmHozk8Bnp2czMkd3FmK8DfVID7zxmD5OA==" type="application/javascript" id="js-conditional-compat" data-src="https://github.githubassets.com/assets/compat-bootstrap-d0c13d7e.js"></script>
-    <script crossorigin="anonymous" integrity="sha512-3H5DpgtWsQ6Fe2vBcKjkSmOXvXzISvus5d4D0vQYirHtOTh6xhTJss0rX+7Vvg8ThKo9vOYAGWzZ/P7N9HFqyQ==" type="application/javascript" src="https://github.githubassets.com/assets/frameworks-dc7e43a6.js"></script>
+    <script crossorigin="anonymous" integrity="sha512-X05w7XvoTXbYlPzf+7O1zoqnJFmcZglL7ScKn3ntB9SmLg/1n8D/cNKIKDk7gtKSJ5PegWSCl44onkA40k4xuA==" type="application/javascript" src="https://github.githubassets.com/assets/frameworks-5f4e70ed.js"></script>
     
-    <script crossorigin="anonymous" async="async" integrity="sha512-sZT18rg46eyF0sqSjPYMbuzxyQcNNTo8yunrsoECEUcgmN5WYG4pGy6TfQenjEb+zp4WsKI4MLqIKf/ZL66QJQ==" type="application/javascript" src="https://github.githubassets.com/assets/github-bootstrap-b194f5f2.js"></script>
+    <script crossorigin="anonymous" async="async" integrity="sha512-ZP7K9qwdVB2XvLqj5YhjAYr14NLGXPrxxYQpRjyUU0tI1WNahUL1fv5i1eWLMviB3G6t/13jD+F8D96vBK30oA==" type="application/javascript" src="https://github.githubassets.com/assets/github-bootstrap-64fecaf6.js"></script>
     
     
     
@@ -3589,9 +3613,6 @@ <h1 class="public  d-flex flex-wrap flex-items-center break-word float-none ">
   </div>
 </div>
 
-    
-  <div class="js-notification-shelf-not-found-error" hidden></div>
-
   <div aria-live="polite" class="js-global-screen-reader-notice sr-only"></div>
 
   </body>
diff --git a/src/Elasticsearch.Net/Api/RequestParameters/RequestParameters.Cat.cs b/src/Elasticsearch.Net/Api/RequestParameters/RequestParameters.Cat.cs
index ae087b88017..6c156d54e75 100644
--- a/src/Elasticsearch.Net/Api/RequestParameters/RequestParameters.Cat.cs
+++ b/src/Elasticsearch.Net/Api/RequestParameters/RequestParameters.Cat.cs
@@ -464,7 +464,66 @@ public bool? Verbose
 		}
 	}
 
-	///<summary>Request options for MlDatafeeds <para>http://www.elastic.co/guide/en/elasticsearch/reference/current/ml-get-datafeed-stats.html</para></summary>
+	///<summary>Request options for MlDataFrameAnalytics <para>https://www.elastic.co/guide/en/elasticsearch/reference/current/get-dfanalytics-stats.html</para></summary>
+	public class MlDataFrameAnalyticsRequestParameters : RequestParameters<MlDataFrameAnalyticsRequestParameters>
+	{
+		public override HttpMethod DefaultHttpMethod => HttpMethod.GET;
+		public override bool SupportsBody => false;
+		///<summary>Whether to ignore if a wildcard expression matches no configs. (This includes `_all` string or when no configs have been specified)</summary>
+		public bool? AllowNoMatch
+		{
+			get => Q<bool? >("allow_no_match");
+			set => Q("allow_no_match", value);
+		}
+
+		///<summary>The unit in which to display byte values</summary>
+		public Bytes? Bytes
+		{
+			get => Q<Bytes? >("bytes");
+			set => Q("bytes", value);
+		}
+
+		///<summary>a short version of the Accept header, e.g. json, yaml</summary>
+		public string Format
+		{
+			get => Q<string>("format");
+			set
+			{
+				Q("format", value);
+				SetAcceptHeader(value);
+			}
+		}
+
+		///<summary>Comma-separated list of column names to display</summary>
+		public string[] Headers
+		{
+			get => Q<string[]>("h");
+			set => Q("h", value);
+		}
+
+		///<summary>Return help information</summary>
+		public bool? Help
+		{
+			get => Q<bool? >("help");
+			set => Q("help", value);
+		}
+
+		///<summary>Comma-separated list of column names or column aliases to sort by</summary>
+		public string[] SortByColumns
+		{
+			get => Q<string[]>("s");
+			set => Q("s", value);
+		}
+
+		///<summary>Verbose mode. Display column headers</summary>
+		public bool? Verbose
+		{
+			get => Q<bool? >("v");
+			set => Q("v", value);
+		}
+	}
+
+	///<summary>Request options for MlDatafeeds <para>https://www.elastic.co/guide/en/elasticsearch/reference/current/ml-get-datafeed-stats.html</para></summary>
 	public class MlDatafeedsRequestParameters : RequestParameters<MlDatafeedsRequestParameters>
 	{
 		public override HttpMethod DefaultHttpMethod => HttpMethod.GET;
@@ -516,7 +575,7 @@ public bool? Verbose
 		}
 	}
 
-	///<summary>Request options for MlJobs <para>http://www.elastic.co/guide/en/elasticsearch/reference/current/ml-get-job-stats.html</para></summary>
+	///<summary>Request options for MlJobs <para>https://www.elastic.co/guide/en/elasticsearch/reference/current/ml-get-job-stats.html</para></summary>
 	public class MlJobsRequestParameters : RequestParameters<MlJobsRequestParameters>
 	{
 		public override HttpMethod DefaultHttpMethod => HttpMethod.GET;
diff --git a/src/Elasticsearch.Net/Api/RequestParameters/RequestParameters.MachineLearning.cs b/src/Elasticsearch.Net/Api/RequestParameters/RequestParameters.MachineLearning.cs
index cb51d343184..b60d9b773d6 100644
--- a/src/Elasticsearch.Net/Api/RequestParameters/RequestParameters.MachineLearning.cs
+++ b/src/Elasticsearch.Net/Api/RequestParameters/RequestParameters.MachineLearning.cs
@@ -166,7 +166,7 @@ public class DeleteTrainedModelRequestParameters : RequestParameters<DeleteTrain
 		public override bool SupportsBody => false;
 	}
 
-	///<summary>Request options for EstimateMemoryUsage <para>http://www.elastic.co/guide/en/elasticsearch/reference/current/estimate-memory-usage-dfanalytics.html</para></summary>
+	///<summary>Request options for EstimateMemoryUsage <para>https://www.elastic.co/guide/en/elasticsearch/reference/current/estimate-memory-usage-dfanalytics.html</para></summary>
 	public class EstimateMemoryUsageRequestParameters : RequestParameters<EstimateMemoryUsageRequestParameters>
 	{
 		public override HttpMethod DefaultHttpMethod => HttpMethod.POST;
@@ -180,7 +180,7 @@ public class EvaluateDataFrameRequestParameters : RequestParameters<EvaluateData
 		public override bool SupportsBody => true;
 	}
 
-	///<summary>Request options for ExplainDataFrameAnalytics <para>http://www.elastic.co/guide/en/elasticsearch/reference/current/explain-dfanalytics.html</para></summary>
+	///<summary>Request options for ExplainDataFrameAnalytics <para>https://www.elastic.co/guide/en/elasticsearch/reference/current/explain-dfanalytics.html</para></summary>
 	public class ExplainDataFrameAnalyticsRequestParameters : RequestParameters<ExplainDataFrameAnalyticsRequestParameters>
 	{
 		public override HttpMethod DefaultHttpMethod => HttpMethod.POST;
diff --git a/src/Elasticsearch.Net/ElasticLowLevelClient.Cat.cs b/src/Elasticsearch.Net/ElasticLowLevelClient.Cat.cs
index 8ac477ad24a..16b24548c12 100644
--- a/src/Elasticsearch.Net/ElasticLowLevelClient.Cat.cs
+++ b/src/Elasticsearch.Net/ElasticLowLevelClient.Cat.cs
@@ -176,41 +176,61 @@ public TResponse Master<TResponse>(CatMasterRequestParameters requestParameters
 		[MapsApi("cat.master", "")]
 		public Task<TResponse> MasterAsync<TResponse>(CatMasterRequestParameters requestParameters = null, CancellationToken ctx = default)
 			where TResponse : class, IElasticsearchResponse, new() => DoRequestAsync<TResponse>(GET, "_cat/master", ctx, null, RequestParams(requestParameters));
-		///<summary>GET on /_cat/ml/datafeeds <para>http://www.elastic.co/guide/en/elasticsearch/reference/current/ml-get-datafeed-stats.html</para></summary>
+		///<summary>GET on /_cat/ml/data_frame/analytics <para>https://www.elastic.co/guide/en/elasticsearch/reference/current/get-dfanalytics-stats.html</para></summary>
+		///<param name = "requestParameters">Request specific configuration such as querystring parameters &amp; request specific connection settings.</param>
+		public TResponse MlDataFrameAnalytics<TResponse>(MlDataFrameAnalyticsRequestParameters requestParameters = null)
+			where TResponse : class, IElasticsearchResponse, new() => DoRequest<TResponse>(GET, "_cat/ml/data_frame/analytics", null, RequestParams(requestParameters));
+		///<summary>GET on /_cat/ml/data_frame/analytics <para>https://www.elastic.co/guide/en/elasticsearch/reference/current/get-dfanalytics-stats.html</para></summary>
+		///<param name = "requestParameters">Request specific configuration such as querystring parameters &amp; request specific connection settings.</param>
+		[MapsApi("cat.ml_data_frame_analytics", "")]
+		public Task<TResponse> MlDataFrameAnalyticsAsync<TResponse>(MlDataFrameAnalyticsRequestParameters requestParameters = null, CancellationToken ctx = default)
+			where TResponse : class, IElasticsearchResponse, new() => DoRequestAsync<TResponse>(GET, "_cat/ml/data_frame/analytics", ctx, null, RequestParams(requestParameters));
+		///<summary>GET on /_cat/ml/data_frame/analytics/{id} <para>https://www.elastic.co/guide/en/elasticsearch/reference/current/get-dfanalytics-stats.html</para></summary>
+		///<param name = "id">The ID of the data frame analytics to fetch</param>
+		///<param name = "requestParameters">Request specific configuration such as querystring parameters &amp; request specific connection settings.</param>
+		public TResponse MlDataFrameAnalytics<TResponse>(string id, MlDataFrameAnalyticsRequestParameters requestParameters = null)
+			where TResponse : class, IElasticsearchResponse, new() => DoRequest<TResponse>(GET, Url($"_cat/ml/data_frame/analytics/{id:id}"), null, RequestParams(requestParameters));
+		///<summary>GET on /_cat/ml/data_frame/analytics/{id} <para>https://www.elastic.co/guide/en/elasticsearch/reference/current/get-dfanalytics-stats.html</para></summary>
+		///<param name = "id">The ID of the data frame analytics to fetch</param>
+		///<param name = "requestParameters">Request specific configuration such as querystring parameters &amp; request specific connection settings.</param>
+		[MapsApi("cat.ml_data_frame_analytics", "id")]
+		public Task<TResponse> MlDataFrameAnalyticsAsync<TResponse>(string id, MlDataFrameAnalyticsRequestParameters requestParameters = null, CancellationToken ctx = default)
+			where TResponse : class, IElasticsearchResponse, new() => DoRequestAsync<TResponse>(GET, Url($"_cat/ml/data_frame/analytics/{id:id}"), ctx, null, RequestParams(requestParameters));
+		///<summary>GET on /_cat/ml/datafeeds <para>https://www.elastic.co/guide/en/elasticsearch/reference/current/ml-get-datafeed-stats.html</para></summary>
 		///<param name = "requestParameters">Request specific configuration such as querystring parameters &amp; request specific connection settings.</param>
 		public TResponse MlDatafeeds<TResponse>(MlDatafeedsRequestParameters requestParameters = null)
 			where TResponse : class, IElasticsearchResponse, new() => DoRequest<TResponse>(GET, "_cat/ml/datafeeds", null, RequestParams(requestParameters));
-		///<summary>GET on /_cat/ml/datafeeds <para>http://www.elastic.co/guide/en/elasticsearch/reference/current/ml-get-datafeed-stats.html</para></summary>
+		///<summary>GET on /_cat/ml/datafeeds <para>https://www.elastic.co/guide/en/elasticsearch/reference/current/ml-get-datafeed-stats.html</para></summary>
 		///<param name = "requestParameters">Request specific configuration such as querystring parameters &amp; request specific connection settings.</param>
 		[MapsApi("cat.ml_datafeeds", "")]
 		public Task<TResponse> MlDatafeedsAsync<TResponse>(MlDatafeedsRequestParameters requestParameters = null, CancellationToken ctx = default)
 			where TResponse : class, IElasticsearchResponse, new() => DoRequestAsync<TResponse>(GET, "_cat/ml/datafeeds", ctx, null, RequestParams(requestParameters));
-		///<summary>GET on /_cat/ml/datafeeds/{datafeed_id} <para>http://www.elastic.co/guide/en/elasticsearch/reference/current/ml-get-datafeed-stats.html</para></summary>
+		///<summary>GET on /_cat/ml/datafeeds/{datafeed_id} <para>https://www.elastic.co/guide/en/elasticsearch/reference/current/ml-get-datafeed-stats.html</para></summary>
 		///<param name = "datafeedId">The ID of the datafeeds stats to fetch</param>
 		///<param name = "requestParameters">Request specific configuration such as querystring parameters &amp; request specific connection settings.</param>
 		public TResponse MlDatafeeds<TResponse>(string datafeedId, MlDatafeedsRequestParameters requestParameters = null)
 			where TResponse : class, IElasticsearchResponse, new() => DoRequest<TResponse>(GET, Url($"_cat/ml/datafeeds/{datafeedId:datafeedId}"), null, RequestParams(requestParameters));
-		///<summary>GET on /_cat/ml/datafeeds/{datafeed_id} <para>http://www.elastic.co/guide/en/elasticsearch/reference/current/ml-get-datafeed-stats.html</para></summary>
+		///<summary>GET on /_cat/ml/datafeeds/{datafeed_id} <para>https://www.elastic.co/guide/en/elasticsearch/reference/current/ml-get-datafeed-stats.html</para></summary>
 		///<param name = "datafeedId">The ID of the datafeeds stats to fetch</param>
 		///<param name = "requestParameters">Request specific configuration such as querystring parameters &amp; request specific connection settings.</param>
 		[MapsApi("cat.ml_datafeeds", "datafeed_id")]
 		public Task<TResponse> MlDatafeedsAsync<TResponse>(string datafeedId, MlDatafeedsRequestParameters requestParameters = null, CancellationToken ctx = default)
 			where TResponse : class, IElasticsearchResponse, new() => DoRequestAsync<TResponse>(GET, Url($"_cat/ml/datafeeds/{datafeedId:datafeedId}"), ctx, null, RequestParams(requestParameters));
-		///<summary>GET on /_cat/ml/anomaly_detectors <para>http://www.elastic.co/guide/en/elasticsearch/reference/current/ml-get-job-stats.html</para></summary>
+		///<summary>GET on /_cat/ml/anomaly_detectors <para>https://www.elastic.co/guide/en/elasticsearch/reference/current/ml-get-job-stats.html</para></summary>
 		///<param name = "requestParameters">Request specific configuration such as querystring parameters &amp; request specific connection settings.</param>
 		public TResponse MlJobs<TResponse>(MlJobsRequestParameters requestParameters = null)
 			where TResponse : class, IElasticsearchResponse, new() => DoRequest<TResponse>(GET, "_cat/ml/anomaly_detectors", null, RequestParams(requestParameters));
-		///<summary>GET on /_cat/ml/anomaly_detectors <para>http://www.elastic.co/guide/en/elasticsearch/reference/current/ml-get-job-stats.html</para></summary>
+		///<summary>GET on /_cat/ml/anomaly_detectors <para>https://www.elastic.co/guide/en/elasticsearch/reference/current/ml-get-job-stats.html</para></summary>
 		///<param name = "requestParameters">Request specific configuration such as querystring parameters &amp; request specific connection settings.</param>
 		[MapsApi("cat.ml_jobs", "")]
 		public Task<TResponse> MlJobsAsync<TResponse>(MlJobsRequestParameters requestParameters = null, CancellationToken ctx = default)
 			where TResponse : class, IElasticsearchResponse, new() => DoRequestAsync<TResponse>(GET, "_cat/ml/anomaly_detectors", ctx, null, RequestParams(requestParameters));
-		///<summary>GET on /_cat/ml/anomaly_detectors/{job_id} <para>http://www.elastic.co/guide/en/elasticsearch/reference/current/ml-get-job-stats.html</para></summary>
+		///<summary>GET on /_cat/ml/anomaly_detectors/{job_id} <para>https://www.elastic.co/guide/en/elasticsearch/reference/current/ml-get-job-stats.html</para></summary>
 		///<param name = "jobId">The ID of the jobs stats to fetch</param>
 		///<param name = "requestParameters">Request specific configuration such as querystring parameters &amp; request specific connection settings.</param>
 		public TResponse MlJobs<TResponse>(string jobId, MlJobsRequestParameters requestParameters = null)
 			where TResponse : class, IElasticsearchResponse, new() => DoRequest<TResponse>(GET, Url($"_cat/ml/anomaly_detectors/{jobId:jobId}"), null, RequestParams(requestParameters));
-		///<summary>GET on /_cat/ml/anomaly_detectors/{job_id} <para>http://www.elastic.co/guide/en/elasticsearch/reference/current/ml-get-job-stats.html</para></summary>
+		///<summary>GET on /_cat/ml/anomaly_detectors/{job_id} <para>https://www.elastic.co/guide/en/elasticsearch/reference/current/ml-get-job-stats.html</para></summary>
 		///<param name = "jobId">The ID of the jobs stats to fetch</param>
 		///<param name = "requestParameters">Request specific configuration such as querystring parameters &amp; request specific connection settings.</param>
 		[MapsApi("cat.ml_jobs", "job_id")]
diff --git a/src/Elasticsearch.Net/ElasticLowLevelClient.MachineLearning.cs b/src/Elasticsearch.Net/ElasticLowLevelClient.MachineLearning.cs
index 896762937bf..7f95680eb3b 100644
--- a/src/Elasticsearch.Net/ElasticLowLevelClient.MachineLearning.cs
+++ b/src/Elasticsearch.Net/ElasticLowLevelClient.MachineLearning.cs
@@ -187,13 +187,13 @@ public TResponse DeleteTrainedModel<TResponse>(string modelId, DeleteTrainedMode
 		[MapsApi("ml.delete_trained_model", "model_id")]
 		public Task<TResponse> DeleteTrainedModelAsync<TResponse>(string modelId, DeleteTrainedModelRequestParameters requestParameters = null, CancellationToken ctx = default)
 			where TResponse : class, IElasticsearchResponse, new() => DoRequestAsync<TResponse>(DELETE, Url($"_ml/inference/{modelId:modelId}"), ctx, null, RequestParams(requestParameters));
-		///<summary>POST on /_ml/data_frame/analytics/_estimate_memory_usage <para>http://www.elastic.co/guide/en/elasticsearch/reference/current/estimate-memory-usage-dfanalytics.html</para></summary>
+		///<summary>POST on /_ml/data_frame/analytics/_estimate_memory_usage <para>https://www.elastic.co/guide/en/elasticsearch/reference/current/estimate-memory-usage-dfanalytics.html</para></summary>
 		///<param name = "body">Memory usage estimation definition</param>
 		///<param name = "requestParameters">Request specific configuration such as querystring parameters &amp; request specific connection settings.</param>
 		///<remarks>Note: Experimental within the Elasticsearch server, this functionality is experimental and may be changed or removed completely in a future release. Elastic will take a best effort approach to fix any issues, but experimental features are not subject to the support SLA of official GA features.</remarks>
 		public TResponse EstimateMemoryUsage<TResponse>(PostData body, EstimateMemoryUsageRequestParameters requestParameters = null)
 			where TResponse : class, IElasticsearchResponse, new() => DoRequest<TResponse>(POST, "_ml/data_frame/analytics/_estimate_memory_usage", body, RequestParams(requestParameters));
-		///<summary>POST on /_ml/data_frame/analytics/_estimate_memory_usage <para>http://www.elastic.co/guide/en/elasticsearch/reference/current/estimate-memory-usage-dfanalytics.html</para></summary>
+		///<summary>POST on /_ml/data_frame/analytics/_estimate_memory_usage <para>https://www.elastic.co/guide/en/elasticsearch/reference/current/estimate-memory-usage-dfanalytics.html</para></summary>
 		///<param name = "body">Memory usage estimation definition</param>
 		///<param name = "requestParameters">Request specific configuration such as querystring parameters &amp; request specific connection settings.</param>
 		///<remarks>Note: Experimental within the Elasticsearch server, this functionality is experimental and may be changed or removed completely in a future release. Elastic will take a best effort approach to fix any issues, but experimental features are not subject to the support SLA of official GA features.</remarks>
@@ -213,27 +213,27 @@ public TResponse EvaluateDataFrame<TResponse>(PostData body, EvaluateDataFrameRe
 		[MapsApi("ml.evaluate_data_frame", "body")]
 		public Task<TResponse> EvaluateDataFrameAsync<TResponse>(PostData body, EvaluateDataFrameRequestParameters requestParameters = null, CancellationToken ctx = default)
 			where TResponse : class, IElasticsearchResponse, new() => DoRequestAsync<TResponse>(POST, "_ml/data_frame/_evaluate", ctx, body, RequestParams(requestParameters));
-		///<summary>POST on /_ml/data_frame/analytics/_explain <para>http://www.elastic.co/guide/en/elasticsearch/reference/current/explain-dfanalytics.html</para></summary>
+		///<summary>POST on /_ml/data_frame/analytics/_explain <para>https://www.elastic.co/guide/en/elasticsearch/reference/current/explain-dfanalytics.html</para></summary>
 		///<param name = "body">The data frame analytics config to explain</param>
 		///<param name = "requestParameters">Request specific configuration such as querystring parameters &amp; request specific connection settings.</param>
 		///<remarks>Note: Experimental within the Elasticsearch server, this functionality is experimental and may be changed or removed completely in a future release. Elastic will take a best effort approach to fix any issues, but experimental features are not subject to the support SLA of official GA features.</remarks>
 		public TResponse ExplainDataFrameAnalytics<TResponse>(PostData body, ExplainDataFrameAnalyticsRequestParameters requestParameters = null)
 			where TResponse : class, IElasticsearchResponse, new() => DoRequest<TResponse>(POST, "_ml/data_frame/analytics/_explain", body, RequestParams(requestParameters));
-		///<summary>POST on /_ml/data_frame/analytics/_explain <para>http://www.elastic.co/guide/en/elasticsearch/reference/current/explain-dfanalytics.html</para></summary>
+		///<summary>POST on /_ml/data_frame/analytics/_explain <para>https://www.elastic.co/guide/en/elasticsearch/reference/current/explain-dfanalytics.html</para></summary>
 		///<param name = "body">The data frame analytics config to explain</param>
 		///<param name = "requestParameters">Request specific configuration such as querystring parameters &amp; request specific connection settings.</param>
 		///<remarks>Note: Experimental within the Elasticsearch server, this functionality is experimental and may be changed or removed completely in a future release. Elastic will take a best effort approach to fix any issues, but experimental features are not subject to the support SLA of official GA features.</remarks>
 		[MapsApi("ml.explain_data_frame_analytics", "body")]
 		public Task<TResponse> ExplainDataFrameAnalyticsAsync<TResponse>(PostData body, ExplainDataFrameAnalyticsRequestParameters requestParameters = null, CancellationToken ctx = default)
 			where TResponse : class, IElasticsearchResponse, new() => DoRequestAsync<TResponse>(POST, "_ml/data_frame/analytics/_explain", ctx, body, RequestParams(requestParameters));
-		///<summary>POST on /_ml/data_frame/analytics/{id}/_explain <para>http://www.elastic.co/guide/en/elasticsearch/reference/current/explain-dfanalytics.html</para></summary>
+		///<summary>POST on /_ml/data_frame/analytics/{id}/_explain <para>https://www.elastic.co/guide/en/elasticsearch/reference/current/explain-dfanalytics.html</para></summary>
 		///<param name = "id">The ID of the data frame analytics to explain</param>
 		///<param name = "body">The data frame analytics config to explain</param>
 		///<param name = "requestParameters">Request specific configuration such as querystring parameters &amp; request specific connection settings.</param>
 		///<remarks>Note: Experimental within the Elasticsearch server, this functionality is experimental and may be changed or removed completely in a future release. Elastic will take a best effort approach to fix any issues, but experimental features are not subject to the support SLA of official GA features.</remarks>
 		public TResponse ExplainDataFrameAnalytics<TResponse>(string id, PostData body, ExplainDataFrameAnalyticsRequestParameters requestParameters = null)
 			where TResponse : class, IElasticsearchResponse, new() => DoRequest<TResponse>(POST, Url($"_ml/data_frame/analytics/{id:id}/_explain"), body, RequestParams(requestParameters));
-		///<summary>POST on /_ml/data_frame/analytics/{id}/_explain <para>http://www.elastic.co/guide/en/elasticsearch/reference/current/explain-dfanalytics.html</para></summary>
+		///<summary>POST on /_ml/data_frame/analytics/{id}/_explain <para>https://www.elastic.co/guide/en/elasticsearch/reference/current/explain-dfanalytics.html</para></summary>
 		///<param name = "id">The ID of the data frame analytics to explain</param>
 		///<param name = "body">The data frame analytics config to explain</param>
 		///<param name = "requestParameters">Request specific configuration such as querystring parameters &amp; request specific connection settings.</param>