Bug 35810 - Lucene content indexer doesn't work when binding is enabled
Summary: Lucene content indexer doesn't work when binding is enabled
Status: NEW
Alias: None
Product: Slide
Classification: Unclassified
Component: Search (show other bugs)
Version: Nightly
Hardware: PC All
: P3 major with 2 votes (vote)
Target Milestone: ---
Assignee: Slide Developer List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-21 10:42 UTC by Nicolas Aguil
Modified: 2005-11-02 01:38 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nicolas Aguil 2005-07-21 10:42:52 UTC
I use Slide 2.2pre1 with tomcat 5.5.9

Configuring lucene contentindexer
org.apache.slide.index.lucene.LuceneContentIndexer works perfectly on my store

But when binding (org.apache.slide.store.BindingStore) is enabled for this store
the contentindexer stops working. (nothings happen in the indexpath : no
creation of deletable and .cfs files)
Comment 1 Nicolas Aguil 2005-08-26 08:37:49 UTC
i think i've found the reason of this behaviour but i still need help for
solving it.

The problem comes from the 'matches' method from the ExtractorManager class.
- when binding is disabled the line
   uri.startsWith(extractor.getUri()) returns true because :
      uri is /documents/install.txt
      extractor.uri=/documents

- but when binding is enabled :
   uri is /112497926846/0/29
   extractor.uri=/documents       this meens that 'matches' never match an
Extractor so content ise never indexed.

When reading metadata/.def.xml i've seen the tag <child name="documents"
uuri="112497926846/0/23" />
and in metadata/112497926846/0/29.def.xml there is the tag <parent
name="install.txt" uuri="112497926846/0/23" />

I need help from a developper of slide (or someone else) because i don't know
how to retrieve these properties for matching them.