<p dir="auto">Currently, when invoking <code class="notranslate">GET indexname/_mapping</code> one gets a long list of the fields that can be expected in the index. All these have the form:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="&quot;feed&quot;: {
            &quot;type&quot;: &quot;string&quot;,
            &quot;index&quot;: &quot;not_analyzed&quot;
}"><pre class="notranslate"><code class="notranslate">"feed": {
            "type": "string",
            "index": "not_analyzed"
}
</code></pre></div>
<p dir="auto">For an end user, who normally cannot see the configuration, the name of the field and its properties might not be enough to understand what the field actually holds. Therefore, it would be very helpful to allow a comment field inside the object above. Here is an example:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="&quot;feed&quot;: {
            &quot;type&quot;: &quot;string&quot;,
            &quot;index&quot;: &quot;not_analyzed&quot;
            &quot;comment&quot;: &quot;feed holds the name of the feed as provided by the client side&quot;
}"><pre class="notranslate"><code class="notranslate">"feed": {
            "type": "string",
            "index": "not_analyzed"
            "comment": "feed holds the name of the feed as provided by the client side"
}
</code></pre></div>
<p dir="auto">Transaction logs are being persisted wrongly to the shared gateway storage, causing the full translog to be persisted each time (and not the delta), causing both wrong data stored in the gateway, and possible duplicates created when recovering.</p>