Thanks Hoss. I understand the dynamic nature of doc-IDs. All that I care about is the most recent docs be at the top of the hit list when there is a tie. From your reply, it is not clear if that's what happens. If not, then I have to sort, but this is something I want to avoid so it won't add cost to my queries (CPU and RAM).
Can you help me answer those two questions? Steve On Mon, Aug 24, 2015 at 2:16 PM, Chris Hostetter <hossman_luc...@fucit.org> wrote: > > : A follow up question. Is the sub-sorting on the lucene internal doc IDs > : ascending or descending order? That is, do the most recently index doc > > you can not make any generic assumptions baout hte order of the internal > lucene doc IDS -- the secondary sort on the internal IDs is stable (and > FWIW: ascending) for static indexes, but as mentioned before: the *actual* > order hte the IDS changes as the index changes -- if there is an index > merge, the ids can be totally different and docs can be re-arranged into a > diff order... > > : > However, internal Lucene Ids can change when index changes. (merges, > : > updates etc). > > ... > > : show up first in this set of docs that have tied score? If not, who can > I > : have the most recent be first? Do I have to sort on lucene's internal > doc > > add a "timestamp" or "counter" field when you index your documents that > means whatevery you want it to mean (order added, order updated, order > according to some external sort criteria from some external system) and > then do an explicit sort on that. > > > -Hoss > http://www.lucidworks.com/ >
