3 ms·

I think it’s the fact that the implementation details don’t change the optics; AWS had the resources and talent to both monetize AND be a Good Samaritan by cont

I think it’s the fact that the implementation details don’t change the optics; AWS had the resources and talent to both monetize AND be a Good Samaritan by contributing to the upstream. The contributions could have been RFCs, GitHub issues, etc. With that said, I can imagine the rumored culture of AWS engineering doesn’t support wondering souls that typically nurture thoughts of community service for the upstream.

_msw_ 5y ago
Disclosure: I work for AWS. There were contributions sent upstream for Elasticsearch bugfixes and enhancements. Some of those PRs are still open, for example [1]. A sampling of additional PRs can be found in this blog post [2]. Further contributions upstream to Apache Lucene have been growing over the years. The new Approximate Nearest Neighbor support in Elasticsearch 8.0 comes from work that was sponsored by Amazon in upstream Apache Lucene [3]. [1] https://github.com/elastic/elasticsearch/pull/64513 https://github.com/elastic/elasticsearch/pull/64513 [2] https://aws.amazon.com/blogs/opensource/stepping-up-for-a-truly-open-source-elasticsearch/ https://aws.amazon.com/blogs/opensource/stepping-up-for-a-tr... [3] https://issues.apache.org/jira/browse/LUCENE-9004 https://issues.apache.org/jira/browse/LUCENE-9004