4 ms·
>MeiliSearch (but their API triggered a panic response) Could you expand on that with examples? I only played around with it lightly but it seemed ok via the P
by sidmitra 4y ago
>MeiliSearch (but their API triggered a panic response)
Could you expand on that with examples? I only played around with it lightly but it seemed ok via the Python SDK.
I've been recently leaning towards Meilisearch for some client facing search features. This was over Typesense because, i believe Typesense is totally in-memory, but in some cases my dataset might not fit in RAM(atleast not at a reasonable cost). I was fine with taking a performance hit for disk access, provided i could have thousands of separate indexes with separate permissions etc. and directly call them from the browser app.
- remram 4y agoAdmittedly it's been almost a year since I tried it, but: * If you have more than 65,535 words in a document, words after that limit will be SILENTLY IGNORED (not indexed). This was 1,000 words when I tried it, which was very limiting * Documents where your query word happens sooner are ranked above documents where your query words happen later (in the document string). You can't turn that off * You can't get the "match" information (i.e. the position where your query matched in the document) unless you retrieve that attribute (i.e. tell the database to send you the entire document content) * The API uses HTTP verbs wrong, e.g. POST is used to "Add or replace documents" and PUT is used to update documents (it's exactly backwards from the intended use, per RFC 7231)