# Search using speical characater

**URL:** <https://discuss.elastic.co/t/search-using-speical-characater/3539>\
**Category:** Elasticsearch\
**Created:** [November 9, 2010, 5:50am UTC](https://discuss.elastic.co/t/search-using-speical-characater/3539 "2010-11-09T05:50:30Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![srrin](https://avatars.discourse-cdn.com/v4/letter/s/85f322/32.png) [@srrin](https://discuss.elastic.co/u/srrin)\
**Post date:** [November 9, 2010, 5:50am UTC](https://discuss.elastic.co/t/search-using-speical-characater/3539/1 "2010-11-09T05:50:30Z")

</div>

Hi ,  
I have a search request which passes lucene query string as search criteria as like  
pagecount:{2 TO 4] which is produced from lucenes constantsearchrangequery. Since I m having "{" is in the search criteria I am unable to suceed. My full search request using JSON is as follows

curl -XGET '[http://localhost/db25/\_search](http://localhost/db25/_search)' -d '{ "query" : { "query\_string" : { "default\_field" : "", "query" : "+(pagecount:{2 TO 4])","default\_operator" : "OR","analyzer" : "Standard","allow\_leading\_wildcard" : true,"lowercase\_expanded\_terms" : true,"enable\_position\_increments" : true,"fuzzy\_prefix\_length" : 0,"fuzzy\_min\_sim" : 0.5,"phrase\_slop" : 0,"boost" : 1.0 } }, "from" : 0, "size" : 0, "facets" : {"tag\_reviewstatus" : { "terms" : { "field" :"\_reviewstatus","size" : 10 } } , "global" : false }, "explain" : false }'

Once I pass this request in CURL I am getting ParseException as SEARCHPHASEEXECUTIONEXCEPTION.  
Kindly help. Thanks in advance

-SRR

---

<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:** [November 10, 2010, 10:57am UTC](https://discuss.elastic.co/t/search-using-speical-characater/3539/2 "2010-11-10T10:57:05Z")

</div>

And if you execute it with pagecount:[2 TO 4] or pagecount:{2 TO 4} it  
works? If I am not mistaken, the query parser does not allow to mix { or }  
with [or]. You can use the range query explicitly in the query DSL to  
support that.

On Tue, Nov 9, 2010 at 7:50 AM, srrIN [srrranga@gmail.com](mailto:srrranga@gmail.com) wrote:

> Hi ,  
> I have a search request which passes lucene query string as search criteria  
> as like  
> pagecount:{2 TO 4] which is produced from lucenes constantsearchrangequery.  
> Since I m having "{" is in the search criteria I am unable to suceed. My  
> full search request using JSON is as follows
> 
> curl -XGET '[http://localhost/db25/\_search](http://localhost/db25/_search)' -d '{ "query" : {  
> "query\_string"  
> : { "default\_field" : "", "query" : "+(pagecount:{2 TO  
> 4])","default\_operator" : "OR","analyzer" :  
> "Standard","allow\_leading\_wildcard" : true,"lowercase\_expanded\_terms" :  
> true,"enable\_position\_increments" : true,"fuzzy\_prefix\_length" :  
> 0,"fuzzy\_min\_sim" : 0.5,"phrase\_slop" : 0,"boost" : 1.0 } }, "from" : 0,  
> "size" : 0, "facets" : {"tag\_reviewstatus" : { "terms" : { "field"  
> :"\_reviewstatus","size" : 10 } } , "global" : false }, "explain" : false }'
> 
> Once I pass this request in CURL I am getting ParseException as  
> SEARCHPHASEEXECUTIONEXCEPTION.  
> Kindly help. Thanks in advance
> 
> ## -SRR
> 
> View this message in context:  
> [http://elasticsearch-users.115913.n3.nabble.com/Search-using-speical-characater-tp1867290p1867290.html](http://elasticsearch-users.115913.n3.nabble.com/Search-using-speical-characater-tp1867290p1867290.html)  
> Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com).

