Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-11679

TraveValueSource & trace() parser

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Trivial
    • Resolution: Won't Do
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      I whiped up a little TraceValueSource and trave() function parser to help demonstrate how/when the ValueSource API was used by the FunctionRangeQParser for the purposes of a blog post i'm about to publish.

      Essentially it just writes a log message with some tracing details everytime one of the FunctionValue methods (ie: exists, intVal, floatVal, etc...) are called, so that when used from FunctionRangeQParser you can see how things like cost and post-filtering impact things.

      I don't think there is a lot of value in committing the code as is – it would be dangerously verbose on non trivial indexes – but i wanted to put the patch in jira in case it inspires anyone with a more interesting idea.

        Attachments

        1. SOLR-11679.patch
          9 kB
          Chris M. Hostetter

          Issue Links

            Activity

              People

              • Assignee:
                hossman Chris M. Hostetter
                Reporter:
                hossman Chris M. Hostetter
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: