Page MenuHomePhabricator

Implement query_string_plus_plus_plus query parsing
Closed, DeclinedPublic


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.

Related Objects

Event Timeline

Manybubbles claimed this task.
Manybubbles raised the priority of this task from to Medium.
Manybubbles updated the task description. (Show Details)
Deskana added a subscriber: Deskana.EditedJun 2 2015, 2:44 PM

@Manybubbles Please add some more context and information to this task. It's fairly incomprehensible right now, which makes it hard to prioritise.

Manybubbles set Security to None.

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.

demon removed a subscriber: demon.Aug 19 2015, 4:43 PM
ksmith added a subscriber: ksmith.

@Deskana: Not clear to me why @Manybubbles moved this to "done".

@Deskana: Not clear to me why @Manybubbles moved this to "done".

Indeed. Let's bump this to the backlog then.

Deskana removed Manybubbles as the assignee of this task.Dec 3 2015, 4:55 AM
Deskana lowered the priority of this task from Medium to Lowest.Feb 26 2016, 7:04 PM

Changing priority here to reflect reality.

Deskana moved this task from Needs triage to Search on the Discovery board.Feb 26 2016, 7:04 PM
dcausse closed this task as Declined.Jul 31 2018, 6:56 PM
dcausse added a subscriber: dcausse.

this will happen in cirrus, not as an elasticsearch plugin