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 request] Wildcard search on not_analyzed fields for Elasticsearch datasource #7451
Comments
I have a patch ready, if you are interested. |
I can see this option was removed on Elasticsearch 5.x, do you know what is the behavior in it? |
No, I did not have the time to test the behaviour with Elasticsearch 5.x. We currently still use 2.3, but I will try to make a quick test within the next days. |
I´s only a deprecation: I tried to write a feature to configure the query_term options ... take a look : regards |
Hi Guys, Any updates on this? |
Maybe someone could review my pull request? (If this is the reason not to merge) regards |
since this option was removed in Elastic 5.x closing this seems appropriate |
Grafana version: 4.1.1
Datasource: Elasticsearch - Native Plugin v. 3.0.0
OS: linux
Problem
With the current Elasticseach datasource plugin it is not possible to use wildcards in the Lucene query for
not_analyzed
fields. This concerns at least Elasticsearch version 2.3.The reason is that the current
query_string
created by the plugin is not specifyinglowercase_expanded_terms: false
Lucene query example
Resolution
The problem can easily be fixed by adding to query_buider.js the missing
query_string
optionSee also Elasticsearch documentation:
https://www.elastic.co/guide/en/elasticsearch/reference/2.3/query-dsl-query-string-query.html
The text was updated successfully, but these errors were encountered: