Feature/indexupdates #24
Open
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
# Conflicts: # Moriyama.AzureSearch.Umbraco.Application/AzureSearchClient.cs
…s compatibility with examine version
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.
Various updates for azure indexes
Add event for CreatingIndex to allow custom modification to the index
Sorted umbraco fields alphabetically, keeping key/id at the top
Add search term highlighting to assist with identifying why an item was matched
Add searchablepath to allow searching for path.startswith etc
Add search.in and filter support - see search.in
Add support for full query syntax - see Lucene syntax
Add support for custom search params
Add support for lucene query syntax, and an examine searcher to 'proxy' examine searches through to azure search