This repository was archived by the owner on Nov 7, 2025. It is now read-only.
Fuzzy search support #1509
Merged
Fuzzy search support #1509
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Using damerauLevenshteinDistance clickhouse function as it's the closest alternative to elasticsearch '~' operator. Signed-off-by: Radim Hrazdil <[email protected]>
Signed-off-by: Radim Hrazdil <[email protected]>
rhrazdil
requested review from
avelanarius,
jakozaur,
nablaone,
stared and
trzysiek
|
|
Member
|
/run-it |
|
Member
|
Code LGTM, also tested it a bit manually. Thanks for the contribution! |
Member
|
/run-it |
mieciu
approved these changes
Aug 11, 2025
Member
mieciu
left a comment
mieciu
left a comment
There was a problem hiding this comment.
Nice, thank you so much for your contribution!
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[Why]
We're in a process of migrating data from elasticsearch to clickhouse. We have a alerting service reading the data from elasticsearch (https://github.com/jertel/elastalert2), with no clear substitution offering feature partiy for Clickhouse. This is where quesma seems like a perfect fit.
One of our alerts relies on fuzzy search (
~), so I decided to give it a try implementing.I'd be happy for any feedback.
PR introduces implementation of elasticsearch fuzzy search for clickhouse database.
I decided to use
damerauLevenshteinDistanceclickhouse function, as its functionality is the closest to elasticsearch~operator, based on my direct comparison.I did basic E2E test of the implemented functionality in my local setup with clickhouse-server 24.5.