Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Full text search #226

Open
lsabi opened this issue Sep 29, 2021 · 3 comments
Open

Feature: Full text search #226

lsabi opened this issue Sep 29, 2021 · 3 comments
Labels
C-enhancement New feature or request

Comments

@lsabi
Copy link

lsabi commented Sep 29, 2021

Description
An approach I found often online, is to use a full text search engine such as apache solr for creating and querying the database content, in combination with a key value datastore, such as redis for retrieving the matching items, based on the keys returned from the search.

Adding an index, that can be full text searchable or even simple B+ trees, would be a nice feature.

There exist already some libraries for full text search written in rust, such as https://github.com/tantivy-search/tantivy

Not sure if it supports also geoindexing such as lucene.

@lsabi lsabi added the C-enhancement New feature or request label Sep 29, 2021
@ohsayan
Copy link
Member

ohsayan commented Oct 1, 2021

Hey, thanks for the suggestion! I'll be back with you on this matter a little later. @glydr remind

@glydr glydr added the S-waiting-on-maintainers This issue/PR is awaiting a response from the maintainers label Oct 1, 2021
@ohsayan
Copy link
Member

ohsayan commented Mar 2, 2022

Just to clarify, by FTS I'm going to assume that you're looking for a way to search across all values in the database (that ofc is for binary strings/unicode strings and not lists). Or if I'm getting you wrong, are you referring to searches for keys by prefixes?

@ohsayan ohsayan removed the S-waiting-on-maintainers This issue/PR is awaiting a response from the maintainers label Mar 2, 2022
@lsabi
Copy link
Author

lsabi commented Mar 2, 2022

I was assuming the first one.

Though, key prefixes/suffixes/ranges could also be an idea, in particular where composite keys are used and partial key search is needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants