Search Engine Parser
whoosh
Our great sponsors
| Search Engine Parser | whoosh | |
|---|---|---|
| - | 5 | |
| 429 | 524 | |
| 0.0% | - | |
| 0.0 | 0.0 | |
| over 1 year ago | 4 months ago | |
| Python | Python | |
| MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Search Engine Parser
We haven't tracked posts mentioning Search Engine Parser yet.
Tracking mentions began in Dec 2020.
whoosh
-
Milli-py: Python bindings for Milli, an embeddable high-performance search engine
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.
-
Meilisearch v1.0 – the open-source Rust alternative to Algolia and Elasticsearch
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?
-
Faster Full Text Search
For our full text search, we used whoosh, which works pretty well for moderately big amount of data.
-
We upgraded an old, 3PB large, Elasticsearch cluster without downtime
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.
-
Starting a KF Discord Bot
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.
What are some alternatives?
Elasticsearch - Free and Open, Distributed, RESTful Search Engine
Whoosh
pysolr - Pysolr — Python Solr client
django-haystack - Modular search for Django
elasticsearch-dsl-py - High level Python client for Elasticsearch
solrpy - Automatically exported from code.google.com/p/solrpy
query-builder - sql query builder library for crystal-lang
esengine - ElasticSearch ODM (Object Document Mapper) for Python - pip install esengine
query.cr - Query abstraction for Crystal Language. Used by active_record.cr library.
lunr.js - A bit like Solr, but much smaller and not as bright