-
Notifications
You must be signed in to change notification settings - Fork 139
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: typo tolerance #2144
feature: typo tolerance #2144
Conversation
e7cb908
to
c07b9c5
Compare
b80abcf
to
9df46e5
Compare
1f6e97d
to
48d3ce7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we change id-worker to a better name and include cronjob
instead of worker
b30ee62
to
f182eac
Compare
Pending problems -
|
bf40e24
to
1470220
Compare
2816711
to
1814ad8
Compare
e99c37d
to
ec2a434
Compare
a9c2721
to
3d0763b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Recursive data structure is too deep, getting "bk tree depth limit exceeded" serde errror when trying to load into the server. Will need to store the tree as a different structure. First thing that comes to mind is an adjacency list.
b3d4926
to
52d97ed
Compare
870bd4f
to
fcc95cc
Compare
fcc95cc
to
7d09c52
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can it return the corrected query on the response?
47acc28
to
57303ca
Compare
57303ca
to
41eec72
Compare
When spinning up services the amount of word_workers > bktree_workers. If dealing with big datasets spin up word_workers to 15+ to accommodate load CH can take the abuse