-
Notifications
You must be signed in to change notification settings - Fork 9
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
39 wildcard searching #41
Merged
Merged
Conversation
This file contains 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
I'm rebasing this onto a new v3 branch due to the breaking changes. I want to see if the breaking changes are enough to support some form of Levenshtein distance fuzzy matching before completing the version release. |
Note to self: I think some performance work is going to be needed for wildcard searches that return lots of results, especially when multiple wildcard are included in the query |
mikegoatly
added a commit
that referenced
this pull request
Feb 6, 2022
* Added methods on index navigator to support backtracking and peeking next characters * Added multi character wildcard matching * Wildcard query parsing * Bumped major version due to breaking changes * Added Search overload to index
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Implementation of wildcard searching #39
This introduces some breaking changes:
IFullTextIndex
Search(IQuery)
overload onIFullTextIndex
IIndexNavigator
CreateBookmark
that allows the current state of the navigator to be captured and subsequently reapplied usingIIndexNavigatorBookmark.Apply
EnumerateIndexedTokens
will throw an exception if a bookmark has been applied during the usage of the navigator.EnumerateNextCharacters
that enumerates any characters that can be navigated to from the navigators current positionITokenizer
Normalize(ReadOnlySpan<char>)
- normalizes the given text according to any input preprocessors, but doesn't apply any additional tokenization rules, e.g. stemming.%
characters - these are considered part of a wildcard search.Removals
IWordQueryPart
- any types implement it only need implementIQueryPart
StartsWithWordQueryPart
- redundant now thatWildcardQueryPart
exists