To follow up on this... As a general rule is it better to have one horse size index or a hundred duck sized indices. I am thinking about those types of searches where you might frequently search a subset of the data. For example keeping a separate index for every customer because normally the app restricts itself to only dealing with one customer at a time. Perhaps doing a compound split based on customer and year if your searches rarely go outside of the current year.
Thanks. On Wednesday, April 23, 2014 4:07:58 PM UTC+12, Mark Walkom wrote: > > 1 and 2 - It'd probably be easiest to try this yourself :) > 3 - not really, you should look into routing. > 4 - only the index metadata is stored in memory. However doing > aggregations will pull the applicable data into memory. > 5 - not sure. > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: [email protected] <javascript:> > web: www.campaignmonitor.com > > > On 23 April 2014 13:04, Mohannad Saeed <[email protected] <javascript:>>wrote: > >> Any experienced dude with ES to answer 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 [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/3e238739-2928-4aed-9883-094452bc6c11%40googlegroups.com >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/28d1e12a-a381-4921-b13e-83640767e281%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
