Thanks Erick.
Your summary about doc IDs is much helpful.
I tested the second level sort with a small set of data (10K records) and
didn't see much of a significant impact. I will test with a 10m records at
some time later.
Steve
On Mon, Aug 24, 2015 at 11:03 PM, Erick Erickson
wrote:
> Gett
Getting the most recent doc first in the case of a tie
will _not_ "just happen". I don't think you really get the
nuance here...
You index doc1, and doc2 later. Let's
claim that doc1 gets internal Lucene doc ID of 1 and
doc2 gets an internal doc ID of 2. So far you're golden.
Let's further claim t
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 c
: 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
F
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
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
IDs?
Thanks Ahmet.
Steve
On Mon, Aug 24, 2015 at 10:09 AM, Ahmet Arslan
wrote:
> Hi Steven,
>
> When scores produce a tie, internal Lucene document IDs are used to break
> it.
> However, internal Lucene Ids can change when index changes. (merges,
> updates etc).
>
> You can see those values with [do
Hi Steven,
Here is the relevant Jira ticket :
https://issues.apache.org/jira/browse/LUCENE-6057
Ahmet
On Monday, August 24, 2015 5:09 PM, Ahmet Arslan
wrote:
Hi Steven,
When scores produce a tie, internal Lucene document IDs are used to break it.
However, internal Lucene Ids can change when
Hi Steven,
When scores produce a tie, internal Lucene document IDs are used to break it.
However, internal Lucene Ids can change when index changes. (merges, updates
etc).
You can see those values with [docid] - DocIdAugmenterFactory.
If you want 100% stable sorting, use a second sorting criter
Hi Everyone,
When I search for a term in Solr, and it happens that 10 doc end up with
the same score, what's the order of doc ranking in the set of those 10
equally scored doc and what is it based on? Is there a link I can read
more about this?
Thanks,
Steve
