lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vladimir Gubarkov <xon...@gmail.com>
Subject Sort.INDEXORDER works incorrectly?
Date Tue, 17 Apr 2012 23:27:07 GMT
Hi, dear Lucene specialists,


I've updated in my project the version of Lucene to the latest (3.6).
I wanted at last to add near realtime support to my indexing
subsystem. Everything seemed to work pretty fine except that I
suddenly encountered that the sorting by indexorder (actually,
reversed order as I'm using new Sort(new SortField(null,
SortField.DOC, true))) not works as before.

Please let me explain. I am sorting by reversed index order because it
coinsides with the order of the dates of my documents (actually, forum
posts) but sorting by actual dates is much more RAM-intensive and
slow.

Now what I'm seen is the resulting order looks like random.
Interesting enough is that when I search by *:* (matchall) I'm getting
nearly correct order (though at 1 results page it is also little
broken).

The only explanation I could think of is the new TieredMergePolicy
instead of old LogMergePolicy. Could it be that because of
TieredMergePolicy merges not adjacent segments - this results in not
preserving index order or this is total nonsense?

Please advise.


Sincerely yours,
Vladimir

---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org


Mime
View raw message