Zum Inhalt der Seite gehen
Elasticsearch looks like bullshit to me. You think you need it, because "it's fast", but you don't. Just stick to a new PostgreSQL and properly use it's full text search functionality.

Pros:
- no need to index things manually
- no inconsistencies
- sane query language, instead of JSON dumbfuckery (you use JSON as a query language and then complain about lisp's parethesis)
feld
if you can do it without hitting the limitations of the Postgres FTS, you're winning. I agree to avoid solutions like Elastic until you REALLY need it. And then if you do try something else like Zincsearch (Elastic clone in Go) or Meilisearch
Doug Webb
hey! I'm only just getting into search, in context of #mediawiki

Their default search is database (mariadb) and all extensions on top are elastic.

Have there been recent improvements with db search in recent times, or is it limited to postgres?

@pintoch
#mediawiki @Antonin Delpeuch
Derk-Jan 💙💛🇺🇦
I’ve actually been looking at mediawiki’s sql search as well. It’s heavily outdated and underdeveloped. Most code is still from 2003 and ever since 2004/2005 it has been lucene and later elastic in separate extensions.
It really could use some rework.
Doug Webb
would be very happy to user test! Actually developing search stuff seems a bit scary to me.
⇧