Reindexing data is not as straightforward as it could be. You are required to set up the settings and mapping in advance of a reindex call even if all you're doing is reindexing data in an existing index with no changes (e.g. in preparation for a major version upgrade). While it may seem like all that's required is to GET the existing index settings/mapping and copy/paste into a new index, this

What happens

When creating snapshot, meilisearch opens a temp dir which may be on a different disk than snapshot_path and even if enough disk space is available for the snapshot path, it fails with No space left on device.

Expected behaviour

Should create temp dir inside snapshot_path.

https://github.com/meilisearch/MeiliSearch/blob/f83caa6c40a01c931ee4ccde4fb1113067fda488/meilis

Currently when clicking an image from search resutls the pop-up includes the image at a fixed size.
I propose to either increase that scaling to a somewhat higher fixed value or factor in the original image size so that very small pictures do not become pixelated.

Currently the preview is too small in my opinion which forces me to visit the website.

The DocStore builds blocks of contiguous document serialized in an adhoc simple binary format.
These blocks are then compressed.

The format goes:

• field: u32
• type tag: u8
• value: specific to the type but for instance u64 simply take 8 byts.

@ppodolsky noticed that despite the compression, it might be possible to shave off a few percent of storage by changing the encoding. This might

Feeding documents with large tensor fields (e.g tensor(p{},dt{},x[128})) using JSON or XML(deprecated) serialization is cumbersome as string representation of float/double is costing a lot of network bandwidth, storage and processing (serialize, deserialize).

What happened

Accidentally omitting document content returns 500 Internal Server Error with a body of {"message":"Internal error","uri":"/new_index"}

What was expected

Emitting any kind of helpful message would be helpful. Also, in my experience, when the client receives a 500 response, there is usually something informative on the server-side. But in this case, the server e

People are interested in a size-comparison between

• tinysearch
• lunr.js
• elasticlunr
• flexsearch
• fuse.js

If anyone wants to do a comparison, post a comment here.
Some ideas:

• Use an open dataset, e.g. Shakespeare texts https://shakespeare.folger.edu/download/
• Create a size histogram of the results that we can include into the README.
• Add the code to the repository under a `b

Is your feature request related to a problem? Please describe.
If you work on domain corpora, collecting additional training data to improve your reader or retriever models is very helpful.
For collecting training data, there are two main options:
a) Manual Labelling
b) User feedback for "live predictions"

b) is particularly promising if you don't have enough time or resources for a)