Affects Version/s: 6.1.1 CE GA2, 6.1.20 EE GA2
Component/s: Search Infrastructure
Environment:Tomcat 7 + Oracle 11g. Portal EE 6.1.x GIT ID: a53e1bfe45d67ca0e53aac060a8af0d0a1d554dd.
Tomcat 7 + Oracle 11g. Portal CE 6.2.x GIT ID: 92946415c75e5c4a04b8c450b511f078e6b42be5.
Backported to Branch:Committed
As the order of retrieved rows of a SELECT statement without an ORDER BY clause is completely arbitrary, the following piece of code in JournalArticleIndexer might index old versions instead of new ones.
Steps to reproduce
1) Create a Web Content with title "WC1" and publish it a few times in order to create more than one version of it.
2) Even tough the row order is completely arbitrary, in small quantities we can reverse it for the sake of testability.
3) Do a full reindex.
4) Look into the search index with Luke (https://luke.googlecode.com/files/lukeall-3.5.0.jar).
- Point Luke to the index direcotory of Liferay.
Example Path: /home/lcsontos/liferay/instances/lportal-trunk/data/lucene
- Tick Open in Read-Only mode.
5) Search for "title:wc1" (with lowercase) and seek field version.
- Select the Search tab.
- Put search query into field Enter the search expression here.
- Click Search.
What you should see here is that the current value of version of the found document is "1.0" (or the lowest if you previously deleted "1.0").