# Explaining the execution plan

**URL:** <https://discuss.elastic.co/t/explaining-the-execution-plan/5208>\
**Category:** Elasticsearch\
**Created:** [August 20, 2011, 5:16pm UTC](https://discuss.elastic.co/t/explaining-the-execution-plan/5208 "2011-08-20T17:16:30Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![mfeingold](https://avatars.discourse-cdn.com/v4/letter/m/ecb155/32.png) [@mfeingold](https://discuss.elastic.co/u/mfeingold)\
**Post date:** [August 20, 2011, 5:16pm UTC](https://discuss.elastic.co/t/explaining-the-execution-plan/5208/1 "2011-08-20T17:16:30Z")

</div>

Is there a way to understand how the query will be executed -  
something similar to the explain feature in SQL? As explained in the  
manual explain flag on the query only covers the score computation

---

<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:** [August 22, 2011, 6:41pm UTC](https://discuss.elastic.co/t/explaining-the-execution-plan/5208/2 "2011-08-22T18:41:08Z")

</div>

Explain flag is as detailed as it goes. What else are you missing?

On Sat, Aug 20, 2011 at 8:16 PM, Michael Feingold [mfeingold@hill30.com](mailto:mfeingold@hill30.com)wrote:

> Is there a way to understand how the query will be executed -  
> something similar to the explain feature in SQL? As explained in the  
> manual explain flag on the query only covers the score computation

---

<div class="post-metadata">

**Author:** ![mfeingold](https://avatars.discourse-cdn.com/v4/letter/m/ecb155/32.png) [@mfeingold](https://discuss.elastic.co/u/mfeingold)\
**Post date:** [August 29, 2011, 4:12pm UTC](https://discuss.elastic.co/t/explaining-the-execution-plan/5208/3 "2011-08-29T16:12:27Z")

</div>

What I am looking for is a way to get some understanding as to what  
makes my query slow and may be some hints about how to make it  
faster.

Something similar to what is available for SQL - for a query if a  
proper index is missing it would tell you that table scan was used, so  
it becomes clear that adding an index will speed it up - may be.

I am not sure how much (if any) of this stuff can be applied here, but  
I am certainly missing it.

On Aug 22, 1:41 pm, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote:

> Explain flag is as detailed as it goes. What else are you missing?
> 
> On Sat, Aug 20, 2011 at 8:16 PM, Michael Feingold [mfeing...@hill30.com](mailto:mfeing...@hill30.com)wrote:
> 
> > Is there a way to understand how the query will be executed -  
> > something similar to the explain feature in SQL? As explained in the  
> > manual explain flag on the query only covers the score computation

---

<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:** [August 29, 2011, 5:33pm UTC](https://discuss.elastic.co/t/explaining-the-execution-plan/5208/4 "2011-08-29T17:33:37Z")

</div>

I see, yea, that can be interesting. Need to think a bit on how something  
like that can be recorded and then exposed.

On Mon, Aug 29, 2011 at 7:12 PM, Michael Feingold [mfeingold@hill30.com](mailto:mfeingold@hill30.com)wrote:

> What I am looking for is a way to get some understanding as to what  
> makes my query slow and may be some hints about how to make it  
> faster.
> 
> Something similar to what is available for SQL - for a query if a  
> proper index is missing it would tell you that table scan was used, so  
> it becomes clear that adding an index will speed it up - may be.
> 
> I am not sure how much (if any) of this stuff can be applied here, but  
> I am certainly missing it.
> 
> On Aug 22, 1:41 pm, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote:
> 
> > Explain flag is as detailed as it goes. What else are you missing?
> > 
> > On Sat, Aug 20, 2011 at 8:16 PM, Michael Feingold \<[mfeing...@hill30.com](mailto:mfeing...@hill30.com)  
> > wrote:
> > 
> > > Is there a way to understand how the query will be executed -  
> > > something similar to the explain feature in SQL? As explained in the  
> > > manual explain flag on the query only covers the score computation

---

<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:55am UTC](https://discuss.elastic.co/t/explaining-the-execution-plan/5208/5 "2017-07-06T03:55:42Z")

</div>


