Crates.io | summavy |
lib.rs | summavy |
version | 0.25.3 |
source | src |
created_at | 2022-10-13 15:37:31.288193 |
updated_at | 2023-01-13 12:11:05.99079 |
description | Search engine library |
homepage | https://github.com/izihawa/tantivy |
repository | https://github.com/izihawa/tantivy |
max_upload_size | |
id | 687258 |
size | 26,363,149 |
Tantivy is a full-text search engine library written in Rust.
It is closer to Apache Lucene than to Elasticsearch or Apache Solr in the sense it is not an off-the-shelf search engine server, but rather a crate that can be used to build such a search engine.
Tantivy is, in fact, strongly inspired by Lucene's design.
If you are looking for an alternative to Elasticsearch or Apache Solr, check out Quickwit, our search engine built on top of Tantivy.
The following benchmark breakdowns performance for different types of queries/collections.
Your mileage WILL vary depending on the nature of queries and their load.
(michael AND jackson) OR "king of pop"
)"michael jackson"
)&[u8]
fast fieldsDistributed search is out of the scope of Tantivy, but if you are looking for this feature, check out Quickwit.
Tantivy works on stable Rust and supports Linux, macOS, and Windows.
tantivy-cli
is an actual command-line interface that makes it easy for you to create a search engine,
index documents, and search via the CLI or a small server with a REST API.
It walks you through getting a Wikipedia search engine up and running in a few minutes.There are many ways to support this project.
We use the GitHub Pull Request workflow: reference a GitHub ticket and/or include a comprehensive commit message when opening a PR.
When implementing a tokenizer for tantivy depend on the tantivy-tokenizer-api
crate.
Tantivy currently requires at least Rust 1.62 or later to compile.
Tantivy compiles on stable Rust. To check out and run tests, you can simply run:
git clone https://github.com/quickwit-oss/tantivy.git
cd tantivy
cargo build
Some tests will not run with just cargo test
because of fail-rs
.
To run the tests exhaustively, run ./run-tests.sh
.
You might find it useful to step through the programme with a debugger.
Make sure you haven't run cargo clean
after the most recent cargo test
or cargo build
to guarantee that the target/
directory exists. Use this bash script to find the name of the most recent debug build of Tantivy and run it under rust-gdb
:
find target/debug/ -maxdepth 1 -executable -type f -name "tantivy*" -printf '%TY-%Tm-%Td %TT %p\n' | sort -r | cut -d " " -f 3 | xargs -I RECENT_DBG_TANTIVY rust-gdb RECENT_DBG_TANTIVY
Now that you are in rust-gdb
, you can set breakpoints on lines and methods that match your source code and run the debug executable with flags that you normally pass to cargo test
like this:
$gdb run --test-threads 1 --test $NAME_OF_TEST
By default, rustc
compiles everything in the examples/
directory in debug mode. This makes it easy for you to make examples to reproduce bugs:
rust-gdb target/debug/examples/$EXAMPLE_NAME
$ gdb run
You can also find other bindings on GitHub but they may be less maintained.
commit
is called on an IndexWriter
. Existing IndexReader
s will also need to be reloaded in order to reflect the changes. Finally, changes are only visible to newly acquired Searcher
.