public class PosSearcher extends Searcher
Modifier and Type | Field and Description |
---|---|
static double |
km2deg |
static double |
mi2deg |
private static com.yahoo.processing.request.CompoundName |
posAttributeName |
private static com.yahoo.processing.request.CompoundName |
posBb |
static String |
POSITION_PARSING |
private static com.yahoo.processing.request.CompoundName |
posLl |
private static com.yahoo.processing.request.CompoundName |
posRadius |
private static com.yahoo.processing.request.CompoundName |
posUnits |
private static com.yahoo.processing.request.CompoundName |
posXy |
Constructor and Description |
---|
PosSearcher() |
Modifier and Type | Method and Description |
---|---|
private void |
handleGeoCircle(Query query,
String ll,
Location target) |
private void |
handleXyCircle(Query query,
String xy,
Location target) |
private static void |
parseBoundingBox(String bb,
Location target) |
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 POSITION_PARSING
private static final com.yahoo.processing.request.CompoundName posBb
private static final com.yahoo.processing.request.CompoundName posLl
private static final com.yahoo.processing.request.CompoundName posXy
private static final com.yahoo.processing.request.CompoundName posAttributeName
private static final com.yahoo.processing.request.CompoundName posRadius
private static final com.yahoo.processing.request.CompoundName posUnits
public static final double km2deg
public static final double mi2deg
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.