It's an internal abstract class intended to finalize ase a query processing after query parsing.
This type of query is not actually involved into query execution.
| category | Zend |
|---|---|
| package | Zend_Search_Lucene |
| subpackage | Search |
| internal | |
| copyright | Copyright (c) 2005-2015 Zend Technologies USA Inc. (http://www.zend.com) |
| license | New BSD License |
| inherited_from | \Zend_Search_Lucene_Search_Query_Preprocessing |
__construct(string $phrase, string $phraseEncoding, string $fieldName)
stringPhrase to search.
stringPhrase encoding.
stringField name.
__toString() : string
string__toString() : string
stringcreateWeight(\Zend_Search_Lucene_Interface $reader) : \Zend_Search_Lucene_Search_Weight
\Zend_Search_Lucene_Interface
\Zend_Search_Lucene_Search_Weightexecute(\Zend_Search_Lucene_Interface $reader, \Zend_Search_Lucene_Index_DocsFilter|null $docsFilter = null)
Query specific implementation
\Zend_Search_Lucene_Interface
\Zend_Search_Lucene_Index_DocsFilternull
getBoost() : float
floatgetQueryTerms() : array
arraygetSlop() : integer
integerhighlightMatches(string $inputHTML, string $defaultEncoding = '', \Zend_Search_Lucene_Search_Highlighter_Interface|null $highlighter = null) : string
string
stringHTML encoding, is used if it's not specified using Content-type HTTP-EQUIV meta tag.
\Zend_Search_Lucene_Search_Highlighter_Interfacenull
stringhtmlFragmentHighlightMatches(string $inputHtmlFragment, string $encoding= 'UTF-8', \Zend_Search_Lucene_Search_Highlighter_Interface|null $highlighter= null) : string
string
stringInput HTML string encoding
\Zend_Search_Lucene_Search_Highlighter_Interfacenull
stringmatchedDocs() : array
It's an array with document ids as keys (performance considerations)
arrayoptimize(\Zend_Search_Lucene_Interface $index) : \Zend_Search_Lucene_Search_Query
\Zend_Search_Lucene_Interface
\Zend_Search_Lucene_Search_Queryreset()
rewrite(\Zend_Search_Lucene_Interface $index) : \Zend_Search_Lucene_Search_Query
\Zend_Search_Lucene_Interface
\Zend_Search_Lucene_Search_Queryrewrite(\Zend_Search_Lucene_Interface $index) : \Zend_Search_Lucene_Search_Query
\Zend_Search_Lucene_Interface
\Zend_Search_Lucene_Search_Queryscore(integer $docId, \Zend_Search_Lucene_Interface $reader) : float
integer
\Zend_Search_Lucene_Interface
floatsetBoost(float $boost)
float
setSlop(integer $slop)
integer
_highlightMatches(\Zend_Search_Lucene_Search_Highlighter_Interface $highlighter)
\Zend_Search_Lucene_Search_Highlighter_InterfaceHighlighter object (also contains doc for highlighting)
_highlightMatches(\Zend_Search_Lucene_Search_Highlighter_Interface $highlighter)
\Zend_Search_Lucene_Search_Highlighter_InterfaceHighlighter object (also contains doc for highlighting)
_initWeight(\Zend_Search_Lucene_Interface $reader)
\Zend_Search_Lucene_Interface
$_matches : array
nullMatched terms list. It's filled during rewrite operation and may be used for search result highlighting
Array of Zend_Search_Lucene_Index_Term objects
$_weight : \Zend_Search_Lucene_Search_Weight
null$_boost : float
1$_currentColorIndex : integer
0$_field : string
$_phrase : string
$_phraseEncoding : string
$_slop : integer
If zero, then this is an exact phrase search. For larger values this works like a WITHIN or NEAR operator.
The slop is in fact an edit-distance, where the units correspond to moves of terms in the query phrase out of position. For example, to switch the order of two words requires two moves (the first move places the words atop one another), so to permit re-orderings of phrases, the slop must be at least two. More exact matches are scored higher than sloppier matches, thus search results are sorted by exactness.
The slop is zero by default, requiring exact matches.