As someone who maintains an Elasticsearch plugin, you often have to do A LOT of research into how Elastic themselves have dealt with their undocumented, constantly evolving APIs to figure out how to adapt your own code. Stuff like this happens all the time where some boilerplate code changes, you copy in the way Elastic themselves did it. Given how the code is now a mix of Elastic and Apache code, now you can create a host of legal liability by accidentally taking the wrong piece of boilerplate.
Potential legal liability on top the headaches of maintaining an open source project in my spare time with almost no support. Oh joy.
This has happened with my comments on other posts, it's content is that instead of using license encumbered ELK product people can use SOLR, Vespa or Lucene which are truly open source. It was down voted enough to move it to last or grey it out to make it difficult to read.
> Loki is meant to be complementary to existing solutions like Elasticsearch and Splunk that do full text indexing.
https://github.com/floragunncom/search-guard-enterprise-modu...
In particular, the change to getLiveDocs(): https://github.com/floragunncom/search-guard-enterprise-modu...
and numDocs(): https://github.com/floragunncom/search-guard-enterprise-modu...
EDIT:
At least in the case of numDocs(), both Elastic and Search Guard's implementations seem to be based on this bit of Apache-licensed code from Lucene (or perhaps this is just a common pattern for counting live documents?):
https://github.com/apache/lucene-solr/blob/branch_6_3/lucene...