[LUCENE-1937] Add more methods to manipulate QueryNodeProcessorPipeline elements

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.9
• Fix Version/s: 3.1, 4.0-ALPHA
• Component/s: modules/other
• Lucene Fields: New
• Assignee: Robert Muir
• Reporter: Adriano Crestani
• Created: 01/Oct/09 17:15
• Updated: 28/Aug/22 12:10
• Resolved: 19/Oct/10 20:47

Description

QueryNodeProcessorPipeline allows the user to define a list of processors to process a query tree. However, it's not very flexible when the user wants to extend/modify an already created pipeline, because it only provides an add method, which only allows the user to append a new processor to the pipeline.

So, I propose to add new methods to manipulate the processor in a pipeline. I think the methods should not consider an index position when modifying the pipeline, hence the index position in a pipeline does not mean anything, a processor has a meaning when it's after or before another processor. Therefore, I suggest the methods should always consider another processor when inserting/modifying the pipeline. For example, insertAfter(processor, newProcessor), which will insert the "newProcessor" after the "processor".

Issue Links

• blocks: LUCENE-1938 Precedence query parser using the contrib/queryparser framework