# I'm looking for a grammar/parser for elasticsearch query\_string

**URL:** <https://discuss.elastic.co/t/im-looking-for-a-grammar-parser-for-elasticsearch-query-string/188283>\
**Category:** Elasticsearch\
**Created:** [July 1, 2019, 10:16am UTC](https://discuss.elastic.co/t/im-looking-for-a-grammar-parser-for-elasticsearch-query-string/188283 "2019-07-01T10:16:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dave\_Hangman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dave_hangman/32/45057_2.png) [@Dave\_Hangman](https://discuss.elastic.co/u/Dave_Hangman)\
**Post date:** [July 1, 2019, 10:16am UTC](https://discuss.elastic.co/t/im-looking-for-a-grammar-parser-for-elasticsearch-query-string/188283/1 "2019-07-01T10:16:49Z")

</div>

What I'm trying to achieve is to generate a valid elasticsearch [query\_string](https://www.elastic.co/guide/en/elasticsearch/reference/6.7/query-dsl-query-string-query.html) form inputs preferably in frontend.  
In worst case it can be generated in the backend (nodeJS, NestJS).  
I'm looking for libraries which can generate the query\_string mentioned above and parse it back so I can add more criterias to the search without string concatenation i.e. `queryString += 'OR (big apple)'`.  
I already found a [post](https://groups.google.com/forum/#!topic/pegjs/x4Zh_phvunk) which already proves that the query\_string is forwarded to Lucene (inside of Elasticsearch source code), so Lucene compatible query\_string might be acceptable.

---

<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 29, 2019, 10:16am UTC](https://discuss.elastic.co/t/im-looking-for-a-grammar-parser-for-elasticsearch-query-string/188283/2 "2019-07-29T10:16:53Z")

</div>

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