Re: Advices on migrating 1.3.2 to 1.4.1

I upgraded our logging cluster to 1.4 without any problems. When I looked into upgrading a separate dev/test instance used for a different purpose I ran into problems with the plugins. If you are using plugins, make sure they are supported in 1.4. -- You received this message because you are

Re: Advices on migrating 1.3.2 to 1.4.1

Thank you for the advice 2014-12-04 9:30 GMT-02:00 Elvar Böðvarsson elv...@gmail.com: I upgraded our logging cluster to 1.4 without any problems. When I looked into upgrading a separate dev/test instance used for a different purpose I ran into problems with the plugins. If you are using

Re: Advices on migrating 1.3.2 to 1.4.1

Hi, 1.4 changed a lot of things, especially at the distributed system level, so testing it in your staging environment will certainly help ensure that things work as expected. Filtered aliases have been available for a long time (even before 1.4.0.beta1), it's very likely that they are already

Re: Advices on migrating 1.3.2 to 1.4.1

Thank you for your response Looks like I read it wrong in the documentation, only the Fields referred to in alias filters must exist in the mappings of the index/indices pointed to by the alias. part was included in the 1.4.0.beta1 Anyway, I found the terms lookup mechanism

Advices on migrating 1.3.2 to 1.4.1

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