# Is "Will" or "will" reserved for sorting? **URL:** \ **Category:** Elasticsearch\ **Created:** [August 31, 2012, 4:03pm UTC](https://discuss.elastic.co/t/is-will-or-will-reserved-for-sorting/8905 "2012-08-31T16:03:47Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![samCougars](https://avatars.discourse-cdn.com/v4/letter/s/71e660/32.png) [@samCougars](https://discuss.elastic.co/u/samCougars)\ **Post date:** [August 31, 2012, 4:03pm UTC](https://discuss.elastic.co/t/is-will-or-will-reserved-for-sorting/8905/1 "2012-08-31T16:03:47Z")
I have "will" as value on one of my indexed field(firstNameSort). When I do a sorting on that particular field(firstNameSort), the recored with "will" on that field shows up on top. Has anyone seen this issue? Here is my curl command: { "size" : 300, "query" : { "match\_all" : { } }, "sort" : [ { "firstNameSort" : { "order" : "asc" } } ] } ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [August 31, 2012, 4:49pm UTC](https://discuss.elastic.co/t/is-will-or-will-reserved-for-sorting/8905/2 "2012-08-31T16:49:47Z")
Do you use default analyzer ? If so, i suppose that will is not indexed as it's an english common verb. HTH -- David 😉 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs Le 31 août 2012 à 18:03, samCougars [sbaniya@gmail.com](mailto:sbaniya@gmail.com) a écrit : > I have "will" as value on one of my indexed field(firstNameSort). When I do a > sorting on that particular field(firstNameSort), the recored with "will" on > that field shows up on top. Has anyone seen this issue? > Here is my curl command: > { > "size" : 300, > "query" : { > "match\_all" : { > } > }, > "sort" : [ { > "firstNameSort" : { > "order" : "asc" > } > } ] > } > > -- > View this message in context: [http://elasticsearch-users.115913.n3.nabble.com/Is-Will-or-will-reserved-for-sorting-tp4022341.html](http://elasticsearch-users.115913.n3.nabble.com/Is-Will-or-will-reserved-for-sorting-tp4022341.html) > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com). > > -- -- ---
**Author:** ![samCougars](https://avatars.discourse-cdn.com/v4/letter/s/71e660/32.png) [@samCougars](https://discuss.elastic.co/u/samCougars)\ **Post date:** [August 31, 2012, 5:15pm UTC](https://discuss.elastic.co/t/is-will-or-will-reserved-for-sorting/8905/3 "2012-08-31T17:15:35Z")
I'm not using any kind of analyzer at all. So with that, it might be just using default analyzer then. How would I add "will" as a common verb? ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [August 31, 2012, 5:32pm UTC](https://discuss.elastic.co/t/is-will-or-will-reserved-for-sorting/8905/4 "2012-08-31T17:32:41Z")
Just to be sure, that's the issue, try to set analyze to no for that field, reindex and search with sort. -- David 😉 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs Le 31 août 2012 à 19:15, samCougars [sbaniya@gmail.com](mailto:sbaniya@gmail.com) a écrit : > I'm not using any kind of analyzer at all. So with that, it might be just > using default analyzer then. How would I add "will" as a common verb? > > -- > View this message in context: [http://elasticsearch-users.115913.n3.nabble.com/Is-Will-or-will-reserved-for-sorting-tp4022341p4022343.html](http://elasticsearch-users.115913.n3.nabble.com/Is-Will-or-will-reserved-for-sorting-tp4022341p4022343.html) > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com). > > -- -- ---
**Author:** ![samCougars](https://avatars.discourse-cdn.com/v4/letter/s/71e660/32.png) [@samCougars](https://discuss.elastic.co/u/samCougars)\ **Post date:** [August 31, 2012, 8:08pm UTC](https://discuss.elastic.co/t/is-will-or-will-reserved-for-sorting/8905/5 "2012-08-31T20:08:22Z")
Thanks David. I added to ignore built-in stop words from lucene on my config file since I'm already removing stop words in my app. And now it is working fine. By the way, it was not just word "will", it had to do with all stop words... Here is the config I added on elasticsearch.yml : #Index Settings index: analysis: analyzer: # set standard analyzer with no stop words as the default for both indexing and searching default: type: standard stopwords: _none_ ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [August 31, 2012, 8:13pm UTC](https://discuss.elastic.co/t/is-will-or-will-reserved-for-sorting/8905/6 "2012-08-31T20:13:45Z")
Thanks for the feedback. I was not aware of the _none_ stopwords config. -- David 😉 Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs Le 31 août 2012 à 22:08, samCougars [sbaniya@gmail.com](mailto:sbaniya@gmail.com) a écrit : > Thanks David. I added to ignore built-in stop words from lucene on my config > file since I'm already removing stop words in my app. And now it is working > fine. By the way, it was not just word "will", it had to do with all stop > words... > Here is the config I added on elasticsearch.yml : > #Index Settings > index: > analysis: > analyzer: > # set standard analyzer with no stop words as the default for both > indexing and searching > default: > type: standard > stopwords: _none_ > > -- > View this message in context: [http://elasticsearch-users.115913.n3.nabble.com/Is-Will-or-will-reserved-for-sorting-tp4022341p4022357.html](http://elasticsearch-users.115913.n3.nabble.com/Is-Will-or-will-reserved-for-sorting-tp4022341p4022357.html) > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com). > > -- -- ---
**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:14am UTC](https://discuss.elastic.co/t/is-will-or-will-reserved-for-sorting/8905/7 "2017-07-06T03:14:21Z")