whoosh VS elasticsearch-dsl-py

The only other embeddable search engine I'm aware off, Whoosh, is brilliant but building the index was quite slow, and search performance degraded quite a lot as number of documents increase (performance is strictly a non-goal). Meilisearch was comparatively faster, I didn't like managing a server to get "just search" in my scripts and applications. However, their underlying engine Milli solves both issues I had, and all that was needed creating bindings for it.

Is it really "just a single statically linked binary"?

I'd love to use Meilisearch as you describe, but their so-called SDKs are just about for the search client, you still need the HTTP server listening on localhost.

I would love to see something like SQLite based off Meilisearch (i.e. a fully selfcontained library like https://github.com/mchaput/whoosh). Do you know if such a thing exists?

For our full text search, we used whoosh, which works pretty well for moderately big amount of data.

Nearly a decade ago (oh god) I converted some overdesigned five node ES mess to https://github.com/mchaput/whoosh. It's (obviously) not the fastest or anything, but it was more than good enough for low-dozens of GBs of mostly static data.

Your best bet is to start using a proper search library rather than the simple loop with 'in' checks that you have now. A search lib will handle things like Unicode/ASCII similarities, removal of stop words, stemming, TF-IDF (and other) weighting, etc. and will be massively faster as well. Quite a few pages come up if you Google "python search engine", also Whoosh looks promising.

requests - A simple, yet elegant, HTTP library. sanic - Next generation Python web server/framework | Build fast. Run fast. click - Python composable command line interface toolkit elasticsearch-dsl-py - High level Python client for Elasticsearch panel - A high-level app and dashboarding solution for Python internetarchive - A Python and Command-Line Interface to Archive.org coconut - Simple, elegant, Pythonic functional programming

I'm not being cryptic. I'm struggling to see how I can be any clearer. You only need to import things you actually use in your code. The only names from Elasticsearch that you use in your code are Search and MultiSearch, and even those are commented out. You don't need to import things that are only used by other imports. Otherwise where would it stop? Obviously the code that defines Match and MultiMatch themselves references other internal Elasticsearch things, and other libraries that are irrelevant to your code - you can see what it imports here. You don't need to import any of those, and for the same reason you don't need to import Match just because it might be referenced by the query method.