public class NonPhrasingSearcher extends Searcher
Detects and removes certain phrases from the query.
Modifier and Type | Field and Description |
---|---|
private PhraseMatcher |
phraseMatcher |
private static com.yahoo.processing.request.CompoundName |
suggestonly |
Constructor and Description |
---|
NonPhrasingSearcher(com.yahoo.component.ComponentId id,
com.yahoo.container.QrSearchersConfig config) |
NonPhrasingSearcher(String phraseAutomatonFile)
Creates a nonphrasing searcher
|
Modifier and Type | Method and Description |
---|---|
private void |
remove(List<PhraseMatcher.Phrase> phrases) |
Result |
search(Query query,
Execution execution)
Override this to implement your searcher.
|
private void |
setupAutomatonFile(String phraseAutomatonFile) |
ensureFilled, fill, getLogger, process, toString
getAnnotatedDependencies, getDefaultAnnotatedDependencies, getDependencies, initDependencies
private static final com.yahoo.processing.request.CompoundName suggestonly
private PhraseMatcher phraseMatcher
public NonPhrasingSearcher(com.yahoo.component.ComponentId id, com.yahoo.container.QrSearchersConfig config)
public NonPhrasingSearcher(String phraseAutomatonFile)
phraseAutomatonFile
- the file containing phrases which should be removedIllegalStateException
- if the automata component is unavailable
in the current environmentIllegalArgumentException
- if the file is not foundprivate void setupAutomatonFile(String phraseAutomatonFile)
public Result search(Query query, Execution execution)
Searcher
Searcher implementation subclasses will, depending on their type of logic, do one of the following:
Hits come in two kinds - concrete hits are actual content of the kind requested by the user, meta hits are hits which provides information about the collection of hits, on the query, the service and so on.
The query specifies a window into a larger result list that must be returned from the searcher through hits and offset; Searchers which returns list of hits in the top level in the result must return at least hits number of hits (or if impossible; all that are available), starting at the given offset. In addition, searchers are allowed to return any number of meta hits (although this number is expected to be low). For hits contained in nested hit groups, the concept of a window defined by hits and offset is not well defined and does not apply.
Error handling in searchers:
private void remove(List<PhraseMatcher.Phrase> phrases)
Copyright © 2017. All rights reserved.