Bug 98055 - lucene indexing of p2fs content
lucene indexing of p2fs content
Product: Red Hat Enterprise CMS
Classification: Retired
Component: other (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: ccm-bugs-list
Jon Orris
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2003-06-25 16:36 EDT by Richard Li
Modified: 2007-04-18 12:55 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-07-12 04:43:24 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Richard Li 2003-06-25 16:36:33 EDT
Something which may be interesting for other projects: 

For FranceTV, we have implemented Lucene indexing of content published
to the filesystem. This is done by maintaining a Lucene index which is
separate from the search engine we have on the editorial server. 

The changelist is 32335, and basically involves two new methods in
PublishToFile which can be overriden in derived classes
(indexSearchContent and unindexSearchContent). For computing the indexed
content, we use the Lucene Adapter class that's part of the existing
search engine.

The location of the PFS Lucene index is controlled with this section in

init com.arsdigita.cms.publishToFile.LuceneInitializer {
    // Settings for indexing PFS content with Lucene.
    luceneIndexLocation = "/tmp/lucene-index.dat";

And publishListener has to be changed to:

publishListener = "com.arsdigita.cms.publishToFile.LucenePublishToFile";

Documentation can be found in the JavaDoc of
com.arsdigita.cms.publishToFile and LucenePublishToFile, and in

Expected results:

Additional info:
Comment 1 Carsten Clasohm 2003-07-11 07:49:08 EDT
I have changed the implementation in the meantime. See changelist 33226.
Comment 2 Carsten Clasohm 2006-07-12 04:43:24 EDT
Closing old tickets.

Note You need to log in before you can comment on or make changes to this bug.