Hacker News Reader

Comment by craigching | Hacker News Reader

I'm wondering how this affects the distribution of x-pack. From what I'm reading, the new Free model probably includes it and we have to turn it off if we don't want it? I wish there was still an x-pack free distribution in this model.

View on HN

Since the entire Elasticsearch codebase is now under SSPL, there's no more distinction between the former Apache-2 code and the x-pack code.

There are still proprietary modules only available under the Elastic License just as before.

However it seems that they will be moving the free modules which were previously only licensed under Elastic License to be licensed under SSPL instead.

At least, that is what this graph seems to be indicating to me. https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce...

You're right -- it's only the free "X-pack Basic" code that will now be available under SSPL. But that does mean that all Elasticsearch distributions will now include the former "X-pack Basic" features.

That seems to be what they are suggesting by making the "free" box in the 3rd column span both the "free" and "free/basic" tiers of the previous columns.

Unless they plan to make those modules paid which were previously free, which I doubt

Yes, I understand that, but what I would like is a distribution without any x-pack code. I don't want to have to figure out how to turn off and remove x-pack. What I'm concerned about is that it's another vector for security vulnerabilities that I don't need.

Reply on news.ycombinator.com