lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Miller <>
Subject Re: Lucene implementation/performance question
Date Thu, 20 Nov 2008 16:43:45 GMT
Yeah, discussion came up on order and I believe we punted - its up to 
you to track order and sort at the moment. I think that was to prevent 
those that didnt need it from paying the sort cost, but I have to go 
find that discussion again (maybe its in the issue?) I'll look at the 
whole idea again though.

Greg Shackles wrote:
> On Wed, Nov 19, 2008 at 12:33 PM, Greg Shackles <> wrote:
>> In the searching phase, I would run the search across all page documents,
>> and then for each of those pages, do a search with
>> PayloadSpanUtil.getPayloadsForQuery that made it so it only got payloads for
>> each page at a time.  The function returns a Collection of Payloads as far
>> as I can tell, so is there any way of knowing which payloads go together?
>> That is to say, if you were to do a search for "lucene rocks" on the page
>> and it appeared 3 times, you would get back 6 payloads in total.  Is there a
>> quick way of knowing how to group them in the collection?
> Just a follow-up on my post now that I was able to see what the real data
> looks like when it comes back from PayloadSpanUtil.  The order of payload
> terms in the collection doesn't seem useful, as I suspect it is somehow
> related to the order they are stored in the index itself.  Because of that,
> grouping them is going to be difficult as I suspected, but this seems like
> something Lucene should be able to do for me.  Is that not correct?  I'd
> like to keep as much of the logic as possible out of my own implementation
> for the sake of performance so if there is some way to do this, I would love
> to know.  Thanks!
> By the way, the Payloads feature is really cool! Definitely way better than
> how I was doing things originally.  : )
> - Greg

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message