lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] Resolved: (LUCENE-1937) Add more methods to manipulate QueryNodeProcessorPipeline elements
Date Tue, 19 Oct 2010 20:49:27 GMT


Robert Muir resolved LUCENE-1937.

    Resolution: Fixed

Committed revisions 1024402, 1024405 (3x).

Thanks Adriano! I'll look at LUCENE-1938 now

> Add more methods to manipulate QueryNodeProcessorPipeline elements
> ------------------------------------------------------------------
>                 Key: LUCENE-1937
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: contrib/*
>    Affects Versions: 2.9
>            Reporter: Adriano Crestani
>            Assignee: Robert Muir
>            Priority: Minor
>             Fix For: 3.1, 4.0
>         Attachments: LUCENE-1937.patch, LUCENE-1937.patch, LUCENE-1937_10_13_2009.patch
> 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".

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message