lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Grant Ingersoll <grant.ingers...@gmail.com>
Subject Re: [jira] Commented: (LUCENE-834) Payload Queries
Date Fri, 20 Apr 2007 14:25:15 GMT

On Apr 17, 2007, at 6:13 PM, Michael Busch (JIRA) wrote:

>
>     [ https://issues.apache.org/jira/browse/LUCENE-834? 
> page=com.atlassian.jira.plugin.system.issuetabpanels:comment- 
> tabpanel#action_12489562 ]
>
> Michael Busch commented on LUCENE-834:
> --------------------------------------
>
> Yes, I was mainly thinking about large documents. I think in  
> general memory consumption during search should depend on query  
> complexity, not on the actual index.
> Besides, I don't see much benefits in gathering all payloads up  
> front and processing them thereafter (maybe I overlook some?). What  
> about having a method in BoostingTermScorer like:
>
> protected float calculateTermBoost(TermPostions tp);
>

Because this is also a SpanQuery (which, it doesn't have to be) going  
this route would mean a double loop over the positions.

How about an array of floats that contains the scores for each  
payload and is filled in by an overridden, but similar version of  
setFreqCurrentDoc() (from SpanScorer)

Then, in the score method, we can add another callback to similarity  
that passes in this array of floats, with the default implementation  
averaging them.  The other option is just average them in the  
SpanScorer and derived classes can override setFreqCurrentDoc() and/ 
or score() if they want a different scheme.





> which implements averaging per default but can be overwritten by  
> subclasses? An optimized implementation might e. g. consider just  
> to read the first x% position payloads for large docs and estimate  
> the boost for performance reasons.
>
>> Payload Queries
>> ---------------
>>
>>                 Key: LUCENE-834
>>                 URL: https://issues.apache.org/jira/browse/LUCENE-834
>>             Project: Lucene - Java
>>          Issue Type: New Feature
>>          Components: Search
>>            Reporter: Grant Ingersoll
>>         Assigned To: Grant Ingersoll
>>            Priority: Minor
>>         Attachments: boosting.term.query.patch
>>
>>
>> Now that payloads have been implemented, it will be good to make  
>> them searchable via one or more Query mechanisms.  See http:// 
>> wiki.apache.org/lucene-java/Payload_Planning for some background  
>> information and https://issues.apache.org/jira/browse/LUCENE-755  
>> for the issue that started it all.
>
> -- 
> 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: java-dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-dev-help@lucene.apache.org
>

------------------------------------------------------
Grant Ingersoll
http://www.grantingersoll.com/
http://lucene.grantingersoll.com
http://www.paperoftheweek.com/



---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message