---

<div class="post-metadata">

**Author:** ![srrin](https://avatars.discourse-cdn.com/v4/letter/s/85f322/32.png) [@srrin](https://discuss.elastic.co/u/srrin)\
**Post date:** [November 10, 2010, 11:04am UTC](https://discuss.elastic.co/t/search-using-speical-characater/3539/3 "2010-11-10T11:04:46Z")

</div>

Hi Kimchy,  
Thanks for getting back to me.

pagecount:[2 TO 4] or pagecount:{2 TO 4} is working fine there is no issue. As I explained mixing curly and square bracket the issue.

-SRR

---

<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:** [November 12, 2010, 10:36pm UTC](https://discuss.elastic.co/t/search-using-speical-characater/3539/4 "2010-11-12T22:36:05Z")

</div>

Support for mixing curl and square brackets will be supported in the next  
version of Lucene (as far as I can tell). You can use the explicit range  
query definition (defined within the search body of a search request) to  
specify different inclusion of upper and lower bounds.

-shay.banon

On Wed, Nov 10, 2010 at 1:04 PM, srrIN [srrranga@gmail.com](mailto:srrranga@gmail.com) wrote:

> Hi Kimchy,  
> Thanks for getting back to me.
> 
> pagecount:[2 TO 4] or pagecount:{2 TO 4} is working fine there is no issue.  
> As I explained mixing curly and square bracket the issue.
> 
> ## -SRR
> 
> View this message in context:  
> [http://elasticsearch-users.115913.n3.nabble.com/Search-using-speical-characater-tp1867290p1875312.html](http://elasticsearch-users.115913.n3.nabble.com/Search-using-speical-characater-tp1867290p1875312.html)  
> Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com).

---

<div class="post-metadata">

**Author:** ![srrin](https://avatars.discourse-cdn.com/v4/letter/s/85f322/32.png) [@srrin](https://discuss.elastic.co/u/srrin)\
**Post date:** [November 13, 2010, 3:37am UTC](https://discuss.elastic.co/t/search-using-speical-characater/3539/5 "2010-11-13T03:37:01Z")

</div>

Hi shay.banon  
Thank you for getting back.

Currently I m using query dsl with inclusion and exclusion, since I m unable to find a solution for mixing braces. So mixing the braces in next version will be added advantage and looking for the next release.

Thank you.  
-SRR

---

<div class="post-metadata">

**Author:** ![Woland](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/woland/32/101616_2.png) [@Woland](https://discuss.elastic.co/u/Woland)\
**Post date:** [March 23, 2012, 9:01pm UTC](https://discuss.elastic.co/t/search-using-speical-characater/3539/6 "2012-03-23T21:01:34Z")

</div>

The mixed range query is already supported by the latest lucene. When do you expect ElasticSearch to support that?

Thanks.

---

<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:** [March 27, 2012, 6:45pm UTC](https://discuss.elastic.co/t/search-using-speical-characater/3539/7 "2012-03-27T18:45:17Z")

</div>

What do you mean by mixed range query? You mean the range query parser  
syntax?

On Fri, Mar 23, 2012 at 11:01 PM, Woland [sasha.la@gmail.com](mailto:sasha.la@gmail.com) wrote:

> The mixed range query is already supported by the latest lucene. When do  
> you  
> expect Elasticsearch to support that?
> 
> Thanks.
> 
> --  
> View this message in context:  
> [http://elasticsearch-users.115913.n3.nabble.com/Search-using-speical-characater-tp1867290p3852781.html](http://elasticsearch-users.115913.n3.nabble.com/Search-using-speical-characater-tp1867290p3852781.html)  
> Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com).

---

<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:34am UTC](https://discuss.elastic.co/t/search-using-speical-characater/3539/8 "2017-07-06T03:34:33Z")

</div>


