[zanata-bugs] [Bug 815197] Reindex operation takes a long time on production server
bugzilla at redhat.com
bugzilla at redhat.com
Mon Apr 23 06:18:11 UTC 2012
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=815197
--- Comment #2 from David Mason <damason at redhat.com> 2012-04-23 02:18:10 EDT ---
Technical note added. If any revisions are required, please edit the
"Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content
Services team.
New Contents:
Cause
The available search re-indexing operation always discards existing indexes and
re-indexes all classes.
Consequence
Search re-index takes an unnecessarily long time when only a single class needs
to be re-indexed. Search operations are not able to use existing indexes until
the re-index operation for the appropriate class is complete, so will not
return good results.
Change
Search re-index backing beans were updated to take a set of boolean options for
each indexable class, which determine whether existing indices for the class
will be purged, whether re-index will be performed on entities of the class,
and whether the index for the class will be optimized. These options are
presented in a table on the "Manage Search" page under the Administration menu.
Result
Classes can be re-indexed separately, allowing for shorter re-index time per
operation. Existing indices can be kept during re-indexing, so searches may be
able to return good results during re-index.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
More information about the zanata-bugs
mailing list