I agree the java option is really crude way to switch the feature off. But I want to take a step back: the sub-request scanning feature originated when I was trying to make the
index_rewrite rule work: we needed sub-request granularity to change every index field in every sub-request.
Of course, that turned out being a total failure due to the wide and ever changing set of ActionRequest types within ES, but also - clearly - for performance.
As of today,
index_rewrite rule has been removed from documentation, but sub-request checking is still on by default. And I would be in fact very keen to disable this feature.
Some background about sub-request checking
The subrequest checking is trying to address the scenario when you have a bulk request that contains a set or requests that apply to different indices.
Without the subrequest checking, the indices rule evaluates the bulk request as a whole. So the global set of indices is evaluated and if one is prohibited, the whole request is dropped.
With subrequest checking If the bulk request contains 10 subrequests, one of which is trying to index/update/delete the wrong index, only that subrequest is discarded and the other nine will remain. Now the bulk request can be allowed by ROR.
Anybody against disabling this by default?
- DISABLED BY DEFAULT
- LEAVE IT ON BY DEFAULT
- DELETE FEATURE