Package org.apache.lucene.queryParser.core.nodes

Contains query nodes that are commonly used by query parser implementations

See:
          Description

Interface Summary
FieldableNode A query node implements FieldableNode interface to indicate that its children and itself are associated to a specific field.
FieldValuePairQueryNode<T> This interface should be implemented by QueryNode that holds a field and an arbitrary value.
QueryNode A QueryNode is a interface implemented by all nodes on a QueryNode tree.
RangeQueryNode<T extends FieldValuePairQueryNode<?>> This interface should be implemented by a QueryNode that represents some kind of range query.
TextableQueryNode  
ValueQueryNode<T> This interface should be implemented by a QueryNode that holds an arbitrary value.
 

Class Summary
AndQueryNode A AndQueryNode represents an AND boolean operation performed on a list of nodes.
AnyQueryNode A AnyQueryNode represents an ANY operator performed on a list of nodes.
BooleanQueryNode A BooleanQueryNode represents a list of elements which do not have an explicit boolean operator defined between them.
BoostQueryNode A BoostQueryNode boosts the QueryNode tree which is under this node.
DeletedQueryNode A DeletedQueryNode represents a node that was deleted from the query node tree.
FieldQueryNode A FieldQueryNode represents a element that contains field/text tuple
FuzzyQueryNode A FuzzyQueryNode represents a element that contains field/text/similarity tuple
GroupQueryNode A GroupQueryNode represents a location where the original user typed real parenthesis on the query string.
MatchAllDocsQueryNode A MatchAllDocsQueryNode indicates that a query node tree or subtree will match all documents if executed in the index.
MatchNoDocsQueryNode A MatchNoDocsQueryNode indicates that a query node tree or subtree will not match any documents if executed in the index.
ModifierQueryNode A ModifierQueryNode indicates the modifier value (+,-,?,NONE) for each term on the query string.
NoTokenFoundQueryNode A NoTokenFoundQueryNode is used if a term is convert into no tokens by the tokenizer/lemmatizer/analyzer (null).
OpaqueQueryNode A OpaqueQueryNode is used for specify values that are not supposed to be parsed by the parser.
OrQueryNode A OrQueryNode represents an OR boolean operation performed on a list of nodes.
ParametricQueryNode Deprecated. this class will be removed in future.
ParametricRangeQueryNode A ParametricRangeQueryNode represents LE, LT, GE, GT, EQ, NE query.
PathQueryNode A PathQueryNode is used to store queries like /company/USA/California /product/shoes/brown.
PathQueryNode.QueryText  
PhraseSlopQueryNode  
ProximityQueryNode A ProximityQueryNode represents a query where the terms should meet specific distance conditions.
ProximityQueryNode.ProximityType  
QueryNodeImpl A QueryNodeImpl is the default implementation of the interface QueryNode
QuotedFieldQueryNode A QuotedFieldQueryNode represents phrase query.
SlopQueryNode A SlopQueryNode represents phrase query with a slop.
TokenizedPhraseQueryNode A TokenizedPhraseQueryNode represents a node created by a code that tokenizes/lemmatizes/analyzes.
 

Enum Summary
ModifierQueryNode.Modifier  
ParametricQueryNode.CompareOperator  
ProximityQueryNode.Type  
 

Package org.apache.lucene.queryParser.core.nodes Description

Contains query nodes that are commonly used by query parser implementations

Query Nodes

The package org.apache.lucene.queryParser.nodes contains all the basic query nodes. The interface that represents a query node is QueryNode. Every query node must be serializable.

QueryNodes are used by the text parser to create a syntax tree. These nodes are designed to be used by UI or other text parsers. The default Lucene text parser is StandardSyntaxParser, it implements Lucene's standard syntax.

QueryNode interface should be implemented by all query nodes, the class QueryNodeImpl implements QueryNode and is extended by all current query node implementations.

A query node tree can be printed to the a stream, and it generates a pseudo XML representation with all the nodes.

A query node tree can also generate a query string that can be parsed back by the original text parser, at this point only the standard lucene syntax is supported.

Grouping nodes:

Leaf Nodes:

Utility Nodes: