[jira] [Commented] (SOLR-11679) TraveValueSource & trace() parser

["Hoss Man (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-11679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16267080#comment-16267080 ] 

Hoss Man commented on SOLR-11679:
---------------------------------

Blog post that inspired this: https://lucidworks.com/2017/11/27/caching-and-filters-and-post-filters/

(the writing of which led me to the optimization in SOLR-11641)

> 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
>         Attachments: SOLR-11679.patch
>
>
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org