I would separate the performance issue from the logical structure of your domain. You really need to thing in terms of numbers of documents and shards (and not indices).
You may want to look into using index aliases, which can take a filter. That way you can have one index and several branch aliases with a filter. Or alternatively you can have one index per branch and then a company alias that includes all branch indexes. That way you can do company wide searches. It all depends on what you need. Jilles On Tuesday, April 8, 2014 11:58:17 AM UTC+2, Marcio Rodrigues wrote: > > Still new to ES, so I was wondering what would be the best approach. > > Say you have for example a company with different branhes throughout the > country and their documents will be stored centrally, but need to be > searched sepperately. > > Would it be better to create one index for all documents and use filters > on the queries or better to make a sepperate index for each branch? > > By better I mean most efficient in terms of performance a resource usage. > -- 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/4c77e453-20c2-40aa-88da-20086cd096fa%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
