Not sure what the desired end result is here, but you shouldn't need to update the document jut to give it a boost factor. This can be done in the query string used to search the index.
As for updating affecting search order, I don't think you can assume any guarantees in this regard. You're probably better off sorting the results manually. The simplest solution would be to add a timestamp to each document when it's created (milliseconds since epoch for example), then sort by that. This will have an impact on speed, but in my experience it's marginal. On 8/28/06, AlexeyG <[EMAIL PROTECTED]> wrote:
Is there a way to update a document in the Index without causing any change to the order in which it comes up in searches? I have a bunch of search results being returned as a result of a query. This is done in order to allow users to "request boost" - they have a drop-down box with options slight/average/high boost to select from for every search result. Selecting an option results in a field being added to the document called "BOOST_REQUEST", which is alter used to review requets and add boost. The problem is, the document gets overwritten when users request boost. This results in that document automaticallty jumping to the end of search results that have the same score. Is there a way to update a document in the Index without causing any change to the order in which it comes up in searches? Thank You. -- View this message in context: http://www.nabble.com/Lucene-displaying-results-in-the-order-they-were-added-tf2173858.html#a6011016 Sent from the Lucene - Java Users forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
