-
Type:
Regression Bug
-
Status: Closed
-
Resolution: Fixed
-
Affects Version/s: 6.2.X EE, 7.0.0 M3
-
Fix Version/s: 6.2.3 CE GA4, 6.2.X EE, 7.0.0 M3
-
Component/s: Search Infrastructure, Search Infrastructure > Framework
-
Branch Version/s:6.2.x
-
Backported to Branch:Committed
-
Story Points:12
-
Fix Priority:3
-
Git Pull Request:
After a full reindex of Liferay indexes, a wrong webcontent version is indexed in Lucene index when journal.articles.index.all.versions=false
Steps to Reproduce
- Install hotfix that includes
LPS-48407 - Activate journal.articles.index.all.versions=false flag at portal-ext.properties
- Create a new web structure and template
- Create a new webcontent using previous created structure
- Add some versions to webcontent, leave last version as "draft" (1.0 => approved, 1.1 => approved and 1.2 => draft)
- Check indexed version at lucene/elasticsearch index: the last approved version 1.1 version will be stored at index
- Execute a full reindex of Liferay indexes => all webcontents will be reindexed
- Check indexed version at lucene/elasticsearch index: the 1.2 version(draft) will be stored at index
- Discovered while testing
-
LPS-51880 After modifying a Structure, a wrong webcontent version is indexed in Lucene index when journal.articles.index.all.versions=false
- Closed
- is caused by
-
LPS-48407 Support for not searching in the History of Web Content Administration
- Closed
- relates
-
LPE-13174 Incorrect Web Content article version is indexed in Lucene
-
- Closed
-