# Exact matching

**URL:** <https://discuss.elastic.co/t/exact-matching/5077>\
**Category:** Elasticsearch\
**Created:** [August 8, 2011, 5:14am UTC](https://discuss.elastic.co/t/exact-matching/5077 "2011-08-08T05:14:49Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![BeckerIV](https://avatars.discourse-cdn.com/v4/letter/b/f05b48/32.png) [@BeckerIV](https://discuss.elastic.co/u/BeckerIV)\
**Post date:** [August 8, 2011, 5:14am UTC](https://discuss.elastic.co/t/exact-matching/5077/1 "2011-08-08T05:14:49Z")

</div>

I am trying to build a query to match a string (username) exactly.

> <https://gist.github.com/sbeckeriv/1131225>

I thought term would work for me.

Any help would be well..helpful  
Thanks!  
Becker

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [August 8, 2011, 7:35am UTC](https://discuss.elastic.co/t/exact-matching/5077/2 "2011-08-08T07:35:26Z")

</div>

Are you sure the username is not analyzed? Use get mapping to verify it is:

> **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)**
>
> Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today.

.

On Mon, Aug 8, 2011 at 8:14 AM, BeckerIV [sbeckeriv@gmail.com](mailto:sbeckeriv@gmail.com) wrote:

> I am trying to build a query to match a string (username) exactly.
> 
> [Exact matching · GitHub](https://gist.github.com/1131225)
> 
> I thought term would work for me.
> 
> Any help would be well..helpful  
> Thanks!  
> Becker

---

<div class="post-metadata">

**Author:** ![BeckerIV](https://avatars.discourse-cdn.com/v4/letter/b/f05b48/32.png) [@BeckerIV](https://discuss.elastic.co/u/BeckerIV)\
**Post date:** [August 8, 2011, 2:59pm UTC](https://discuss.elastic.co/t/exact-matching/5077/3 "2011-08-08T14:59:22Z")

</div>

Thanks. It still gives me many matt's.

I found I was running 5 elasticsearches. I stopped them all. Deleted the  
data directory and re-added the data. This was an error in how I was  
setup and running elasticsearch. I updated the gist  
[Exact matching · GitHub](https://gist.github.com/1131225) with the mapping call. I am still  
seeing the same results. I am sure I am now running only one elasticsearch.

Thanks again for the help.  
Becker

On Mon, Aug 8, 2011 at 12:35 AM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote:

> Are you sure the username is not analyzed? Use get mapping to verify it  
> is: [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/api/admin-indices-get-mapping.html).
> 
> On Mon, Aug 8, 2011 at 8:14 AM, BeckerIV [sbeckeriv@gmail.com](mailto:sbeckeriv@gmail.com) wrote:
> 
> > I am trying to build a query to match a string (username) exactly.
> > 
> > [Exact matching · GitHub](https://gist.github.com/1131225)
> > 
> > I thought term would work for me.
> > 
> > Any help would be well..helpful  
> > Thanks!  
> > Becker

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [August 8, 2011, 3:12pm UTC](https://discuss.elastic.co/t/exact-matching/5077/4 "2011-08-08T15:12:01Z")

</div>

You have two types? document and person? Make sure username is not analyzed  
on both of them.

On Mon, Aug 8, 2011 at 5:59 PM, SbeckerIV [sbeckeriv@gmail.com](mailto:sbeckeriv@gmail.com) wrote:

> Thanks. It still gives me many matt's.
> 
> I found I was running 5 elasticsearches. I stopped them all. Deleted the  
> data directory and re-added the data. This was an error in how I was  
> setup and running elasticsearch. I updated the gist  
> [Exact matching · GitHub](https://gist.github.com/1131225) with the mapping call. I am still  
> seeing the same results. I am sure I am now running only one elasticsearch.
> 
> Thanks again for the help.  
> Becker
> 
> On Mon, Aug 8, 2011 at 12:35 AM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote:
> 
> > Are you sure the username is not analyzed? Use get mapping to verify it  
> > is:  
> > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/api/admin-indices-get-mapping.html)  
> > .
> > 
> > On Mon, Aug 8, 2011 at 8:14 AM, BeckerIV [sbeckeriv@gmail.com](mailto:sbeckeriv@gmail.com) wrote:
> > 
> > > I am trying to build a query to match a string (username) exactly.
> > > 
> > > [Exact matching · GitHub](https://gist.github.com/1131225)
> > > 
> > > I thought term would work for me.
> > > 
> > > Any help would be well..helpful  
> > > Thanks!  
> > > Becker

---

<div class="post-metadata">

**Author:** ![BeckerIV](https://avatars.discourse-cdn.com/v4/letter/b/f05b48/32.png) [@BeckerIV](https://discuss.elastic.co/u/BeckerIV)\
**Post date:** [August 8, 2011, 4:11pm UTC](https://discuss.elastic.co/t/exact-matching/5077/5 "2011-08-08T16:11:42Z")

</div>

I dont mean to have two types. I am using the ruby Tire lib. I will  
work on recreating my types via curl and see if that helps things. I  
changed username to person.username and I also tried /g/person/\_search  
both of those came up empty. The way I index the data is incorrect.  
that would explain why there is a second type!

Thanks for helping me debug this. Im pretty sure its my bulk index  
code. I will let you know when I figure it out.  
Becker

On Mon, Aug 8, 2011 at 8:12 AM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote:

> You have two types? document and person? Make sure username is not analyzed  
> on both of them.
> 
> On Mon, Aug 8, 2011 at 5:59 PM, SbeckerIV [sbeckeriv@gmail.com](mailto:sbeckeriv@gmail.com) wrote:
> 
> > Thanks. It still gives me many matt's.
> > 
> > I found I was running 5 elasticsearches. I stopped them all. Deleted the  
> > data directory and re-added the data. This was an error in how I was  
> > setup and running elasticsearch. I updated the gist  
> > [Exact matching · GitHub](https://gist.github.com/1131225) with the mapping call. I am still  
> > seeing the same results. I am sure I am now running only one  
> > elasticsearch.
> > 
> > Thanks again for the help.  
> > Becker
> > 
> > On Mon, Aug 8, 2011 at 12:35 AM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote:
> > 
> > > Are you sure the username is not analyzed? Use get mapping to verify it
> > > 
> > > is: [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/api/admin-indices-get-mapping.html).
> > > 
> > > On Mon, Aug 8, 2011 at 8:14 AM, BeckerIV [sbeckeriv@gmail.com](mailto:sbeckeriv@gmail.com) wrote:
> > > 
> > > > I am trying to build a query to match a string (username) exactly.
> > > > 
> > > > [Exact matching · GitHub](https://gist.github.com/1131225)
> > > > 
> > > > I thought term would work for me.
> > > > 
> > > > Any help would be well..helpful  
> > > > Thanks!  
> > > > Becker

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [August 8, 2011, 4:31pm UTC](https://discuss.elastic.co/t/exact-matching/5077/6 "2011-08-08T16:31:36Z")

</div>

For some reason, you end up indexing two types, I would check the indexing  
code and see why it happens... .

On Mon, Aug 8, 2011 at 7:11 PM, SbeckerIV [sbeckeriv@gmail.com](mailto:sbeckeriv@gmail.com) wrote:

> I dont mean to have two types. I am using the ruby Tire lib. I will  
> work on recreating my types via curl and see if that helps things. I  
> changed username to person.username and I also tried /g/person/\_search  
> both of those came up empty. The way I index the data is incorrect.  
> that would explain why there is a second type!
> 
> Thanks for helping me debug this. Im pretty sure its my bulk index  
> code. I will let you know when I figure it out.  
> Becker
> 
> On Mon, Aug 8, 2011 at 8:12 AM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote:
> 
> > You have two types? document and person? Make sure username is not  
> > analyzed  
> > on both of them.
> > 
> > On Mon, Aug 8, 2011 at 5:59 PM, SbeckerIV [sbeckeriv@gmail.com](mailto:sbeckeriv@gmail.com) wrote:
> > 
> > > Thanks. It still gives me many matt's.
> > > 
> > > I found I was running 5 elasticsearches. I stopped them all. Deleted the  
> > > data directory and re-added the data. This was an error in how I was  
> > > setup and running elasticsearch. I updated the gist  
> > > [Exact matching · GitHub](https://gist.github.com/1131225) with the mapping call. I am still  
> > > seeing the same results. I am sure I am now running only one  
> > > elasticsearch.
> > > 
> > > Thanks again for the help.  
> > > Becker
> > > 
> > > On Mon, Aug 8, 2011 at 12:35 AM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote:
> > > 
> > > > Are you sure the username is not analyzed? Use get mapping to verify  
> > > > it
> > > > 
> > > > is:  
> > > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/api/admin-indices-get-mapping.html)  
> > > > .
> > > > 
> > > > On Mon, Aug 8, 2011 at 8:14 AM, BeckerIV [sbeckeriv@gmail.com](mailto:sbeckeriv@gmail.com) wrote:
> > > > 
> > > > > I am trying to build a query to match a string (username) exactly.
> > > > > 
> > > > > [Exact matching · GitHub](https://gist.github.com/1131225)
> > > > > 
> > > > > I thought term would work for me.
> > > > > 
> > > > > Any help would be well..helpful  
> > > > > Thanks!  
> > > > > Becker

---

<div class="post-metadata">

**Author:** ![Javier\_Muniz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/javier_muniz/32/3142_2.png) [@Javier\_Muniz](https://discuss.elastic.co/u/Javier_Muniz)\
**Post date:** [August 8, 2011, 4:40pm UTC](https://discuss.elastic.co/t/exact-matching/5077/7 "2011-08-08T16:40:05Z")

</div>

I saw this same behavior when using Tire this weekend. Are you indexing the item twice? I found that Tire's import method was stripping type from the documents, so when I reused the object to store an update, my type was set to document. Kindof an odd corner case, but it's definitely odd that Tire's import appears to modify the array of documents passed into it.

-javier

* * *

From: [elasticsearch@googlegroups.com](mailto:elasticsearch@googlegroups.com) [elasticsearch@googlegroups.com] on behalf of Shay Banon [kimchy@gmail.com]  
Sent: Monday, August 08, 2011 9:31 AM  
To: [elasticsearch@googlegroups.com](mailto:elasticsearch@googlegroups.com)  
Subject: Re: Exact matching

For some reason, you end up indexing two types, I would check the indexing code and see why it happens... .

On Mon, Aug 8, 2011 at 7:11 PM, SbeckerIV \<[sbeckeriv@gmail.com](mailto:sbeckeriv@gmail.com)[mailto:sbeckeriv@gmail.com](mailto:sbeckeriv@gmail.com)\> wrote:  
I dont mean to have two types. I am using the ruby Tire lib. I will  
work on recreating my types via curl and see if that helps things. I  
changed username to person.username and I also tried /g/person/\_search  
both of those came up empty. The way I index the data is incorrect.  
that would explain why there is a second type!

Thanks for helping me debug this. Im pretty sure its my bulk index  
code. I will let you know when I figure it out.  
Becker

On Mon, Aug 8, 2011 at 8:12 AM, Shay Banon \<[kimchy@gmail.com](mailto:kimchy@gmail.com)[mailto:kimchy@gmail.com](mailto:kimchy@gmail.com)\> wrote:

> You have two types? document and person? Make sure username is not analyzed  
> on both of them.
> 
> On Mon, Aug 8, 2011 at 5:59 PM, SbeckerIV \<[sbeckeriv@gmail.com](mailto:sbeckeriv@gmail.com)[mailto:sbeckeriv@gmail.com](mailto:sbeckeriv@gmail.com)\> wrote:
> 
> > Thanks. It still gives me many matt's.
> > 
> > I found I was running 5 elasticsearches. I stopped them all. Deleted the  
> > data directory and re-added the data. This was an error in how I was  
> > setup and running elasticsearch. I updated the gist  
> > [Exact matching · GitHub](https://gist.github.com/1131225) with the mapping call. I am still  
> > seeing the same results. I am sure I am now running only one  
> > elasticsearch.
> > 
> > Thanks again for the help.  
> > Becker
> > 
> > On Mon, Aug 8, 2011 at 12:35 AM, Shay Banon \<[kimchy@gmail.com](mailto:kimchy@gmail.com)[mailto:kimchy@gmail.com](mailto:kimchy@gmail.com)\> wrote:
> > 
> > > Are you sure the username is not analyzed? Use get mapping to verify it
> > > 
> > > is: [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/api/admin-indices-get-mapping.html).
> > > 
> > > On Mon, Aug 8, 2011 at 8:14 AM, BeckerIV \<[sbeckeriv@gmail.com](mailto:sbeckeriv@gmail.com)[mailto:sbeckeriv@gmail.com](mailto:sbeckeriv@gmail.com)\> wrote:
> > > 
> > > > I am trying to build a query to match a string (username) exactly.
> > > > 
> > > > [Exact matching · GitHub](https://gist.github.com/1131225)
> > > > 
> > > > I thought term would work for me.
> > > > 
> > > > Any help would be well..helpful  
> > > > Thanks!  
> > > > Becker

---

<div class="post-metadata">

**Author:** ![BeckerIV](https://avatars.discourse-cdn.com/v4/letter/b/f05b48/32.png) [@BeckerIV](https://discuss.elastic.co/u/BeckerIV)\
**Post date:** [August 9, 2011, 4:13am UTC](https://discuss.elastic.co/t/exact-matching/5077/8 "2011-08-09T04:13:24Z")

</div>

After reading the tire gem I had locally I needed to use "type" or  
:type as a key in my data hashes. The newer version has more logic and  
includes :\_type or "\_type" which I was using.

[https://github.com/karmi/tire/blob/master/lib/tire/index.rb](https://github.com/karmi/tire/blob/master/lib/tire/index.rb) line  
270ish for more.

Thanks everyone for the help! I am now only getting one matt back.  
Also I suspect the geo features should work now.  
Thanks so much!  
Becker

On Mon, Aug 8, 2011 at 9:40 AM, Javier Muniz [javier@granicus.com](mailto:javier@granicus.com) wrote:

> I saw this same behavior when using Tire this weekend. Are you indexing the  
> item twice? I found that Tire's import method was stripping type from the  
> documents, so when I reused the object to store an update, my type was set  
> to document. Kindof an odd corner case, but it's definitely odd that Tire's  
> import appears to modify the array of documents passed into it.
> 
> -javier
> 
> * * *
> 
> From: [elasticsearch@googlegroups.com](mailto:elasticsearch@googlegroups.com) [elasticsearch@googlegroups.com] on  
> behalf of Shay Banon [kimchy@gmail.com]  
> Sent: Monday, August 08, 2011 9:31 AM  
> To: [elasticsearch@googlegroups.com](mailto:elasticsearch@googlegroups.com)  
> Subject: Re: Exact matching
> 
> For some reason, you end up indexing two types, I would check the indexing  
> code and see why it happens... .
> 
> On Mon, Aug 8, 2011 at 7:11 PM, SbeckerIV [sbeckeriv@gmail.com](mailto:sbeckeriv@gmail.com) wrote:
> 
> > I dont mean to have two types. I am using the ruby Tire lib. I will  
> > work on recreating my types via curl and see if that helps things. I  
> > changed username to person.username and I also tried /g/person/\_search  
> > both of those came up empty. The way I index the data is incorrect.  
> > that would explain why there is a second type!
> > 
> > Thanks for helping me debug this. Im pretty sure its my bulk index  
> > code. I will let you know when I figure it out.  
> > Becker
> > 
> > On Mon, Aug 8, 2011 at 8:12 AM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote:
> > 
> > > You have two types? document and person? Make sure username is not  
> > > analyzed  
> > > on both of them.
> > > 
> > > On Mon, Aug 8, 2011 at 5:59 PM, SbeckerIV [sbeckeriv@gmail.com](mailto:sbeckeriv@gmail.com) wrote:
> > > 
> > > > Thanks. It still gives me many matt's.
> > > > 
> > > > I found I was running 5 elasticsearches. I stopped them all. Deleted  
> > > > the  
> > > > data directory and re-added the data. This was an error in how I was  
> > > > setup and running elasticsearch. I updated the gist  
> > > > [Exact matching · GitHub](https://gist.github.com/1131225) with the mapping call. I am still  
> > > > seeing the same results. I am sure I am now running only one  
> > > > elasticsearch.
> > > > 
> > > > Thanks again for the help.  
> > > > Becker
> > > > 
> > > > On Mon, Aug 8, 2011 at 12:35 AM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote:
> > > > 
> > > > > Are you sure the username is not analyzed? Use get mapping to verify  
> > > > > it
> > > > > 
> > > > > is: [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/api/admin-indices-get-mapping.html).
> > > > > 
> > > > > On Mon, Aug 8, 2011 at 8:14 AM, BeckerIV [sbeckeriv@gmail.com](mailto:sbeckeriv@gmail.com) wrote:
> > > > > 
> > > > > > I am trying to build a query to match a string (username) exactly.
> > > > > > 
> > > > > > [Exact matching · GitHub](https://gist.github.com/1131225)
> > > > > > 
> > > > > > I thought term would work for me.
> > > > > > 
> > > > > > Any help would be well..helpful  
> > > > > > Thanks!  
> > > > > > Becker

---

<div class="post-metadata">

**Author:** ![karmi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/karmi/32/44951_2.png) [@karmi](https://discuss.elastic.co/u/karmi)\
**Post date:** [August 9, 2011, 9:33pm UTC](https://discuss.elastic.co/t/exact-matching/5077/9 "2011-08-09T21:33:36Z")

</div>

Hi,

a) why not use the curl-based output from Tire's logger, implemented  
exactly for a situation like this, for the gist? (see readme)

b) it's fairly clear you should set the type property in the  
[http://karmi.github.com/tire](http://karmi.github.com/tire) docs...

@javier: could you extract the problem you had with stripping the type  
property from the Hash and send an issue for that? The reasoning  
behind is, of course, that storing the type is completely unnecessary,  
because such information is already contained in the ES document  
type...

Karel

On 9 srp, 06:13, SbeckerIV [sbecke...@gmail.com](mailto:sbecke...@gmail.com) wrote:

> After reading the tire gem I had locally I needed to use "type" or  
> :type as a key in my data hashes. The newer version has more logic and  
> includes :\_type or "\_type" which I was using.
> 
> [https://github.com/karmi/tire/blob/master/lib/tire/index.rbline](https://github.com/karmi/tire/blob/master/lib/tire/index.rbline)  
> 270ish for more.
> 
> Thanks everyone for the help! I am now only getting one matt back.  
> Also I suspect the geo features should work now.  
> Thanks so much!  
> Becker
> 
> On Mon, Aug 8, 2011 at 9:40 AM, Javier Muniz [jav...@granicus.com](mailto:jav...@granicus.com) wrote:
> 
> > I saw this same behavior when using Tire this weekend. Are you indexing the  
> > item twice? I found that Tire's import method was stripping type from the  
> > documents, so when I reused the object to store an update, my type was set  
> > to document. Kindof an odd corner case, but it's definitely odd that Tire's  
> > import appears to modify the array of documents passed into it.
> 
> > -javier
> > 
> > * * *
> > 
> > From: [elasticsearch@googlegroups.com](mailto:elasticsearch@googlegroups.com) [elasticsearch@googlegroups.com] on  
> > behalf of Shay Banon [kim...@gmail.com]  
> > Sent: Monday, August 08, 2011 9:31 AM  
> > To: [elasticsearch@googlegroups.com](mailto:elasticsearch@googlegroups.com)  
> > Subject: Re: Exact matching
> 
> > For some reason, you end up indexing two types, I would check the indexing  
> > code and see why it happens... .
> 
> > On Mon, Aug 8, 2011 at 7:11 PM, SbeckerIV [sbecke...@gmail.com](mailto:sbecke...@gmail.com) wrote:
> 
> > > I dont mean to have two types. I am using the ruby Tire lib. I will  
> > > work on recreating my types via curl and see if that helps things. I  
> > > changed username to person.username and I also tried /g/person/\_search  
> > > both of those came up empty. The way I index the data is incorrect.  
> > > that would explain why there is a second type!
> 
> > > Thanks for helping me debug this. Im pretty sure its my bulk index  
> > > code. I will let you know when I figure it out.  
> > > Becker
> 
> > > On Mon, Aug 8, 2011 at 8:12 AM, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote:
> > > 
> > > > You have two types? document and person? Make sure username is not  
> > > > analyzed  
> > > > on both of them.
> 
> > > > On Mon, Aug 8, 2011 at 5:59 PM, SbeckerIV [sbecke...@gmail.com](mailto:sbecke...@gmail.com) wrote:
> 
> > > > > Thanks. It still gives me many matt's.
> 
> > > > > I found I was running 5 elasticsearches. I stopped them all. Deleted  
> > > > > the  
> > > > > data directory and re-added the data. This was an error in how I was  
> > > > > setup and running elasticsearch. I updated the gist  
> > > > > [https://gist.github.com/1131225with](https://gist.github.com/1131225with) the mapping call. I am still  
> > > > > seeing the same results. I am sure I am now running only one  
> > > > > elasticsearch.
> 
> > > > > Thanks again for the help.  
> > > > > Becker
> 
> > > > > On Mon, Aug 8, 2011 at 12:35 AM, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote:
> > > > > 
> > > > > > Are you sure the username is not analyzed? Use get mapping to verify  
> > > > > > it
> 
> > > > > > is: [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/api/admin-indices-get-ma)....
> 
> > > > > > On Mon, Aug 8, 2011 at 8:14 AM, BeckerIV [sbecke...@gmail.com](mailto:sbecke...@gmail.com) wrote:
> 
> > > > > > > I am trying to build a query to match a string (username) exactly.
> 
> > > > > > > [Exact matching · GitHub](https://gist.github.com/1131225)
> 
> > > > > > > I thought term would work for me.
> 
> > > > > > > Any help would be well..helpful  
> > > > > > > Thanks!  
> > > > > > > Becker

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 3:57am UTC](https://discuss.elastic.co/t/exact-matching/5077/10 "2017-07-06T03:57:41Z")

</div>


