See: Description
| Interface | Description | 
|---|---|
| QueryNodeProcessor | A  QueryNodeProcessoris an interface for classes that process aQueryNodetree. | 
| Class | Description | 
|---|---|
| NoChildOptimizationQueryNodeProcessor | 
 A  NoChildOptimizationQueryNodeProcessorremoves every
 BooleanQueryNode, BoostQueryNode, TokenizedPhraseQueryNode or
 ModifierQueryNode that do not have a valid children. | 
| QueryNodeProcessorImpl | 
 This is a default implementation for the  QueryNodeProcessorinterface, it's an abstract class, so it should be extended by classes that
 want to process aQueryNodetree. | 
| QueryNodeProcessorPipeline | A  QueryNodeProcessorPipelineclass should be used to build a query
 node processor pipeline. | 
| RemoveDeletedQueryNodesProcessor | A  QueryNodeProcessorPipelineclass removes every instance ofDeletedQueryNodefrom a query node tree. | 
The package org.apache.lucene.queryParser.processors contains interfaces that should be implemented by every query node processor.
 The interface that every query node processor should implement is QueryNodeProcessor.
 A query node processor should be used to process a QueryNode tree.
 QueryNode trees can be programmatically created or generated by a
 text parser. See org.apache.lucene.queryparser.flexible.core.parser for more details about text parsers.
 
 A query node processor should be used to process a QueryNode tree.
 QueryNode trees can be programmatically created or generated by a
 text parser. See org.apache.lucene.queryparser.flexible.core.parser for more details about text parsers.
 
 A pipeline of processors can be assembled using QueryNodeProcessorPipeline.
 
 Implementors may want to extend QueryNodeProcessorImpl, which simplifies
 the implementation, because it walks automatically the QueryNode. See
 QueryNodeProcessorImpl for more details.
Copyright © 2000-2017 Apache Software Foundation. All Rights Reserved.