# First thoughts on ES|QL

**URL:** https://discuss.elastic.co/t/first-thoughts-on-es-ql/347607
**Category:** Kibana
**Created:** [November 21, 2023, 9:26am UTC](https://discuss.elastic.co/t/first-thoughts-on-es-ql/347607 "2023-11-21T09:26:35Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Wolfram\_Haussig](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wolfram_haussig/32/70528_2.png) [@Wolfram\_Haussig](https://discuss.elastic.co/u/Wolfram_Haussig)
#### Post date: [November 21, 2023, 9:26am UTC](https://discuss.elastic.co/t/first-thoughts-on-es-ql/347607/1 "2023-11-21T09:26:35Z")

</div>

Dear all,

We are currently trying out the new ES|QL query language and as far as I have used it it is a great improvement! The flexibility and the relatively easy grammar will surely make this my preferred language in the stack.

Of course, there is always room for improvement, so here are a few things I would like to change:

1. Timeouts  
I tried ES|QL in Discover and the query always timed out after 30 seconds - independent of the `Search Timeout` setting in the advanced settings. ES|QL should either adhere to the search timeout settings or get a separate configurable timeout.
2. Link to the ES|QL reference  
The link to the ES|QL reference on the right side of the query window of discover is not as intuitive as I would like (but maybe this is personal preference?).  
Compact version:  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/0/f/0ff899f8b579ef546ad8ea01798b39dcf181b7d8.png)  
Expanded Version:  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/9/5/950ab55d73615d9e24d778e531ea0c8943b1e33a.png)  
Personally, I would prefer a place where it is nearer to the query code:  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/3/0/30f17486cf3d8629fd502020dfc91e81ef95dd57.png)
3. False Syntax errors  
While elasticsearch does not seem to care about case sensitivity, Kibana does not like some uppercase keywords. For example: `| STATS cnt = count(_id) BY service.name` causes Kibana to show the error:

> mismatched input 'BY' expecting {, PIPE, 'by', 'and', COMMA, 'or', '+', '-', '\*', '/', '%'}

1. Show Chart  
The option to create a chart directly in Discover using ES|QL is great but it is too hidden:  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/d/9/d9b20715011a57734fa6e53334e36b05778ecd8d.png)  
Similar to the ES|QL reference, I would like a direkt and easily accessible way to show/hide the chart:  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/c/8/c8b25f5abad86f90f8a7c15ec826351521732ac7.png)

Best regards  
Wolfram

---

<div class="post-metadata">

### Author: ![carly.richmond](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carly.richmond/32/104935_2.png) [@carly.richmond](https://discuss.elastic.co/u/carly.richmond)
#### Post date: [November 21, 2023, 10:01am UTC](https://discuss.elastic.co/t/first-thoughts-on-es-ql/347607/2 "2023-11-21T10:01:48Z")

</div>

Hi @Wolfram_Haussig,

Thanks so much for sharing your feedback. We greatly appreciate it. I'll circulate this internally with the team.

Thanks again!

---

<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: [December 19, 2023, 10:02am UTC](https://discuss.elastic.co/t/first-thoughts-on-es-ql/347607/3 "2023-12-19T10:02:30Z")

</div>

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