Hello We currently have a cluster with 50 millions of docs using ElasticSearch version 1.3.2
We were looking for something like a persisted filter, and the filtered aliases, added in version 1.4.0.beta1, seems perfect for it Our infrastructure team is not happy to upgrading it in production without doing a lot of tests before, so we have to do a lot of tests and upgrade later We are looking for some advices in what can go wrong with this upgrade, what are the risks? And also, is there a way to implement a "persistent filter" in our current version? I mean, some of our users will have access to a part of our data, we need something like a database view. We could send a filter in every request, but that would be too slow with, let's say, 10 millions of ids. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAJp2533WXXhA4hAd4qBPWa0ZUZGBPUFQ0V4Tv_u7p2OuyCChoA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
