# Quering lots of small objects

**URL:** <https://discuss.elastic.co/t/quering-lots-of-small-objects/12284>\
**Category:** Elasticsearch\
**Created:** [June 5, 2013, 4:53pm UTC](https://discuss.elastic.co/t/quering-lots-of-small-objects/12284 "2013-06-05T16:53:47Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alexis\_Okuwa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexis_okuwa/32/1983_2.png) [@Alexis\_Okuwa](https://discuss.elastic.co/u/Alexis_Okuwa)\
**Post date:** [June 5, 2013, 4:53pm UTC](https://discuss.elastic.co/t/quering-lots-of-small-objects/12284/1 "2013-06-05T16:53:47Z")

</div>

Hello,

I have a use case where i have lots of small objects each being about  
500bytes. There are a lot of them being written and will need to get  
purged. I was wondering if I could setup a single index and type it by day.  
But then run the query on the index its self. So  
[http://localhost:9200/bigIndex/\_search](http://localhost:9200/bigIndex/_search). For search that i know which types  
i want to use will I be able to do  
[http://localhost:9200/bigIndex/type1,type2,type3/\_search](http://localhost:9200/bigIndex/type1,type2,type3/_search). I also wanted to  
know if it would be useful to use routing.

Lastly, I will be deleting these types on a daily base, each type will have  
over a million recoords, will the space get reused, And what are the draw  
backs to this.

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [June 6, 2013, 7:57am UTC](https://discuss.elastic.co/t/quering-lots-of-small-objects/12284/2 "2013-06-06T07:57:28Z")

</div>

Hey,

if you use different types, but put data in the same index, the purging of  
data will result in I/O intensive merge operations in order to keep the  
index small.  
If you use own indices instead, you can simply drop a whole index after a  
week or two, which is a really cheap operation. More about index aliases

> **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)**
>
> Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today.

Hope this helps, otherwise you might need to tell a bit more about your  
usecase.

--Alex

On Wed, Jun 5, 2013 at 6:53 PM, Alexis Okuwa [wojonstech@gmail.com](mailto:wojonstech@gmail.com) wrote:

> Hello,
> 
> I have a use case where i have lots of small objects each being about  
> 500bytes. There are a lot of them being written and will need to get  
> purged. I was wondering if I could setup a single index and type it by day.  
> But then run the query on the index its self. So  
> [http://localhost:9200/bigIndex/\_search](http://localhost:9200/bigIndex/_search). For search that i know which  
> types i want to use will I be able to do  
> [http://localhost:9200/bigIndex/type1,type2,type3/\_search](http://localhost:9200/bigIndex/type1,type2,type3/_search). I also wanted  
> to know if it would be useful to use routing.
> 
> Lastly, I will be deleting these types on a daily base, each type will  
> have over a million recoords, will the space get reused, And what are the  
> draw backs to this.
> 
> --  
> You received this message because you are subscribed to the Google Groups  
> "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Alexis\_Okuwa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexis_okuwa/32/1983_2.png) [@Alexis\_Okuwa](https://discuss.elastic.co/u/Alexis_Okuwa)\
**Post date:** [June 6, 2013, 8:02am UTC](https://discuss.elastic.co/t/quering-lots-of-small-objects/12284/3 "2013-06-06T08:02:30Z")

</div>

My use case are a few parts in a time series application i am building  
allows for a large amount of writes to come in. so for example for each  
processes running on a machine its one document that gets created, there is  
a comploent simular to google anyaltics and for each broswer page load they  
get it creates a doc, and then the user is also able to have some custom  
logging enabled, which will create docs on the services. I was going to  
create 1 index for each of these use cases, and then a type for daily, this  
is to keep the index mangment easier, data would present in its raw form  
for 30 to 90 days. which would mean a few hundred indexes if i did one  
index each.

On Thu, Jun 6, 2013 at 12:57 AM, Alexander Reelsen [alr@spinscale.de](mailto:alr@spinscale.de) wrote:

> Hey,
> 
> if you use different types, but put data in the same index, the purging of  
> data will result in I/O intensive merge operations in order to keep the  
> index small.  
> If you use own indices instead, you can simply drop a whole index after a  
> week or two, which is a really cheap operation. More about index aliases  
> [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/api/admin-indices-aliases/)
> 
> Hope this helps, otherwise you might need to tell a bit more about your  
> usecase.
> 
> --Alex
> 
> On Wed, Jun 5, 2013 at 6:53 PM, Alexis Okuwa [wojonstech@gmail.com](mailto:wojonstech@gmail.com) wrote:
> 
> > Hello,
> > 
> > I have a use case where i have lots of small objects each being about  
> > 500bytes. There are a lot of them being written and will need to get  
> > purged. I was wondering if I could setup a single index and type it by day.  
> > But then run the query on the index its self. So  
> > [http://localhost:9200/bigIndex/\_search](http://localhost:9200/bigIndex/_search). For search that i know which  
> > types i want to use will I be able to do  
> > [http://localhost:9200/bigIndex/type1,type2,type3/\_search](http://localhost:9200/bigIndex/type1,type2,type3/_search). I also wanted  
> > to know if it would be useful to use routing.
> > 
> > Lastly, I will be deleting these types on a daily base, each type will  
> > have over a million recoords, will the space get reused, And what are the  
> > draw backs to this.
> > 
> > --  
> > You received this message because you are subscribed to the Google Groups  
> > "elasticsearch" group.  
> > To unsubscribe from this group and stop receiving emails from it, send an  
> > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
> > 
> > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> 
> --  
> You received this message because you are subscribed to a topic in the  
> Google Groups "elasticsearch" group.  
> To unsubscribe from this topic, visit  
> [https://groups.google.com/d/topic/elasticsearch/HR1BBM\_\_yTw/unsubscribe?hl=en-US](https://groups.google.com/d/topic/elasticsearch/HR1BBM__yTw/unsubscribe?hl=en-US)  
> .  
> To unsubscribe from this group and all its topics, send an email to  
> [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
Enjoy,  
Alexis Okuwa  
WojonsTech  
424.835.1223

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<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:** [June 7, 2013, 10:54am UTC](https://discuss.elastic.co/t/quering-lots-of-small-objects/12284/4 "2013-06-07T10:54:01Z")

</div>

types within an index are not designed to be used to separate time base data, in that case, you should have a single type and use timestamp to do ranges. Index per time range is an amazingly powerful design for time base data, as t doesn't suffer the cost of deletes...

On Thu, Jun 6, 2013 at 10:02 AM, Alexis Okuwa [wojonstech@gmail.com](mailto:wojonstech@gmail.com)  
wrote:

> My use case are a few parts in a time series application i am building  
> allows for a large amount of writes to come in. so for example for each  
> processes running on a machine its one document that gets created, there is  
> a comploent simular to google anyaltics and for each broswer page load they  
> get it creates a doc, and then the user is also able to have some custom  
> logging enabled, which will create docs on the services. I was going to  
> create 1 index for each of these use cases, and then a type for daily, this  
> is to keep the index mangment easier, data would present in its raw form  
> for 30 to 90 days. which would mean a few hundred indexes if i did one  
> index each.  
> On Thu, Jun 6, 2013 at 12:57 AM, Alexander Reelsen [alr@spinscale.de](mailto:alr@spinscale.de) wrote:
> 
> > Hey,
> > 
> > if you use different types, but put data in the same index, the purging of  
> > data will result in I/O intensive merge operations in order to keep the  
> > index small.  
> > If you use own indices instead, you can simply drop a whole index after a  
> > week or two, which is a really cheap operation. More about index aliases  
> > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/api/admin-indices-aliases/)
> > 
> > Hope this helps, otherwise you might need to tell a bit more about your  
> > usecase.
> > 
> > --Alex
> > 
> > On Wed, Jun 5, 2013 at 6:53 PM, Alexis Okuwa [wojonstech@gmail.com](mailto:wojonstech@gmail.com) wrote:
> > 
> > > Hello,
> > > 
> > > I have a use case where i have lots of small objects each being about  
> > > 500bytes. There are a lot of them being written and will need to get  
> > > purged. I was wondering if I could setup a single index and type it by day.  
> > > But then run the query on the index its self. So  
> > > [http://localhost:9200/bigIndex/\_search](http://localhost:9200/bigIndex/_search). For search that i know which  
> > > types i want to use will I be able to do  
> > > [http://localhost:9200/bigIndex/type1,type2,type3/\_search](http://localhost:9200/bigIndex/type1,type2,type3/_search). I also wanted  
> > > to know if it would be useful to use routing.
> > > 
> > > Lastly, I will be deleting these types on a daily base, each type will  
> > > have over a million recoords, will the space get reused, And what are the  
> > > draw backs to this.
> > > 
> > > --  
> > > You received this message because you are subscribed to the Google Groups  
> > > "elasticsearch" group.  
> > > To unsubscribe from this group and stop receiving emails from it, send an  
> > > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
> > > 
> > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > 
> > --  
> > You received this message because you are subscribed to a topic in the  
> > Google Groups "elasticsearch" group.  
> > To unsubscribe from this topic, visit  
> > [https://groups.google.com/d/topic/elasticsearch/HR1BBM\_\_yTw/unsubscribe?hl=en-US](https://groups.google.com/d/topic/elasticsearch/HR1BBM__yTw/unsubscribe?hl=en-US)  
> > .  
> > To unsubscribe from this group and all its topics, send an email to  
> > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> 
> ## -- Enjoy, Alexis Okuwa WojonsTech 424.835.1223
> 
> You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Alexis\_Okuwa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexis_okuwa/32/1983_2.png) [@Alexis\_Okuwa](https://discuss.elastic.co/u/Alexis_Okuwa)\
**Post date:** [June 8, 2013, 7:56am UTC](https://discuss.elastic.co/t/quering-lots-of-small-objects/12284/5 "2013-06-08T07:56:31Z")

</div>

Is there anyway to make sure indexes with a simular name always have the  
same mapping?

On Fri, Jun 7, 2013 at 3:54 AM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote:

> types within an index are not designed to be used to separate time base  
> data, in that case, you should have a single type and use timestamp to do  
> ranges. Index per time range is an amazingly powerful design for time base  
> data, as t doesn't suffer the cost of deletes...
> 
> On Thu, Jun 6, 2013 at 10:02 AM, Alexis Okuwa [wojonstech@gmail.com](mailto:wojonstech@gmail.com)wrote:
> 
> > My use case are a few parts in a time series application i am building  
> > allows for a large amount of writes to come in. so for example for each  
> > processes running on a machine its one document that gets created, there is  
> > a comploent simular to google anyaltics and for each broswer page load they  
> > get it creates a doc, and then the user is also able to have some custom  
> > logging enabled, which will create docs on the services. I was going to  
> > create 1 index for each of these use cases, and then a type for daily, this  
> > is to keep the index mangment easier, data would present in its raw form  
> > for 30 to 90 days. which would mean a few hundred indexes if i did one  
> > index each.
> > 
> > On Thu, Jun 6, 2013 at 12:57 AM, Alexander Reelsen [alr@spinscale.de](mailto:alr@spinscale.de)wrote:
> > 
> > > Hey,
> > > 
> > > if you use different types, but put data in the same index, the purging  
> > > of data will result in I/O intensive merge operations in order to keep the  
> > > index small.  
> > > If you use own indices instead, you can simply drop a whole index after  
> > > a week or two, which is a really cheap operation. More about index aliases  
> > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/api/admin-indices-aliases/)
> > > 
> > > Hope this helps, otherwise you might need to tell a bit more about your  
> > > usecase.
> > > 
> > > --Alex
> > > 
> > > On Wed, Jun 5, 2013 at 6:53 PM, Alexis Okuwa [wojonstech@gmail.com](mailto:wojonstech@gmail.com)wrote:
> > > 
> > > > Hello,
> > > > 
> > > > I have a use case where i have lots of small objects each being about  
> > > > 500bytes. There are a lot of them being written and will need to get  
> > > > purged. I was wondering if I could setup a single index and type it by day.  
> > > > But then run the query on the index its self. So  
> > > > [http://localhost:9200/bigIndex/\_search](http://localhost:9200/bigIndex/_search). For search that i know which  
> > > > types i want to use will I be able to do  
> > > > [http://localhost:9200/bigIndex/type1,type2,type3/\_search](http://localhost:9200/bigIndex/type1,type2,type3/_search). I also  
> > > > wanted to know if it would be useful to use routing.
> > > > 
> > > > Lastly, I will be deleting these types on a daily base, each type will  
> > > > have over a million recoords, will the space get reused, And what are the  
> > > > draw backs to this.
> > > > 
> > > > --  
> > > > You received this message because you are subscribed to the Google  
> > > > Groups "elasticsearch" group.  
> > > > To unsubscribe from this group and stop receiving emails from it, send  
> > > > an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
> > > > 
> > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > > 
> > > --  
> > > You received this message because you are subscribed to a topic in the  
> > > Google Groups "elasticsearch" group.  
> > > To unsubscribe from this topic, visit  
> > > [https://groups.google.com/d/topic/elasticsearch/HR1BBM\_\_yTw/unsubscribe?hl=en-US](https://groups.google.com/d/topic/elasticsearch/HR1BBM__yTw/unsubscribe?hl=en-US)  
> > > .  
> > > To unsubscribe from this group and all its topics, send an email to  
> > > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > 
> > --  
> > Enjoy,  
> > Alexis Okuwa  
> > WojonsTech  
> > 424.835.1223
> > 
> > --  
> > You received this message because you are subscribed to the Google Groups  
> > "elasticsearch" group.  
> > To unsubscribe from this group and stop receiving emails from it, send an  
> > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> 
> --  
> You received this message because you are subscribed to a topic in the  
> Google Groups "elasticsearch" group.  
> To unsubscribe from this topic, visit  
> [https://groups.google.com/d/topic/elasticsearch/HR1BBM\_\_yTw/unsubscribe?hl=en-US](https://groups.google.com/d/topic/elasticsearch/HR1BBM__yTw/unsubscribe?hl=en-US)  
> .  
> To unsubscribe from this group and all its topics, send an email to  
> [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
Enjoy,  
Alexis Okuwa  
WojonsTech  
424.835.1223

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [June 8, 2013, 11:39am UTC](https://discuss.elastic.co/t/quering-lots-of-small-objects/12284/6 "2013-06-08T11:39:35Z")

</div>

Hey,

check index templates, see

> **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)**
>
> Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today.

--Alex

On Sat, Jun 8, 2013 at 9:56 AM, Alexis Okuwa [wojonstech@gmail.com](mailto:wojonstech@gmail.com) wrote:

> Is there anyway to make sure indexes with a simular name always have the  
> same mapping?
> 
> On Fri, Jun 7, 2013 at 3:54 AM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote:
> 
> > types within an index are not designed to be used to separate time base  
> > data, in that case, you should have a single type and use timestamp to do  
> > ranges. Index per time range is an amazingly powerful design for time base  
> > data, as t doesn't suffer the cost of deletes...
> > 
> > On Thu, Jun 6, 2013 at 10:02 AM, Alexis Okuwa [wojonstech@gmail.com](mailto:wojonstech@gmail.com)wrote:
> > 
> > > My use case are a few parts in a time series application i am building  
> > > allows for a large amount of writes to come in. so for example for each  
> > > processes running on a machine its one document that gets created, there is  
> > > a comploent simular to google anyaltics and for each broswer page load they  
> > > get it creates a doc, and then the user is also able to have some custom  
> > > logging enabled, which will create docs on the services. I was going to  
> > > create 1 index for each of these use cases, and then a type for daily, this  
> > > is to keep the index mangment easier, data would present in its raw form  
> > > for 30 to 90 days. which would mean a few hundred indexes if i did one  
> > > index each.
> > > 
> > > On Thu, Jun 6, 2013 at 12:57 AM, Alexander Reelsen [alr@spinscale.de](mailto:alr@spinscale.de)wrote:
> > > 
> > > > Hey,
> > > > 
> > > > if you use different types, but put data in the same index, the purging  
> > > > of data will result in I/O intensive merge operations in order to keep the  
> > > > index small.  
> > > > If you use own indices instead, you can simply drop a whole index after  
> > > > a week or two, which is a really cheap operation. More about index aliases  
> > > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/api/admin-indices-aliases/)
> > > > 
> > > > Hope this helps, otherwise you might need to tell a bit more about your  
> > > > usecase.
> > > > 
> > > > --Alex
> > > > 
> > > > On Wed, Jun 5, 2013 at 6:53 PM, Alexis Okuwa [wojonstech@gmail.com](mailto:wojonstech@gmail.com)wrote:
> > > > 
> > > > > Hello,
> > > > > 
> > > > > I have a use case where i have lots of small objects each being about  
> > > > > 500bytes. There are a lot of them being written and will need to get  
> > > > > purged. I was wondering if I could setup a single index and type it by day.  
> > > > > But then run the query on the index its self. So  
> > > > > [http://localhost:9200/bigIndex/\_search](http://localhost:9200/bigIndex/_search). For search that i know which  
> > > > > types i want to use will I be able to do  
> > > > > [http://localhost:9200/bigIndex/type1,type2,type3/\_search](http://localhost:9200/bigIndex/type1,type2,type3/_search). I also  
> > > > > wanted to know if it would be useful to use routing.
> > > > > 
> > > > > Lastly, I will be deleting these types on a daily base, each type will  
> > > > > have over a million recoords, will the space get reused, And what are the  
> > > > > draw backs to this.
> > > > > 
> > > > > --  
> > > > > You received this message because you are subscribed to the Google  
> > > > > Groups "elasticsearch" group.  
> > > > > To unsubscribe from this group and stop receiving emails from it, send  
> > > > > an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
> > > > > 
> > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > > > 
> > > > --  
> > > > You received this message because you are subscribed to a topic in the  
> > > > Google Groups "elasticsearch" group.  
> > > > To unsubscribe from this topic, visit  
> > > > [https://groups.google.com/d/topic/elasticsearch/HR1BBM\_\_yTw/unsubscribe?hl=en-US](https://groups.google.com/d/topic/elasticsearch/HR1BBM__yTw/unsubscribe?hl=en-US)  
> > > > .  
> > > > To unsubscribe from this group and all its topics, send an email to  
> > > > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > > 
> > > --  
> > > Enjoy,  
> > > Alexis Okuwa  
> > > WojonsTech  
> > > 424.835.1223
> > > 
> > > --  
> > > You received this message because you are subscribed to the Google  
> > > Groups "elasticsearch" group.  
> > > To unsubscribe from this group and stop receiving emails from it, send  
> > > an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > 
> > --  
> > You received this message because you are subscribed to a topic in the  
> > Google Groups "elasticsearch" group.  
> > To unsubscribe from this topic, visit  
> > [https://groups.google.com/d/topic/elasticsearch/HR1BBM\_\_yTw/unsubscribe?hl=en-US](https://groups.google.com/d/topic/elasticsearch/HR1BBM__yTw/unsubscribe?hl=en-US)  
> > .  
> > To unsubscribe from this group and all its topics, send an email to  
> > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> 
> --  
> Enjoy,  
> Alexis Okuwa  
> WojonsTech  
> 424.835.1223
> 
> --  
> You received this message because you are subscribed to the Google Groups  
> "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<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, 2:32am UTC](https://discuss.elastic.co/t/quering-lots-of-small-objects/12284/7 "2017-07-06T02:32:13Z")

</div>


