lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Busch (JIRA)" <>
Subject [jira] Commented: (LUCENE-834) Payload Queries
Date Tue, 17 Apr 2007 22:13:15 GMT


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);

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:
>             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 for
some background information and 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:
For additional commands, e-mail:

View raw message