[SOLR-11679] TraveValueSource & trace() parser

• Type: Improvement
• Status: Resolved
• Priority: Trivial
• Resolution: Won't Do
• Assignee: Chris M. Hostetter
• Reporter: Chris M. Hostetter
• Created: 27/Nov/17 17:04
• Updated: 08/Jun/19 15:16
• Resolved: 27/Nov/17 17:13

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.

Issue Links

• relates to: SOLR-11641 {!frange} / FunctionRangeQuery should default to 100==getCost() so non-cached fq's default to post-filtering