<h3 dir="auto">Description</h3>
<p dir="auto">Modify the batch indexing task ID generation logic from</p>
<p dir="auto"><code class="notranslate">&lt;index_type_name&gt;_&lt;datasource&gt;_timestamp</code> to<br>
<code class="notranslate">&lt;index_type_name&gt;_&lt;datasource&gt;_&lt;random_id&gt;</code><br>
This would impact native index tasks as well as hadoop index tasks.</p>
<h3 dir="auto">Motivation</h3>
<p dir="auto">With the existing task naming convention, if there are multiple indexing tasks submitted at the same time for a datasource, only one of the tasks gets accepted and the remaining tasks fail with  <code class="notranslate">Task[xxx] already exists</code>. I'd like to modify the naming convention to the one mentioned above, so that this issue can be avoided.<br>
<a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/users/jihoonson/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/jihoonson">@jihoonson</a> Any comments regarding this?</p>
<p dir="auto">HadoopDruidIndexer should load up the runtime.properties like all of the other processes and be able to fill stuff into the configuration based on the values it finds (stuff like the pusher).  This would help consolidate the various different ways of specifying configuration.</p>