Re: Inserting a document into an index at a specified position

2006-07-07 Thread Jason Calabrese
We only display the 10 hits at a time, so we don't need to iterate through all the hits. It feels like there should be a way to pull a document out 1 index and stick it into an other and bring all the unstored fields along with it. On Friday 07 July 2006 12:52, Erick Erickson wrote: > Did you

Re: Inserting a document into an index at a specified position

2006-07-07 Thread Erick Erickson
Did you use a Hits object to assemble your results? And is that what you're measuring when you say it's slow? In other words, were you measuring the time it took to execute the statement Hits hits = searcher.search(query, new Sort("fullname")); or the time it took to iterate over the Hits object

Re: Inserting a document into an index at a specified position

2006-07-07 Thread Jason Calabrese
> When you say you keep your documents ordered alphabetically, it's confusing > to me. Are you saying that you pre-sort all your documents then insert them > one after another so that automatically-generated internal Lucene ID maps > exactly to the alphabetical ordering? That is, for any document I

Re: Inserting a document into an index at a specified position

2006-07-07 Thread Erick Erickson
When you say you keep your documents ordered alphabetically, it's confusing to me. Are you saying that you pre-sort all your documents then insert them one after another so that automatically-generated internal Lucene ID maps exactly to the alphabetical ordering? That is, for any document IDs D1 a

Re: Inserting a document into an index at a specified position

2006-07-07 Thread Jason Calabrese
All, I sent this the other day, but didn't get any responses. I'm hoping that it was just missed, so I'm trying again. There has to be a better way to to insert a document in to an index then reindexing everything. --Jason On Wednesday 05 July 2006 5:06 pm, Jason Calabrese wrote: > All, > >