Sometimes, people have to search accross multiple enterprise applications. Each application write in a given index and can manage many type of documents.
So it's more a convenient way to separate things. Have one index per type in some cases could be strange if you indexed only a few docs. That said, if you can have one single type per index, I think it's better. You will avoid collisions between fields within the same index. I mean a field X can belong to type1 and another field X to type2. But you could imagine different rules for each (one is a String, the other a Date). Here you can start having some troubles. My 2 cents. David > Le 12 déc. 2014 à 20:43, fye <[email protected]> a écrit : > > Gurus, > > would you shed some lights for a newbie. What is the top benefits of adding > the level of 'type' beyond one level Lucene index? What are the top use cases > that requires multiple types (schemas) within one index? > > thanks! > -- > 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/e99e4a35-4ee9-42b1-b619-63225cd315f5%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/60AEC1A7-487D-4465-8C01-E1E9BFB64F41%40pilato.fr. For more options, visit https://groups.google.com/d/optout.
