2 ms·
They've long addressed all of that. There are helpful x-pack tags on the documentation for features that aren't in the OSS release. Check here for example on th
by jillesvangurp 7y ago
They've long addressed all of that. There are helpful x-pack tags on the documentation for features that aren't in the OSS release. Check here for example on the documentation page for index life cycle management: https://www.elastic.co/guide/en/elasticsearch/reference/current/index-lifecycle-management.html https://www.elastic.co/guide/en/elasticsearch/reference/curr...
The pricing model for their platinum features is indeed opaque (as in most small companies can't afford this, and you'd have to talk to a sales rep to find out). Those features are also clearly marked. X-pack features are free to use. Also, if you try to use these features without the proper license key, it won't work for obvious reasons. There's zero risk of using this accidentally without first agreeing to some license.
As for the repo, if you bother to open: https://github.com/elastic/elasticsearch/blob/master/LICENSE.txt https://github.com/elastic/elasticsearch/blob/master/LICENSE..., it spells it out in 10 lines of text. They've iterated on this a bit but this was always the place where they clearly outlined what is what.
Also, each single source file includes details on how it is licensed. There's zero chance of a developer not seeing that if they are preparing some code patch. This is intentional; it's not optional to document stuff like this if you are serious about enforcing your copyright; which of course they are.
Sysadmins pulling elasticsearch from a linux distro repo of course happens. Presumably they'd be getting an OSS build and not bundle proprietary components because they tend to care about not shipping proprietary code. If you go to the Elastic download pages, there are convenient links to both.