After we've upgraded ES to 1.7.5 we should upgrade ruflin/elastica to 2.3.1
https://github.com/ruflin/Elastica/releases/tag/2.3.1
https://github.com/ruflin/Elastica/compare/2.2.1...2.3.1
Description
Description
Details
Details
| Project | Branch | Lines +/- | Subject | |
|---|---|---|---|---|
| mediawiki/extensions/Elastica | master | +1 -1 | Bump Elastica requirement to 2.3.1 | |
| mediawiki/extensions/CirrusSearch | master | +10 -1 | Support for Elastica 2.3.1 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Deskana | T125603 EPIC: Review current ElasticSearch configuration, and use relevance lab to run tests to optimise the configuration to improve search result relevance | |||
| Resolved | dcausse | T107006 Add a "reverse" suggestion field to workaround the prefix length limitation (typos suggestion) | |||
| Duplicate | None | T122698 Upgrade ElasticSearch to version >=2.2 | |||
| Resolved | Gehel | T122697 Upgrade ElasticSearch to 1.7.5 | |||
| Resolved | EBernhardson | T127831 Upgrade ruflin/elastica to 2.3.1 |
Event Timeline
Comment Actions
Looks like it's a breaking change...
cause the query to fail, not sure to understand why they added this hack but this breaks our query :(
Comment Actions
Change 279997 had a related patch set uploaded (by EBernhardson):
Support for Elastica 2.3.1
Comment Actions
Change 279998 had a related patch set uploaded (by EBernhardson):
Bump Elastica requirement to 2.3.1
Comment Actions
Tested with the above two patches and things look to be working, or at least it passes the browser test suite and I couldn't come up with anything odd while testing manually.
Comment Actions
Let me know if you want me to rebase/reapply https://gerrit.wikimedia.org/r/#/c/260159/