Going forward the repository will have a dual-license and the top image on https://www.elastic.co/pricing/faq/licensing can hopefully explain that better.
[Disclaimer: I work for Elastic]
Sure, at some point someone started to create a plugin for ES (let's say the security/ACL thing in x-pack, used to be called Shield or something like that), they used the ES API and they used runtime linking. (I have no idea if that's okay or not, has been tested in court or not. I know the US Supreme Court will say something about that in June.) But when developing any feature in that plugin nobody thinks of just that plugin. Folks think about ES as a whole, indexes, shards, documents, terms, maybe even in terms of low-level Lucene primitives.
I think it's practically impossible to wear the OSS and the proprietary hat at the same time. (Or separately but on the same project.)
But if you have a copy of the license and the code and it permitted use of it perpetually, then it can continue to be used. That's my understanding.
I would love to but the terms within the ElasticSearch codebase on Github are quite confusing. Here's the text of the LICENCE.TXT file.
Aside from not showing copies of the applicable licenses, it seems you have to read the code headers to determine which source file has which license. There are a lot of ways to respond to competitive threats from Amazon, but this approach is increasingly chaotic the closer you look.[1] https://github.com/elastic/elasticsearch/blob/master/LICENSE...