Hoss Man created SOLR-11679:
-------------------------------
Summary: TraveValueSource & trace() parser
Key: SOLR-11679
URL: https://issues.apache.org/jira/browse/SOLR-11679
Project: Solr
Issue Type: Improvement
Security Level: Public (Default Security Level. Issues are Public)
Reporter: Hoss Man
Assignee: Hoss Man
Priority: Trivial
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.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
