Re:An alternative to Elasticsearch that runs on a few MBs of...
by markandrewj on Monday October 24, 2022 @10:42AM
(#33317314)
Although not exactly the same, Elastic has an SQL query syntax which can be used now as well.
Re:An alternative to Elasticsearch that runs on a few MBs of...
by _boffin_ on Monday October 24, 2022 @07:41PM
(#33324147)
They’ve had it for a long time already. Was using it over a year and a half ago. Not really “new”
Re:An alternative to Elasticsearch that runs on a few MBs of...
by neodymiumphish on Tuesday October 25, 2022 @08:18AM
(#33329497)
In fairness, the comment you're replying to didn't say it was new.
Re:An alternative to Elasticsearch that runs on a few MBs of...
by tensor on Monday October 24, 2022 @10:01AM
(#33316731)
It's probably fairly easy to write an adapter here.
Re:An alternative to Elasticsearch that runs on a few MBs of...
by xvello on Monday October 24, 2022 @12:47PM
(#33319080)
Since Elastic spitefully patched all of their client libraries to fail if the server is not a "genuine" ES server, I don't see what good a drop-in replacement with protocol compatibility would do.
Go client: https://github.com/elastic/go-elasticsearch/blob/3985f2a1554...
Python client: https://github.com/elastic/elasticsearch-py/commit/e72aa3e24...
Re:An alternative to Elasticsearch that runs on a few MBs of...
by snikolaev on Monday October 24, 2022 @12:56PM
(#33319213)
Is it prohibited to include `X-Elastic-Product: Elasticsearch` in the output of your server if the user instructs the server to do so? :)
Re:An alternative to Elasticsearch that runs on a few MBs of...
by hangonhn on Monday October 24, 2022 @02:49PM
(#33320729)
I don't see how they can legally have any control over what a 3rd party's software outputs. And more importantly, how would they even enforce such restrictions?
Re:An alternative to Elasticsearch that runs on a few MBs of...
by blowski on Monday October 24, 2022 @03:04PM
(#33320929)
I imagine AWS can't put it on the headers of their managed service, and that's what it's about.
Re:An alternative to Elasticsearch that runs on a few MBs of...
by sickmate on Monday October 24, 2022 @09:19PM
(#33324972)
AWS has a compatibility mode that allows your cluster to report its version as 7.10.
Re:An alternative to Elasticsearch that runs on a few MBs of...
by yvan on Monday October 24, 2022 @02:59PM
(#33320843)
I believe Elasticsearch is a trademark.
Re:An alternative to Elasticsearch that runs on a few MBs of...
by mumblemumble on Monday October 24, 2022 @03:20PM
(#33321175)
If it really does work this way, then we're all doomed.
https://stackoverflow.com/questions/1114254/why-do-all-brows...
Re:An alternative to Elasticsearch that runs on a few MBs of...
by blowski on Tuesday October 25, 2022 @04:18AM
(#33327672)
If its use is so widespread, then it's probably no longer a trademark, in that context at least.
Re:An alternative to Elasticsearch that runs on a few MBs of...
by jeltz on Monday October 24, 2022 @03:33PM
(#33321378)
A trademark does not forbid people from using a name, it only restricts how it can be used in marketing. I do not see how that would be applicable here.
Re:An alternative to Elasticsearch that runs on a few MBs of...
by metadat on Monday October 24, 2022 @03:03PM
(#33320908)
Are HTTP headers important or even relevant at all for branding trademark purposes?
Such a concern seems utterly ridiculous.
Re:An alternative to Elasticsearch that runs on a few MBs of...
by collegeburner on Monday October 24, 2022 @07:10PM
(#33323855)
same thing nintendo did on old consoles: the "DRM" was requiring the cartridge to display a nintendo logo at start-up. so if you included that, you could get sued.
my guess is because it's "X-Elastic-Product" you'd be falsely "saying" your product is made by Elastic, the company so they could sue over it.
Re:An alternative to Elasticsearch that runs on a few MBs of...
by AbraKdabra on Monday October 24, 2022 @03:30PM
(#33321324)
Those libraries are open source, just nuke those restrictions and you're good to go. Is it the best way? Maybe not, but it's better than modifying your server responses (and in the worst 1984 case, allowing Elastic to sue you), if you develop such a tool you can always put that distinction in your README.
Even if it offers only a fraction of the features offered by ES, that may be fair enough for at least half of the use-cases out there.
Sonic could have really had a strong selling point: "Use an ES-alternative that works fine in most of the real-world applications, but it's written in Rust and it only takes a fraction of the memory footprint required by ES, and it shouldn't require you to change your application code".
Instead, they are proposing yet another search protocol, that developers have to learn and adopt. That definitely increases the adoption barriers.