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

Ivan Small commented on SOLR-2014:
----------------------------------

I wrote this patch for Zvents, a local search company.  The purpose behind 
cleaning up the parsing was to allow for more complex nested expressions.  
These were used in a couple of ways, but the most important was to simply cache 
the document boost in much the same was as a Lucene Field cache.  

About 80% of the queries for local search do not incorporate text.  It's mostly 
based on the 3-tuple [location, time, popularity].  This makes the boosting 
function very complicated and expensive, subsequently making caching absolutely 
required.  There are almost certainly other ways of doing this, but simply 
adding a nested function was the easiest and least invasive for me.  It did 
require that we improve the parsing.  Once in place, we found other uses for 
this nesting.  We used it for auditioning of new content.  This in essence 
boils down to modifying the document boost by some random element to give 
strong candidates a chance to generate popularity for themselves.  It's easy to 
implement by applying a function to the combined document boost score.

I'm not sure how this functionality would be supported by bq and LocalParams.  
An additional comment suggesting possible mechanisms would be great 
appreciated.   

> Allow BF parameter to accept complex nested expressions with whitespace 
> sprinkled throughout
> --------------------------------------------------------------------------------------------
>
>                 Key: SOLR-2014
>                 URL: https://issues.apache.org/jira/browse/SOLR-2014
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Ivan Small
>            Priority: Minor
>         Attachments: SOLR-2014.patch
>
>
> Modify the parsing of the boost function parameter (BF) to allow for 
> whitespace throughout.  This is useful for a couple of reasons.  The first is 
> more intuitive configuration, but the larger is to allow nested boost 
> functions.  By allowing for nesting of the boost function various forms of 
> caching, normalizing and other modification are possible.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to