I'm working with a cluster that has 20 or so indices whose types are pretty
different from each other in the details, but have a couple of
commonalities across them. The application has "advanced search" forms that
are specific to each index and have a lot of filters on various fields.
Now I need to make a "global search" that's a simple text match without
changing the way that the advanced forms make their queries, minimizing
duplication of data, while getting good relevancy results.
At one time, I proposed a single multi-type index, but that's a lot of
duplication and adds quite an ETL burden. Right now, I'm considering adding
"copy_to" to the mappings to copy the specialized fields into consistently
named ones so that I can do a multi-index search that at least produces
similar result objects, but there's still duplication there (if there were
an "alias_to", I might be able to avoid that... but I'm sure that would add
Another option is to have the application do that alias-mapping/unmapping,
but that would make queries enormous, add complexity to result rendering,
and perhaps worst: would make it almost impossible to figure out how
scoring works (at least, that's what I've argued to anyone who's suggested
it). I'd love to hear some more informed opinions though.
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 firstname.lastname@example.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/55973bfa-59a9-41bd-b24f-a0d69de707ed%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.