Re: Kibana4 Beta3: Battling with wildcard search on not_analyzed fields

2015-02-04 Thread Ali Kheyrollahi
Thank you. That is the same with regexp. I managed to get it working with using 4 backslashes. On Wednesday, 4 February 2015 00:20:10 UTC, Itamar Syn-Hershko wrote: > > Here's a working gist: > > https://gist.github.com/synhershko/3d915a7819145f2d7a1f > > You need to double escape the slashes -

Re: Kibana4 Beta3: Battling with wildcard search on not_analyzed fields

2015-02-03 Thread Itamar Syn-Hershko
Here's a working gist: https://gist.github.com/synhershko/3d915a7819145f2d7a1f You need to double escape the slashes - not sure if this is by design or no but that works now -- Itamar Syn-Hershko http://code972.com | @synhershko Freelance Developer & Consultant

Re: Kibana4 Beta3: Battling with wildcard search on not_analyzed fields

2015-02-03 Thread Ali Kheyrollahi
Wildcard does not work either. {"wildcard":{"CounterName":"\\Windows Azure Caching:Client(w3wp_*)\\Failure Exceptions"}} And regardless, Regexp does not work so on its own right it is a bug. Can you please help open the issue on GitHub? Already have an issue which was closed: https://github.co

Re: Kibana4 Beta3: Battling with wildcard search on not_analyzed fields

2015-02-03 Thread Itamar Syn-Hershko
Thinking of it, I'm not sure why you are using regexp here - can you just use wildcard query instead? http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/query-dsl-wildcard-query.html -- Itamar Syn-Hershko http://code972.com | @synhershko Freelan

Re: Kibana4 Beta3: Battling with wildcard search on not_analyzed fields

2015-02-03 Thread Ali Kheyrollahi
No it doesn't which has been my experience: {"regexp":{"CounterName":"\\Windows Azure Caching:Client\\(w3wp_.*\\)\\Failure Exceptions"}} or {"regexp":{"CounterName":"\\Windows Azure Caching\\:Client\\(w3wp_.*\\)\\Failure Exceptions"}} None of them work -- You received this message because you

Re: Kibana4 Beta3: Battling with wildcard search on not_analyzed fields

2015-02-02 Thread Itamar Syn-Hershko
inline -- Itamar Syn-Hershko http://code972.com | @synhershko Freelance Developer & Consultant Lucene.NET committer and PMC member On Tue, Feb 3, 2015 at 1:32 AM, Ali Kheyrollahi wrote: > This *works* (exact value) > > {"term":{"CounterName":"\\Windows Azure Ca

Re: Kibana4 Beta3: Battling with wildcard search on not_analyzed fields

2015-02-02 Thread Ali Kheyrollahi
This *works* (exact value) {"term":{"CounterName":"\\Windows Azure Caching:Client(w3wp_5412)\\Failure Exceptions"}} But NOT this: {"term":{"CounterName":"Caching"}} Nor {"term":{"CounterName":"\\Windows Azure Caching:Client(w3wp_.*)\\Failure Exceptions"}} Or this {"term":{"CounterName":"\\Wind

Re: Kibana4 Beta3: Battling with wildcard search on not_analyzed fields

2015-02-02 Thread Itamar Syn-Hershko
Can you try executing a simple term query in JSON using that query bar? -- Itamar Syn-Hershko http://code972.com | @synhershko Freelance Developer & Consultant Lucene.NET committer and PMC member On Mon, Feb 2, 2015 at 11:57 PM, Ali Kheyrollahi wrote: > Thanks

Re: Kibana4 Beta3: Battling with wildcard search on not_analyzed fields

2015-02-02 Thread Ali Kheyrollahi
Thanks for responding. It is *surely* not_analyzed - hence my frustration. Here is the mapping { "my_index": { "mappings": { "my_type": { "properties": { "@timestamp": { "type": "date", "f

Re: Kibana4 Beta3: Battling with wildcard search on not_analyzed fields

2015-02-02 Thread Itamar Syn-Hershko
It looks like your field is analyzed and you are trying to query it assuming its not_analyzed (e.g. one string). Hard to say without seeing your index mapping. -- Itamar Syn-Hershko http://code972.com | @synhershko Freelance Developer & Consultant Lucene.NET commi

Re: Kibana4 Beta3: Battling with wildcard search on not_analyzed fields

2015-02-02 Thread Ali Kheyrollahi
Any help please?? On Saturday, 31 January 2015 09:56:38 UTC, Ali Kheyrollahi wrote: > > Hi, > > I really haven't found a consistent way to use query window in Discover or > Visualize tabs. My results become hit and miss and inconsistent. > > So I am searching for types of "my_type" and I have a

Re: Kibana4 Beta3: Battling with wildcard search on not_analyzed fields

2015-02-01 Thread Ali Kheyrollahi
Anyone please?? On Saturday, 31 January 2015 09:56:38 UTC, Ali Kheyrollahi wrote: > > Hi, > > I really haven't found a consistent way to use query window in Discover or > Visualize tabs. My results become hit and miss and inconsistent. > > So I am searching for types of "my_type" and I have a fi

Kibana4 Beta3: Battling with wildcard search on not_analyzed fields

2015-01-31 Thread Ali Kheyrollahi
Hi, I really haven't found a consistent way to use query window in Discover or Visualize tabs. My results become hit and miss and inconsistent. So I am searching for types of "my_type" and I have a field called CounterName and I am looking for \Windows Azure Caching:Client(w3wp_2392)\Total Lo