It's even worse. It may change. The internal tiebreaker is the
internal Lucene doc ID,
which may change one against another as segments are merged. So docA may
sort < docB for a while, then eventually sort docA > docB
I _think_ you can play games with the merge policy to anticipate this,
but r
I promised to ask this on the forum just to confirm what I assume is true.
Suppose you're returning results using a sort order based on some field (so,
not relevancy). For example, suppose it's a date field which indicates when the
document was loaded into the solr index. Suppose two items hav
