# How can I make this search requirement work?

**URL:** <https://discuss.elastic.co/t/how-can-i-make-this-search-requirement-work/18678>\
**Category:** Elasticsearch\
**Created:** [July 15, 2014, 2:40pm UTC](https://discuss.elastic.co/t/how-can-i-make-this-search-requirement-work/18678 "2014-07-15T14:40:29Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![mooky](https://avatars.discourse-cdn.com/v4/letter/m/43a26b/32.png) [@mooky](https://discuss.elastic.co/u/mooky)\
**Post date:** [July 15, 2014, 2:40pm UTC](https://discuss.elastic.co/t/how-can-i-make-this-search-requirement-work/18678/1 "2014-07-15T14:40:29Z")

</div>

I have a bit of an odd requirement in so far as analyzer is concerned.  
Wondering if anyone has any tips/suggestions.  
I have an item I am indexing (grade) that has a property (name) whose value  
can be "0# (99.995%)".  
I am doing a prefix search on \_all.  
I want users to be able to search using 99 or 99.9 or 99.995 or 99.995%.  
I also want the user to be able to copy-paste "0# (99.995%)" and it should  
work.

I am currently using the whitespace analyzer - which works for many of my  
cases except the tricky one above.  
99.995 doesnt work.  
But "(99.995" does. Because obviously after whitespace tokenization, the  
token begins with (.  
I could filter out the "(" and ")" characters. But then "0# (99.995%)" wont  
work.  
Does anyone have some different suggestions?

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/9813b93a-249d-41a9-be21-12c8ec5d6d23%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/9813b93a-249d-41a9-be21-12c8ec5d6d23%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![vineeth\_mohan\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vineeth_mohan_2/32/747_2.png) [@vineeth\_mohan\_2](https://discuss.elastic.co/u/vineeth_mohan_2)\
**Post date:** [July 15, 2014, 3:15pm UTC](https://discuss.elastic.co/t/how-can-i-make-this-search-requirement-work/18678/2 "2014-07-15T15:15:18Z")

</div>

Hello Mooky ,

You can apply multiple analyzers to a field -

> **[GitHub - yakaz/elasticsearch-analysis-combo: Elasticsearch Combo Analyzer](https://github.com/yakaz/elasticsearch-analysis-combo/)**
>
> Elasticsearch Combo Analyzer. Contribute to yakaz/elasticsearch-analysis-combo development by creating an account on GitHub.

So you can add all your analyzer here and apply it.

Thanks  
Vineeth

On Tue, Jul 15, 2014 at 8:10 PM, mooky [nick.minutello@gmail.com](mailto:nick.minutello@gmail.com) wrote:

> I have a bit of an odd requirement in so far as analyzer is concerned.  
> Wondering if anyone has any tips/suggestions.  
> I have an item I am indexing (grade) that has a property (name) whose  
> value can be "0# (99.995%)".  
> I am doing a prefix search on \_all.  
> I want users to be able to search using 99 or 99.9 or 99.995 or 99.995%.  
> I also want the user to be able to copy-paste "0# (99.995%)" and it should  
> work.
> 
> I am currently using the whitespace analyzer - which works for many of my  
> cases except the tricky one above.  
> 99.995 doesnt work.  
> But "(99.995" does. Because obviously after whitespace tokenization, the  
> token begins with (.  
> I could filter out the "(" and ")" characters. But then "0# (99.995%)"  
> wont work.  
> Does anyone have some different suggestions?
> 
> --  
> You received this message because you are subscribed to the Google Groups  
> "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> To view this discussion on the web visit  
> [https://groups.google.com/d/msgid/elasticsearch/9813b93a-249d-41a9-be21-12c8ec5d6d23%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/9813b93a-249d-41a9-be21-12c8ec5d6d23%40googlegroups.com)  
> [https://groups.google.com/d/msgid/elasticsearch/9813b93a-249d-41a9-be21-12c8ec5d6d23%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/9813b93a-249d-41a9-be21-12c8ec5d6d23%40googlegroups.com?utm_medium=email&utm_source=footer)  
> .  
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAGdPd5mdRgWFJ8Q3Nwr%2BWh6SLFGtzcCWJg1VVV%2BSbOEhw5ktzA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAGdPd5mdRgWFJ8Q3Nwr%2BWh6SLFGtzcCWJg1VVV%2BSbOEhw5ktzA%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![Glen\_Smith](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/glen_smith/32/111656_2.png) [@Glen\_Smith](https://discuss.elastic.co/u/Glen_Smith)\
**Post date:** [July 15, 2014, 3:33pm UTC](https://discuss.elastic.co/t/how-can-i-make-this-search-requirement-work/18678/3 "2014-07-15T15:33:36Z")

</div>

I would start by suggesting that you create an indexing/querying analyzer  
specifically for the field you know has this format.

Otherwise, I think your likeliest path to success, I think, is somewhere in  
the character filters domain.  
Character filters are applied to the string before the tokenizer:

> **[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.

One possibility here is a pattern replace char filter.

> **[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.

If you can write a matching pattern for all of the allowed values of this  
field, and replace them with just the number,  
apply that pattern to your indexing and searching, then you are only  
dealing with searching for the numbers.

You may need a different character filter for the search analyzer, though,  
since you are allowing for more formats than  
are found in the source document field.

On Tuesday, July 15, 2014 10:40:30 AM UTC-4, mooky wrote:

> I have a bit of an odd requirement in so far as analyzer is concerned.  
> Wondering if anyone has any tips/suggestions.  
> I have an item I am indexing (grade) that has a property (name) whose  
> value can be "0# (99.995%)".  
> I am doing a prefix search on \_all.  
> I want users to be able to search using 99 or 99.9 or 99.995 or 99.995%.  
> I also want the user to be able to copy-paste "0# (99.995%)" and it should  
> work.
> 
> I am currently using the whitespace analyzer - which works for many of my  
> cases except the tricky one above.  
> 99.995 doesnt work.  
> But "(99.995" does. Because obviously after whitespace tokenization, the  
> token begins with (.  
> I could filter out the "(" and ")" characters. But then "0# (99.995%)"  
> wont work.  
> Does anyone have some different suggestions?

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/805c3115-be4f-4ea5-a0d0-0153f9216043%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/805c3115-be4f-4ea5-a0d0-0153f9216043%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![mooky](https://avatars.discourse-cdn.com/v4/letter/m/43a26b/32.png) [@mooky](https://discuss.elastic.co/u/mooky)\
**Post date:** [July 15, 2014, 5:58pm UTC](https://discuss.elastic.co/t/how-can-i-make-this-search-requirement-work/18678/4 "2014-07-15T17:58:46Z")

</div>

Thanks. That looks interesting!

On Tuesday, 15 July 2014 16:15:23 UTC+1, vineeth mohan wrote:

> Hello Mooky ,
> 
> You can apply multiple analyzers to a field -  
> [GitHub - yakaz/elasticsearch-analysis-combo: Elasticsearch Combo Analyzer](https://github.com/yakaz/elasticsearch-analysis-combo/)
> 
> So you can add all your analyzer here and apply it.
> 
> Thanks  
> Vineeth
> 
> On Tue, Jul 15, 2014 at 8:10 PM, mooky \<[nick.mi...@gmail.com](mailto:nick.mi...@gmail.com) \<javascript:\>
> 
> > wrote:
> 
> > I have a bit of an odd requirement in so far as analyzer is concerned.  
> > Wondering if anyone has any tips/suggestions.  
> > I have an item I am indexing (grade) that has a property (name) whose  
> > value can be "0# (99.995%)".  
> > I am doing a prefix search on \_all.  
> > I want users to be able to search using 99 or 99.9 or 99.995 or 99.995%.  
> > I also want the user to be able to copy-paste "0# (99.995%)" and it  
> > should work.
> > 
> > I am currently using the whitespace analyzer - which works for many of my  
> > cases except the tricky one above.  
> > 99.995 doesnt work.  
> > But "(99.995" does. Because obviously after whitespace tokenization, the  
> > token begins with (.  
> > I could filter out the "(" and ")" characters. But then "0# (99.995%)"  
> > wont work.  
> > Does anyone have some different suggestions?
> > 
> > --  
> > You received this message because you are subscribed to the Google Groups  
> > "elasticsearch" group.  
> > To unsubscribe from this group and stop receiving emails from it, send an  
> > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \<javascript:\>.  
> > To view this discussion on the web visit  
> > [https://groups.google.com/d/msgid/elasticsearch/9813b93a-249d-41a9-be21-12c8ec5d6d23%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/9813b93a-249d-41a9-be21-12c8ec5d6d23%40googlegroups.com)  
> > [https://groups.google.com/d/msgid/elasticsearch/9813b93a-249d-41a9-be21-12c8ec5d6d23%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/9813b93a-249d-41a9-be21-12c8ec5d6d23%40googlegroups.com?utm_medium=email&utm_source=footer)  
> > .  
> > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/4e1a9a56-c504-4bc3-b59f-aed6e0226796%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/4e1a9a56-c504-4bc3-b59f-aed6e0226796%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![mooky](https://avatars.discourse-cdn.com/v4/letter/m/43a26b/32.png) [@mooky](https://discuss.elastic.co/u/mooky)\
**Post date:** [July 15, 2014, 6:11pm UTC](https://discuss.elastic.co/t/how-can-i-make-this-search-requirement-work/18678/5 "2014-07-15T18:11:46Z")

</div>

I think I can probably use a combo of the whitespace\* and standard  
analyzers.

My current analyzer settings are :

{

```
"analysis": {
    "analyzer": {
        "default_index": {
            "tokenizer": "whitespace",
            "filter": ["lowercase"]
        },
        "default_search": {
            "tokenizer": "whitespace",
            "filter": ["lowercase"]
        }
    }
}

```

}

-M

On Tuesday, 15 July 2014 16:15:23 UTC+1, vineeth mohan wrote:

> Hello Mooky ,
> 
> You can apply multiple analyzers to a field -  
> [GitHub - yakaz/elasticsearch-analysis-combo: Elasticsearch Combo Analyzer](https://github.com/yakaz/elasticsearch-analysis-combo/)
> 
> So you can add all your analyzer here and apply it.
> 
> Thanks  
> Vineeth
> 
> On Tue, Jul 15, 2014 at 8:10 PM, mooky \<[nick.mi...@gmail.com](mailto:nick.mi...@gmail.com) \<javascript:\>
> 
> > wrote:
> 
> > I have a bit of an odd requirement in so far as analyzer is concerned.  
> > Wondering if anyone has any tips/suggestions.  
> > I have an item I am indexing (grade) that has a property (name) whose  
> > value can be "0# (99.995%)".  
> > I am doing a prefix search on \_all.  
> > I want users to be able to search using 99 or 99.9 or 99.995 or 99.995%.  
> > I also want the user to be able to copy-paste "0# (99.995%)" and it  
> > should work.
> > 
> > I am currently using the whitespace analyzer - which works for many of my  
> > cases except the tricky one above.  
> > 99.995 doesnt work.  
> > But "(99.995" does. Because obviously after whitespace tokenization, the  
> > token begins with (.  
> > I could filter out the "(" and ")" characters. But then "0# (99.995%)"  
> > wont work.  
> > Does anyone have some different suggestions?
> > 
> > --  
> > You received this message because you are subscribed to the Google Groups  
> > "elasticsearch" group.  
> > To unsubscribe from this group and stop receiving emails from it, send an  
> > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \<javascript:\>.  
> > To view this discussion on the web visit  
> > [https://groups.google.com/d/msgid/elasticsearch/9813b93a-249d-41a9-be21-12c8ec5d6d23%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/9813b93a-249d-41a9-be21-12c8ec5d6d23%40googlegroups.com)  
> > [https://groups.google.com/d/msgid/elasticsearch/9813b93a-249d-41a9-be21-12c8ec5d6d23%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/9813b93a-249d-41a9-be21-12c8ec5d6d23%40googlegroups.com?utm_medium=email&utm_source=footer)  
> > .  
> > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/1f3177ef-020f-4263-bae4-ced1870567e8%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/1f3177ef-020f-4263-bae4-ced1870567e8%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![mooky](https://avatars.discourse-cdn.com/v4/letter/m/43a26b/32.png) [@mooky](https://discuss.elastic.co/u/mooky)\
**Post date:** [July 16, 2014, 10:47am UTC](https://discuss.elastic.co/t/how-can-i-make-this-search-requirement-work/18678/6 "2014-07-16T10:47:48Z")

</div>

And it works a treat. Thanks.

It leads me to think that it would be very useful to use with a series of  
specialist (special-case) analyzers in conjunction with the standard  
analyzer.

Back to my original example - "0# (99.995%)" - what I really want is  
something that will extract "99.995%".  
The standard analyzer will extract "99.995" (and the rest of the text), the  
whitespace analyzer will extract "(99.995%)".

Does a financial/numeric/accounting analyzer already exist? ie Something  
that extracts "99.995%" or "$44.5665" or "-45bps" ?

-M

On Tuesday, 15 July 2014 18:58:46 UTC+1, mooky wrote:

> Thanks. That looks interesting!
> 
> On Tuesday, 15 July 2014 16:15:23 UTC+1, vineeth mohan wrote:
> 
> > Hello Mooky ,
> > 
> > You can apply multiple analyzers to a field -  
> > [GitHub - yakaz/elasticsearch-analysis-combo: Elasticsearch Combo Analyzer](https://github.com/yakaz/elasticsearch-analysis-combo/)
> > 
> > So you can add all your analyzer here and apply it.
> > 
> > Thanks  
> > Vineeth
> > 
> > On Tue, Jul 15, 2014 at 8:10 PM, mooky [nick.mi...@gmail.com](mailto:nick.mi...@gmail.com) wrote:
> > 
> > > I have a bit of an odd requirement in so far as analyzer is concerned.  
> > > Wondering if anyone has any tips/suggestions.  
> > > I have an item I am indexing (grade) that has a property (name) whose  
> > > value can be "0# (99.995%)".  
> > > I am doing a prefix search on \_all.  
> > > I want users to be able to search using 99 or 99.9 or 99.995 or 99.995%.  
> > > I also want the user to be able to copy-paste "0# (99.995%)" and it  
> > > should work.
> > > 
> > > I am currently using the whitespace analyzer - which works for many of  
> > > my cases except the tricky one above.  
> > > 99.995 doesnt work.  
> > > But "(99.995" does. Because obviously after whitespace tokenization, the  
> > > token begins with (.  
> > > I could filter out the "(" and ")" characters. But then "0# (99.995%)"  
> > > wont work.  
> > > Does anyone have some different suggestions?
> > > 
> > > --  
> > > You received this message because you are subscribed to the Google  
> > > Groups "elasticsearch" group.  
> > > To unsubscribe from this group and stop receiving emails from it, send  
> > > an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com).  
> > > To view this discussion on the web visit  
> > > [https://groups.google.com/d/msgid/elasticsearch/9813b93a-249d-41a9-be21-12c8ec5d6d23%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/9813b93a-249d-41a9-be21-12c8ec5d6d23%40googlegroups.com)  
> > > [https://groups.google.com/d/msgid/elasticsearch/9813b93a-249d-41a9-be21-12c8ec5d6d23%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/9813b93a-249d-41a9-be21-12c8ec5d6d23%40googlegroups.com?utm_medium=email&utm_source=footer)  
> > > .  
> > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/78a267ff-869e-462d-80c4-057c907e0324%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/78a267ff-869e-462d-80c4-057c907e0324%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![smonasco\_2](https://avatars.discourse-cdn.com/v4/letter/s/848f3c/32.png) [@smonasco\_2](https://discuss.elastic.co/u/smonasco_2)\
**Post date:** [July 17, 2014, 3:58am UTC](https://discuss.elastic.co/t/how-can-i-make-this-search-requirement-work/18678/7 "2014-07-17T03:58:50Z")

</div>

A little late to the party but I would have used a custom index analyzer with lowercase, pattern, edgengram and a search analyzer of lowercase, pattern (maybe you have to flip lowercase and pattern)

With the pattern tokenizer you can specify a regex.

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/693ed0c3-2998-4da4-b30a-c7bf9f311770%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/693ed0c3-2998-4da4-b30a-c7bf9f311770%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![vineeth\_mohan\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vineeth_mohan_2/32/747_2.png) [@vineeth\_mohan\_2](https://discuss.elastic.co/u/vineeth_mohan_2)\
**Post date:** [July 17, 2014, 4:17am UTC](https://discuss.elastic.co/t/how-can-i-make-this-search-requirement-work/18678/8 "2014-07-17T04:17:29Z")

</div>

Hello Mooky ,

Elasticsearch is not any domain specific and hence wont take out these  
financial terms.  
You will need to write your own analyzer to facilitate this function.

Thanks  
Vineeth

On Wed, Jul 16, 2014 at 4:17 PM, mooky [nick.minutello@gmail.com](mailto:nick.minutello@gmail.com) wrote:

> And it works a treat. Thanks.
> 
> It leads me to think that it would be very useful to use with a series of  
> specialist (special-case) analyzers in conjunction with the standard  
> analyzer.
> 
> Back to my original example - "0# (99.995%)" - what I really want is  
> something that will extract "99.995%".  
> The standard analyzer will extract "99.995" (and the rest of the text),  
> the whitespace analyzer will extract "(99.995%)".
> 
> Does a financial/numeric/accounting analyzer already exist? ie Something  
> that extracts "99.995%" or "$44.5665" or "-45bps" ?
> 
> -M
> 
> On Tuesday, 15 July 2014 18:58:46 UTC+1, mooky wrote:
> 
> > Thanks. That looks interesting!
> > 
> > On Tuesday, 15 July 2014 16:15:23 UTC+1, vineeth mohan wrote:
> > 
> > > Hello Mooky ,
> > > 
> > > You can apply multiple analyzers to a field -[Yakaz · GitHub](https://github.com/yakaz/)  
> > > elasticsearch-analysis-combo/
> > > 
> > > So you can add all your analyzer here and apply it.
> > > 
> > > Thanks  
> > > Vineeth
> > > 
> > > On Tue, Jul 15, 2014 at 8:10 PM, mooky [nick.mi...@gmail.com](mailto:nick.mi...@gmail.com) wrote:
> > > 
> > > > I have a bit of an odd requirement in so far as analyzer is concerned.  
> > > > Wondering if anyone has any tips/suggestions.  
> > > > I have an item I am indexing (grade) that has a property (name) whose  
> > > > value can be "0# (99.995%)".  
> > > > I am doing a prefix search on \_all.  
> > > > I want users to be able to search using 99 or 99.9 or 99.995 or  
> > > > 99.995%.  
> > > > I also want the user to be able to copy-paste "0# (99.995%)" and it  
> > > > should work.
> > > > 
> > > > I am currently using the whitespace analyzer - which works for many of  
> > > > my cases except the tricky one above.  
> > > > 99.995 doesnt work.  
> > > > But "(99.995" does. Because obviously after whitespace tokenization,  
> > > > the token begins with (.  
> > > > I could filter out the "(" and ")" characters. But then "0# (99.995%)"  
> > > > wont work.  
> > > > Does anyone have some different suggestions?
> > > > 
> > > > --  
> > > > You received this message because you are subscribed to the Google  
> > > > Groups "elasticsearch" group.  
> > > > To unsubscribe from this group and stop receiving emails from it, send  
> > > > an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com).  
> > > > To view this discussion on the web visit [https://groups.google.com/d/](https://groups.google.com/d/)  
> > > > msgid/elasticsearch/9813b93a-249d-41a9-be21-12c8ec5d6d23%  
> > > > [40googlegroups.com](http://40googlegroups.com)  
> > > > [https://groups.google.com/d/msgid/elasticsearch/9813b93a-249d-41a9-be21-12c8ec5d6d23%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/9813b93a-249d-41a9-be21-12c8ec5d6d23%40googlegroups.com?utm_medium=email&utm_source=footer)  
> > > > .  
> > > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
> > > 
> > > --  
> > > You received this message because you are subscribed to the Google Groups  
> > > "elasticsearch" group.  
> > > To unsubscribe from this group and stop receiving emails from it, send an  
> > > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> > > To view this discussion on the web visit  
> > > [https://groups.google.com/d/msgid/elasticsearch/78a267ff-869e-462d-80c4-057c907e0324%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/78a267ff-869e-462d-80c4-057c907e0324%40googlegroups.com)  
> > > [https://groups.google.com/d/msgid/elasticsearch/78a267ff-869e-462d-80c4-057c907e0324%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/78a267ff-869e-462d-80c4-057c907e0324%40googlegroups.com?utm_medium=email&utm_source=footer)  
> > > .
> 
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAGdPd5kg7TRG%3DX\_%2B7tAueFaZ8pUYXbHrJhFZMVQaYcQyTicenQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAGdPd5kg7TRG%3DX_%2B7tAueFaZ8pUYXbHrJhFZMVQaYcQyTicenQ%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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, 1:15am UTC](https://discuss.elastic.co/t/how-can-i-make-this-search-requirement-work/18678/9 "2017-07-06T01:15:16Z")

</div>