News for hackers. Stuff that matters.
Re:Amazon: Not OK – Why we had to change Elastic licensing by michaelcampbell on Tuesday January 19, 2021 @06:41PM (#25840532)
It wasn't a comparison, it was a statement of fact, which I think is true, no? ES was based on OS from Lucene, or it was not.

You're asserting a comparison where none was made.

Re:Amazon: Not OK – Why we had to change Elastic licensing by cmiles74 on Tuesday January 19, 2021 @06:51PM (#25840629)
In my opinion, the phrase "based on" implies that a lot of the Elasticsearch functionality is actually Lucene functionality. I disagree that this is the case, I think there is a lot of functionality that Elasticsearch brings that is really othogonal to the Lucene project (sharding, multi-tenancy of indexes, clustering, managing nodes, etc.) Again, you my opinion, definitely enough for it's own project.

If that isn't what you meant then perhaps we are in agreement. :-)

Re:Amazon: Not OK – Why we had to change Elastic licensing by cortesoft on Tuesday January 19, 2021 @08:54PM (#25841647)
Honestly, I was just quoting the opening line of the Wikipedia page.

I wasn't trying to imply anything about where most of the functionality was coming from.

Re:Amazon: Not OK – Why we had to change Elastic licensing by cmiles74 on Friday January 22, 2021 @10:04PM (#25879191)
Since you have mentioned this I have read three more articles and short blurbs about this kerfuffle and _they all_ have used the same "based on Lucene" text when describing Elasticsearch. As you say, Wikipedia seems to be the one true source of this phrasing!

https://en.m.wikipedia.org/wiki/Elasticsearch

While I still think this phrasing is unfair, it certainly seems to be the consensus. At least when measured by Google search results.

https://www.google.com/search?q=%22Elasticsearch%20is%20a%20...