lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Grant Ingersoll (JIRA)" <>
Subject [jira] Commented: (LUCENE-834) Payload Queries
Date Sat, 17 Mar 2007 23:03:09 GMT


Grant Ingersoll commented on LUCENE-834:

I should add, one open question is how big the array in the BoostingSpanScorer should be preallocated
to.  I set it to 256, but I would imagine it could be smaller???? but I'm not sure.  Probably
should be configurable, but I didn't go that route.  I would think, for practical purposes,
that payloads should be kept small for the most part, otherwise performance will most likely
suffer.  What do others think?  Have you seen papers/applications where the engine is storing
large amounts of data on a per term basis?

I could see where it might be useful to write VInts, etc. to the payload.  Perhaps a refactoring
of some of the writing/reading methods to allow for usage of them may be useful.  Just thinking
out loud...

> 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