Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@lucene.apache.org
Message-ID: <55336048.1254940291302.JavaMail.jira@brutus>
Date: Wed, 7 Oct 2009 11:31:31 -0700 (PDT)
From: "Luis Alves (JIRA)" <jira@apache.org>
To: java-dev@lucene.apache.org
Subject: [jira] Commented: (LUCENE-1937) Add more methods to manipulate
 QueryNodeProcessorPipeline elements
In-Reply-To: <1852590773.1254417383596.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/LUCENE-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763176#action_12763176 ] 

Luis Alves commented on LUCENE-1937:
------------------------------------

Hi Adriano,

Wouldn't it be better for the pipeline to implement the "List" interface.
What do you think?

> Add more methods to manipulate QueryNodeProcessorPipeline elements
> ------------------------------------------------------------------
>
>                 Key: LUCENE-1937
>                 URL: https://issues.apache.org/jira/browse/LUCENE-1937
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: contrib/*
>    Affects Versions: 2.9
>            Reporter: Adriano Crestani
>            Assignee: Adriano Crestani
>            Priority: Minor
>             Fix For: 3.1
>
>         Attachments: LUCENE-1937.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: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org