Class ForwardingSearcher
- java.lang.Object
-
- com.yahoo.component.AbstractComponent
-
- com.yahoo.component.chain.ChainedComponent
-
- com.yahoo.processing.Processor
-
- com.yahoo.search.Searcher
-
- com.yahoo.search.cluster.PingableSearcher
-
- com.yahoo.search.federation.ForwardingSearcher
-
- All Implemented Interfaces:
com.yahoo.component.Component
,java.lang.Comparable<com.yahoo.component.Component>
public class ForwardingSearcher extends PingableSearcher
A lightweight searcher to forward all incoming requests to a single search chain defined in config. An alternative to federation searcher when standard semantics are not necessary for the application.- Since:
- 5.0.13
- Author:
- Steinar Knutsen
- See Also:
FederationSearcher
-
-
Constructor Summary
Constructors Constructor Description ForwardingSearcher(SearchchainForwardConfig config)
-
Method Summary
All Methods Instance Methods Concrete Methods Modifier and Type Method Description void
fill(Result result, java.lang.String summaryClass, Execution execution)
Fill hit properties with data using the given summary class.Pong
ping(Ping ping, Execution execution)
Send a ping request downwards to probe if this searcher chain is in functioning orderResult
search(Query query, Execution execution)
Override this to implement your searcher.-
Methods inherited from class com.yahoo.search.Searcher
ensureFilled, getLogger, process, toString
-
Methods inherited from class com.yahoo.component.chain.ChainedComponent
getAnnotatedDependencies, getDefaultAnnotatedDependencies, getDependencies, initDependencies
-
-
-
-
Constructor Detail
-
ForwardingSearcher
public ForwardingSearcher(SearchchainForwardConfig config)
-
-
Method Detail
-
search
public Result search(Query query, Execution execution)
Description copied from class:Searcher
Override this to implement your searcher.Searcher implementation subclasses will, depending on their type of logic, do one of the following:
- Query processors: Access the query, then call execution.search and return the result
- Result processors: Call execution.search to get the result, access it and return
- Sources (which produces results): Create a result, add the desired hits and return it.
- Federators (which forwards the search to multiple subchains): Call search on the desired subchains in parallel and get the results. Combine the results to one and return it.
- Workflows: Call execution.search as many times as desired, using different queries. Eventually return a result.
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:
- Unexpected events: Throw any RuntimeException. This query will fail with the exception message, and the error will be logged
- Expected events: Create (new Result(Query, ErrorMessage) or add result.setErrorIfNoOtherErrors(ErrorMessage) an error message to the Result.
- Recoverable user errors: Add a FeedbackHit explaining the condition and how to correct it.
-
ping
public Pong ping(Ping ping, Execution execution)
Description copied from class:PingableSearcher
Send a ping request downwards to probe if this searcher chain is in functioning order- Overrides:
ping
in classPingableSearcher
-
fill
public void fill(Result result, java.lang.String summaryClass, Execution execution)
Description copied from class:Searcher
Fill hit properties with data using the given summary class. Calling this on already filled results has no cost.This needs to be overridden by federating searchers to contact search sources again by propagating the fill call down through the search chain, and by source searchers which talks to fill capable backends to request the data to be filled. Other searchers do not need to override this.
-
-