Details

    • Type: Sub-task
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      The same basic idea as the sibling pivot issue: ask the RangeFacet code to compute some stats X for each range it generates. We can do this with the existing stats.field params, but we'll leverage the tag local param of the stats.field instances to be able to associate which stats we want hanging off of which facet.range instance

      Example...

      facet.range={!stats=s1}timestamp
      facet.range={!stats=s2}bytes_sent
      stats.field={!key=sum_bytes tag=s1 sum=true}bytes_sent
      stats.field={!tag=s1 percentiles=99}request_duration
      stats.field={!tag=s2 mean=true percentiles=99}request_duration
      

      ...with the request above, (hypothetically over an index of web log traffic) each range bucket over the "timestamp" field will (in addition to simple facet count) also include the sum of total bytes_sent, and the 99th percentile of request_duration for all docs in that time range; and each range bucket over the "bytes_sent" field will (in addition to simple facet count) also include the mean and 99th percentile of request_duration.

        Attachments

        1. SOLR-6352.patch
          15 kB
          Shalin Shekhar Mangar

          Issue Links

            Activity

              People

              • Assignee:
                shalinmangar Shalin Shekhar Mangar
                Reporter:
                hossman Hoss Man
              • Votes:
                5 Vote for this issue
                Watchers:
                9 Start watching this issue

                Dates

                • Created:
                  Updated: