2 ms·
By fork they mean: a binary build straight from the unmodified elastic source code using the elastic build file that creates the OSS build bundled with a handfu
by jillesvangurp 6y ago
By fork they mean: a binary build straight from the unmodified elastic source code using the elastic build file that creates the OSS build bundled with a handful of plugins and components to add alternatives some of the things elastic bundles. They don't even build it themselves and it gets downloaded in binary form straight from Elastic's servers.
If you don't believe me, this is the line in the code where they 'fork' in their build script: https://github.com/opendistro-for-elasticsearch/opendistro-build/blob/master/elasticsearch/linux_distributions/opendistro-tar-build.sh#L51 https://github.com/opendistro-for-elasticsearch/opendistro-b...
It will be interesting to see if opendistro actually starts contributing to Lucene or adding value to the elastic code base or whether this 'fork' is effectively frozen in time and doomed to go nowhere due to a lack of actual development on the core product.
I seriously doubt that they are going to put any effort whatsoever in that. Because in two years of pretending they have a fork, there has been no serious code contributions from their side at all that I'm aware off. Correct me if I'm wrong.
If you want to back an OSS version of related technology, maybe use something like Apache Solr, which continues to provide many of the same features and is part of the same ecosystem of users and developers that work on Lucene, which also powers Elasticsearch and which of course continues to contribute a lot to Lucene; unlike Amazon.
- _msw_ 6y agoDisclosure: I work for Amazon, but not directly on search related technology. Some information about Amazon's investments in upstream Apache Lucene can be found here: https://aws.amazon.com/blogs/opensource/amazon-giving-back-apache-lucene/ https://aws.amazon.com/blogs/opensource/amazon-giving-back-a... Covered in the 2019 blog post are: * Concurrent updates and deletes * Indexing custom term frequencies * Lazy loading of Finite State Transducers