public class PageTemplateSearcher extends Searcher
Input query properties:
page.idList- a List<String> of id strings of the page templates this should choose between
page.id- a space-separated string of ids of the page templates this should choose between. This property is ignored if
page.resolverthe id of the resolver to use to resolve choices. This is either the component id of a deployed resolver component, or one of the strings
native.deterministic(which always pics the last choice) or
page.ListOfPageTemplateA List<PageTemplate> containing a list of the page templates used for this query
The set of page templates chosen for the query specifies a list of sources to be queries (the page template sources). In addition, the query may contain
IntentModel(the intent model sources)
|Modifier and Type||Field and Description|
The name of the query property containing a list of candidate pages to consider
The name of the query property containing the page id to use
The name of the query property containing the resolved candidate page template list
The name of the query property containing the resolver id to use
|Constructor and Description|
Creates this from an existing page template registry, using only built-in resolvers
Creates this from a configuration.
|Modifier and Type||Method and Description|
Override this to implement your searcher.
ensureFilled, fill, getLogger, process, toString
getAnnotatedDependencies, getDefaultAnnotatedDependencies, getDependencies, initDependencies
clone, compareTo, deconstruct, getClassName, getId, getIdString, hasInitializedId, initId, isDeconstructable, setIsDeconstructable
public static final com.yahoo.processing.request.CompoundName pagePageTemplateListName
public static final com.yahoo.processing.request.CompoundName pageIdListName
public static final com.yahoo.processing.request.CompoundName pageIdName
public static final com.yahoo.processing.request.CompoundName pageResolverName
@Inject public PageTemplateSearcher(PageTemplatesConfig pageTemplatesConfig, com.yahoo.component.provider.ComponentRegistry<Resolver> resolverRegistry)
public PageTemplateSearcher(PageTemplateRegistry templateRegistry, Resolver... resolvers)
templateRegistry- the page template registry. This will be frozen by this call.
resolvers- the resolvers to use, in addition to the default resolvers
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.