-
Notifications
You must be signed in to change notification settings - Fork 30
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
Is there Infix search possible #4
Comments
With the current PruningRadixTrie structure there is no infix search possible, unless you want to exhaustively scan the whole trie. It would be possible to modify the structure and the algorithm though: When adding a term to the trie you could also add all the suffixes of the term to the trie. But this would significantly increase memory consumption and lookup time. |
Ok, arent you already indexing all single characters? Sorry if I am totally wrong but werent Tries invented to search anywhere ? You can look here, maybe its somehow important especially the Suffix Trie |
No, Radix tries (prefix tries) are supporting efficient prefix search, and Suffix tries are supporting efficient suffix search, None of them is supporting efficient substring (neither prefix nor suffix) search. |
Ok thanks, so something similar to the link I've added is not possible anywhere soon ? |
I have currently no plans to implement it. But anybody is free to fork the repository and add a substring lookup functionality. |
Is there a chance also to look for croso to get results for microsoft?
So not only Prefix search.
The text was updated successfully, but these errors were encountered: