To replace query_string you need to re-implement its core query language parser and lucene query generation code. This task is to do just that. Plus any extensions we implement on the cirrus side like regex queries, specialized field queries.
Note that we don't expect to be perfect on the first pass: the goal of this task is to get far enough the we plausibly believe we can start integrating it with
See parent task for benefits and stakeholders.
Estimate: Weeks.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | PRODUCTION ERROR | None | T94814 Fix: "Warning: Search backend error during .. took .." (tracking) | ||
| Duplicate | PRODUCTION ERROR | None | T90775 support OR between intitle: operators | ||
| Duplicate | None | T98873 [epic] CirrusSearch: Abandon query_string | |||
| Declined | None | T99261 Implement query_string_plus_plus_plus query parsing |
@Manybubbles Please add some more context and information to this task. It's fairly incomprehensible right now, which makes it hard to prioritise.
Replaced the description. For reference this is mostly done except for regex queries which I'm working on now and some hardening around random roll you face on the keyboard style queries.
Its an integral part of its parent task - really the first part.