Support for WilcardQuery and PrefixFilter #565
Closed
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
Contributor
|
Going to close this since it is no longer mergable and there are no UI provisions for its usage |
|
@rashidkpc how one can make prefix search in kibana? How query would look like? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
I was unable to use a lucene query string to make a start_with query on a not_analyzed HTTP request string field like
request:/service/action*successfully.Maybe I missed something in the syntax or in the documentation.
But I found that I could use the ES wildcard query and prefix filter.
This PR add the requires ejs code to use them.
For using them, I edited the configuration in the dashboard json,
sorry I don't have time to make editor panels