Remove portal.properties that allows storing Lucene in the database
Activity
Show:
Cynthia WilburnMarch 12, 2012 at 2:10 PM
Reopening to add 6.1.1 CE GA2. Close as Fixed.
Michael SaechangFebruary 16, 2012 at 3:24 PMEdited
PASSED Manual Testing:
Fixed on:
6.1.x GIT ID: 2fd025d089899db55f3622ba845222fa80410d2a.
6.2.x GIT ID: a2f490c1b9315b6d8010173097c7d56ba497afcf.
10 files have been edited to remove store JDBC and 2 files have been deleted. The store type jdbc has been removed from portal.properties.
Fixed
Details
Assignee
Michael SaechangMichael Saechang(Deactivated)Reporter
Christopher LuiChristopher Lui(Deactivated)Branch Version/s
6.1.xBackported to Branch
CommittedFix Priority
5Components
Fix versions
Affects versions
Priority
Medium
Details
Details
Assignee
Michael SaechangReporter
Christopher LuiBranch Version/s
6.1.x
Backported to Branch
Committed
Fix Priority
5
Components
Fix versions
Affects versions
Priority
MediumZendesk Support
Linked Tickets
Zendesk Support
Linked Tickets
Zendesk Support
Linked Tickets
Created February 16, 2012 at 1:25 PM
Updated June 24, 2023 at 3:51 PM
Resolved March 12, 2012 at 2:26 PM
As Liferay has updated to Lucene version 3.0.3, Compass is no longer compatible with this version of Lucene.
This means that we can no longer support storing Lucene in the database.
We should:
1. Remove "lucene.store.type=jdbc" from our portal.properties
2. State something that Lucene database storage is no longer supported.
In Trunk, it currently reads:
#
Designate whether Lucene stores indexes in a database via JDBC, file
system, or in RAM.
#
#lucene.store.type=jdbc
lucene.store.type=file
#lucene.store.type=ram