Go to file
Clément Renault 2fa5808e3f
Merge pull request #71 from meilisearch/cleanup-useless-build-rs
Cleanup useless custom build file
2021-01-15 15:45:47 +01:00
.github/workflows Avoid compiling benchmarks and speedup the CI 2020-11-11 11:14:57 +01:00
benches Fix the benchmarks 2020-10-31 22:18:29 +01:00
http-ui Fix an fst Set related warning 2021-01-13 11:03:03 +01:00
src highlight with new tokenizer 2021-01-11 21:59:37 +01:00
.gitignore Move the http server into its own sub-module 2020-11-05 11:16:39 +01:00
Cargo.lock highlight with new tokenizer 2021-01-11 21:59:37 +01:00
Cargo.toml integrate with meilisearch tokenizer 2021-01-07 16:14:27 +01:00
LICENSE Initial commit 2020-05-31 14:21:56 +02:00
qc_loop.sh Initial commit 2020-05-31 14:22:06 +02:00
README.md Fix the milli logo in the README 2020-11-05 11:43:47 +01:00

the milli logo

a concurrent indexer combined with fast and relevant search algorithms

Introduction

This engine is a prototype, do not use it in production. This is one of the most advanced search engine I have worked on. It currently only supports the proximity criterion.

Compile and Run the server

You can specify the number of threads to use to index documents and many other settings too.

cd http-ui
cargo run --release -- serve --db my-database.mdb -vvv --indexing-jobs 8

Index your documents

It can index a massive amount of documents in not much time, I already achieved to index:

  • 115m songs (song and artist name) in ~1h and take 107GB on disk.
  • 12m cities (name, timezone and country ID) in 15min and take 10GB on disk.

All of that on a 39$/month machine with 4cores.

You can feed the engine with your CSV (comma-seperated, yes) data like this:

cat "name,age\nhello,32\nkiki,24\n" | http POST 127.0.0.1:9700/documents content-type:text/csv

Here ids will be automatically generated as UUID v4 if they doesn't exist in some or every documents.

Note that it also support JSON and JSON streaming, you can send them to the engine by using the content-type:application/json and content-type:application/x-ndjson headers respectively.

Querying the engine via the website

You can query the engine by going to the HTML page itself.