Lucene - Core
  1. Lucene - Core
  2. LUCENE-5155

Add OrdinalValueResolver in favor of FacetRequest.getValueOf


    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.5, master
    • Component/s: modules/facet
    • Labels:
    • Lucene Fields:
      New, Patch Available


      FacetRequest.getValueOf is responsible for resolving an ordinal's value. It is given FacetArrays, and typically does something like arrays.getIntArray()[ord] – for every ordinal! The purpose of this method is to allow special requests, e.g. average, to do some post processing on the values, that couldn't be done during aggregation.

      I feel that getValueOf is in the wrong place – the calls to getInt/FloatArray are really redundant. Also, if an aggregator maintains some statistics by which it needs to "correct" the aggregated values, it's not trivial to pass it from the aggregator to the request.

      Therefore I would like to make the following changes:

      • Remove FacetRequest.getValueOf and .getFacetArraysSource
      • Add FacetsAggregator.createOrdinalValueResolver which takes the FacetArrays and has a simple API .valueOf(ordinal).
      • Modify the FacetResultHandlers to use OrdValResolver.

      This allows an OVR to initialize the right array instance(s) in the ctor, and return the value of the requested ordinal, without doing arrays.getArray() calls.

      Will post a patch shortly.


        No work has yet been logged on this issue.


          • Assignee:
            Shai Erera
            Shai Erera
          • Votes:
            0 Vote for this issue
            3 Start watching this issue


            • Created: