Class TimingSearcher

  • All Implemented Interfaces:, java.lang.Comparable<>

    public class TimingSearcher
    extends PingableSearcher
    A searcher which is intended to be useful as a general probe for measuring time consumption a search chain.
    Steinar Knutsen
    • Field Summary

      • Fields inherited from class

    • Constructor Summary

      Constructor Description
      TimingSearcher​( id, TimingSearcherConfig config, manager)  
    • Method Summary

      All Methods Instance Methods Concrete Methods 
      Modifier and Type Method Description
      void deconstruct()  
      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 order
      Result search​(Query query, Execution execution)
      Override this to implement your searcher.
      void setMeasurements​( measurements)
      This method is only included for testing.
      • Methods inherited from class

        getAnnotatedDependencies, getDefaultAnnotatedDependencies, getDependencies, initDependencies
      • Methods inherited from class

        clone, compareTo, getClassName, getId, getIdString, hasInitializedId, initId, isDeconstructable, setIsDeconstructable
      • Methods inherited from class java.lang.Object

        equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait
    • Constructor Detail

      • TimingSearcher

        public TimingSearcher​( id,
                              TimingSearcherConfig config,
    • Method Detail

      • 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.

        fill in class Searcher
        result - the result to fill
        summaryClass - the name of the collection of fields to fetch the values of, or null to use the default
      • 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 and return the result
        • Result processors: Call 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 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.
        Specified by:
        search in class Searcher
        query - the query
        the result of making this query
      • setMeasurements

        public void setMeasurements​( measurements)
        This method is only included for testing.
      • deconstruct

        public void deconstruct()
        deconstruct in class