public class GroupingValidator extends Searcher
GroupingRequest
objects attached to a Query
makes sense to the search
cluster for which this searcher has been deployed. This searcher uses exceptions to signal invalid grouping
requests.Modifier and Type | Class and Description |
---|---|
private class |
GroupingValidator.MyVisitor |
Modifier and Type | Field and Description |
---|---|
private Set<String> |
attributeNames |
private String |
clusterName |
private boolean |
enabled |
static String |
GROUPING_VALIDATED |
static com.yahoo.processing.request.CompoundName |
PARAM_ENABLED |
Constructor and Description |
---|
GroupingValidator(com.yahoo.container.QrSearchersConfig qrsConfig,
ClusterConfig clusterConfig,
com.yahoo.vespa.config.search.AttributesConfig attributesConfig)
Constructs a new instance of this searcher with the given component id and config.
|
Modifier and Type | Method and Description |
---|---|
Result |
search(Query query,
Execution execution)
Override this to implement your searcher.
|
ensureFilled, fill, getLogger, process, toString
getAnnotatedDependencies, getDefaultAnnotatedDependencies, getDependencies, initDependencies
public static final String GROUPING_VALIDATED
public static final com.yahoo.processing.request.CompoundName PARAM_ENABLED
private final String clusterName
private final boolean enabled
@Inject public GroupingValidator(com.yahoo.container.QrSearchersConfig qrsConfig, ClusterConfig clusterConfig, com.yahoo.vespa.config.search.AttributesConfig attributesConfig)
qrsConfig
- The shared config for all searchers.clusterConfig
- The config for the cluster that this searcher is deployed for.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:
Copyright © 2018. All rights reserved.