Page MenuHomePhabricator

Fix a bad call in ElasticSearch recovery code
ClosedPublic

Authored by epriestley on Feb 17 2014, 6:54 PM.
Tags
None
Referenced Files
F18803321: D8260.diff
Fri, Oct 17, 10:44 PM
F18756907: D8260.id19648.diff
Sun, Oct 5, 2:21 PM
F18689754: D8260.id19648.diff
Fri, Sep 26, 6:28 PM
F18652016: D8260.diff
Sep 21 2025, 6:20 AM
F18651419: D8260.diff
Sep 21 2025, 4:21 AM
F18624892: D8260.diff
Sep 15 2025, 9:21 PM
F18624888: D8260.diff
Sep 15 2025, 9:21 PM
F18621755: D8260.diff
Sep 15 2025, 9:20 AM
Subscribers

Details

Summary

Ref T4446. Some discussion in IRC. Prior to hitting the 1.0.0 issue, we hit and resolved this issue; this is a leftover call from bringing ApplicationSearch to main search.

Test Plan

User confirmed this fixes the issue.

Diff Detail

Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

I have the same issue:
[HTTP/400]
{"error":"SearchPhaseExecutionException[Failed to execute phase [query], all shards failed; shardFailures {[C7G7eJy3SJSiyL_YyrpkiQ][phabricator][2]: SearchParseException[[phabricator][2]: from[-1],size[-1]: Parse Failure [Failed to parse source [{\"query\":{\"bool\":{\"must\":[{\"field\":{\"field.corpus\":\"vg\"}}]}},\"from\":0,\"size\":101}]]]; nested: QueryParsingException[[phabricator] No query registered for [field]]; }{[C7G7eJy3SJSiyL_YyrpkiQ][phabricator][1]: SearchParseException[[phabricator][1]: fro...

phabricator version:
commit cd080b092e20352e43bc947a4fa2f43b306ca036
Date: Wed Feb 26 11:18:06 2014 -0800

elasticsearch version: 1.0.1

See T4446.

Workaround is to downgrade to 0.9.4 until we have a chance to look at that.

downgrade to 0.90.10 works fine, thanks