Last Comment Bug 811300 - [research] Plan upgrade to ES 0.19.11
: [research] Plan upgrade to ES 0.19.11
u=dev c=search p=1 s=2012.22
Classification: Other
Component: Search (show other bugs)
: unspecified
: All All
: P1 normal (vote)
: 2012Q4
Assigned To: Ricky Rosario [:rrosario, :r1cky]
Depends on:
  Show dependency treegraph
Reported: 2012-11-13 07:29 PST by Ricky Rosario [:rrosario, :r1cky]
Modified: 2012-11-20 08:54 PST (History)
1 user (show)
See Also:
QA Whiteboard:
Iteration: ---
Points: ---


Description User image Ricky Rosario [:rrosario, :r1cky] 2012-11-13 07:29:17 PST
IT has set up a new ES cluster with the latest version of Elastic Search.

We believe there are some backwards incompatible changes that we have to deal with. This bug is about figuring out what they are and how to deal with them (file new bugs).
Comment 1 User image Ricky Rosario [:rrosario, :r1cky] 2012-11-20 06:14:53 PST
I am going to give ES latest a spin today.
Comment 2 User image Will Kahn-Greene [:willkg] 2012-11-20 06:21:51 PST
I look forward to your conclusions.... Hopefully there aren't any issues or the issues are in ElasticUtils and not in pyes.
Comment 3 User image Ricky Rosario [:rrosario, :r1cky] 2012-11-20 08:41:12 PST
Here is what I found:

ES v0.19.8
I've been using this version for local dev for a while and it works great for us.

ES v0.19.9
Running tests result in a bunch of: IndexMissingException: [_all] missing

ES v0.19.10
All tests pass.

ES v0.19.11
All tests pass. I also did a full reindex and everything looks good.

IT wants to put us on v0.19.11 and has a dev cluster ready for us. So I think we can proceed and try it out.
Comment 4 User image Ricky Rosario [:rrosario, :r1cky] 2012-11-20 08:44:23 PST
I am going to close this out. No followup bugs need to be filed at this point \o/
Comment 5 User image Will Kahn-Greene [:willkg] 2012-11-20 08:54:35 PST
Thank you so much for doing this! I'll add an issue to the elasticutils github issue tracker about checking whether it works with 0.19.9 and documenting issues.

Note You need to log in before you can comment on or make changes to this bug.