<p dir="auto">These settings parallel each other and are also confusing with <code class="notranslate">transport.type</code>. This causes problems in tests sometimes since we randomize the first two settings. So if a test wants to rely on, eg always using netty, it has to remember to set <em>two</em> settings, to make sure randomization doesn't mess this up. And if the test forgets one, it can have weird consequences, like the wrong transport address instance being created, causing class cast exceptions like in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="100193487" data-permission-text="Title is private" data-url="https://github.com/elastic/elasticsearch/issues/12788" data-hovercard-type="issue" data-hovercard-url="/elastic/elasticsearch/issues/12788/hovercard" href="https://github.com/elastic/elasticsearch/issues/12788">#12788</a>.</p>
<p dir="auto">I think we should minimize these to as single setting (preferably <code class="notranslate">transport.type</code> since that is the pluggable setting).</p>
<p dir="auto">The notes in the code say that the script parsing will go in 2.0 but its still there. I mean <code class="notranslate">SCRIPT_LANG</code>, <code class="notranslate">SCRIPT_FILE</code>, <code class="notranslate">SCRIPT_ID</code>, and <code class="notranslate">SCRIPT_INLINE</code>.</p>