# Serching fields which ends in a number and a file extension

**URL:** <https://discuss.elastic.co/t/serching-fields-which-ends-in-a-number-and-a-file-extension/81021>\
**Category:** Elasticsearch\
**Created:** [April 3, 2017, 3:24pm UTC](https://discuss.elastic.co/t/serching-fields-which-ends-in-a-number-and-a-file-extension/81021 "2017-04-03T15:24:09Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![YvorL](https://avatars.discourse-cdn.com/v4/letter/y/9fc348/32.png) [@YvorL](https://discuss.elastic.co/u/YvorL)\
**Post date:** [April 3, 2017, 3:24pm UTC](https://discuss.elastic.co/t/serching-fields-which-ends-in-a-number-and-a-file-extension/81021/1 "2017-04-03T15:24:09Z")

</div>

I bumped into a strange issue. When I tried to look for the most requested documents (pdf) on one of the analyzed sites, I saw that there are some docs definitely missing. First I used "request:\*.pdf" then I checked "request:pdf". That was the time I noticed that the wildcard request missed ALL documents which request ended in any number before '.pdf' such as 'calendar\_2017.pdf'. Which is odd, because it is a string field so I don't understand how a number can cause this issue. Is there something I can do without reindexing the data?

@Brandon_Kobel said that the analyzer splits the file name to terms and in this case, it splits the string when it encounters a dot after a number.

I didn't encounter this exception in any Lucene or Elastic document but I definitely didn't read all 🙂

---

<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:** [May 1, 2017, 3:24pm UTC](https://discuss.elastic.co/t/serching-fields-which-ends-in-a-number-and-a-file-extension/81021/2 "2017-05-01T15:24:11Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.