|Resolved||mmodell||T146789 Phab Advanced Search no longer showing typical results|
|Resolved||jcrespo||T146673 Contention on search phabricator database creating full phabricator outages|
|Resolved||mmodell||T146843 Re-evaluate how we implement phabricator's search engine|
|Resolved||mmodell||T151500 Collect test cases for phabricator search|
|Resolved||debt||T151324 [epic] System level upgrade for cirrus / elasticsearch|
|Resolved||Deskana||T154501 [Epic, Q3 Goal] Upgrade search systems to Elasticsearch 5|
|Resolved||EBernhardson||T157479 Put together a production migration plan for ES 2 -> ES 5|
|Resolved||mmodell||T155299 Phabricator: Support elasticsearch 5.x|
The Search Team does not have responsibility for search in Phabricator, and we aren't planning on doing anything there. Despite this task's claims, I doubt that our upgrade of search for the Wikimedia wikis would affect search on Phabricator at all because I don't think they're linked to each other in any form; someone can correct me if I'm wrong. I'm not really sure what this task is about.
Actually, I'm getting this warnning
2017-01-26T19:16:11,892][WARN ][o.e.d.i.m.StringFieldMapper$TypeParser] The [string] field is deprecated, please use [text] or [keyword] instead on [cmnt]
Elasticsearch index Incorrect
Either the Phabricator schema for Elasticsearch has changed or Elasticsearch created the index automatically. Run ./bin/search init to correct the index.
@Deskana: We are evaluating the possibility of moving phabricator's search over to the wikimedia elasticsearch cluster in the future. If we want to be able to do that then phabricator's elasticsearch backend needs to track the version of elastic that we're running on the wikimedia cluster.