public class SemanticSearcher extends Searcher
Modifier and Type | Field and Description |
---|---|
private RuleBase |
defaultRuleBase
The default rule base of this
|
private Map<String,RuleBase> |
ruleBases
All rule bases of this (always including the default)
|
private static com.yahoo.processing.request.CompoundName |
rulesOff |
private static com.yahoo.processing.request.CompoundName |
rulesRulebase |
private static com.yahoo.processing.request.CompoundName |
tracelevelRules |
Constructor and Description |
---|
SemanticSearcher(List<RuleBase> ruleBases) |
SemanticSearcher(RuleBase... ruleBases) |
SemanticSearcher(RuleBase ruleBase)
Creates a semantic searcher using the given default rule base
|
SemanticSearcher(SemanticRulesConfig config) |
Modifier and Type | Method and Description |
---|---|
RuleBase |
getDefaultRuleBase()
Returns the default rule base
|
RuleBase |
getRuleBase(String ruleBaseName)
Returns the rule base of the given name, or null if none.
|
private Result |
handleError(RuleBase ruleBase,
Query query,
String error) |
private RuleBase |
resolveRuleBase(Query query) |
Result |
search(Query query,
Execution execution)
Override this to implement your searcher.
|
private static List<RuleBase> |
toList(SemanticRulesConfig config) |
ensureFilled, fill, getLogger, process, toString
getAnnotatedDependencies, getDefaultAnnotatedDependencies, getDependencies, initDependencies
private static final com.yahoo.processing.request.CompoundName rulesRulebase
private static final com.yahoo.processing.request.CompoundName rulesOff
private static final com.yahoo.processing.request.CompoundName tracelevelRules
private RuleBase defaultRuleBase
public SemanticSearcher(RuleBase ruleBase)
public SemanticSearcher(RuleBase... ruleBases)
@Inject public SemanticSearcher(SemanticRulesConfig config)
private static List<RuleBase> toList(SemanticRulesConfig config)
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:
public RuleBase getDefaultRuleBase()
Copyright © 2017. All rights reserved.