Hi,
-----Original Message----- From: Oliver Zeigermann [mailto:[EMAIL PROTECTED] Sent: Freitag, 23. Januar 2004 13:56 To: Slide Developers Mailing List Subject: Re: Integrate Indexstore and SEARCH (was Indexing store)
Wallmer, Martin wrote:
Hi Stefano,
-----Original Message----- From: Stefano Mazzocchi [mailto:[EMAIL PROTECTED] Sent: Donnerstag, 22. Januar 2004 14:47 To: Slide Developers Mailing List Subject: Re: Integrate Indexstore and SEARCH (was Indexing store)
On 21 Jan 2004, at 14:57, Wallmer, Martin wrote:
In Domain.xml we could have something like:
<store name="jdbc" classname="org.apache.slide.store.BindingStore">
<nodestore
classname="org.apache.slide.store.impl.rdbms.JDBCStore">
<parameter name="driver">com.mysql.jdbc.Driver</parameter>
<parameter name="url">jdbc:mysql://localhost:3306/test?autoReconnect=true</ parameter>
<parameter name="user">wam</parameter>
<parameter name="password"/>
<parameter
name="adapter">org.apache.slide.store.impl.rdbms.MySqlRDBMSA
dapter</
parameter>
</nodestore>
<securitystore>
<reference store="nodestore"/>
</securitystore>
<lockstore>
<reference store="nodestore"/>
</lockstore>
<revisiondescriptorsstore>
<reference store="nodestore"/>
</revisiondescriptorsstore>
<revisiondescriptorstore>
<reference store="nodestore"/>
</revisiondescriptorstore>
<contentstore classname="org.apache.slide.store.txfile.TxFileContentStore">
<parameter name="rootpath">mysql/store/content</parameter>
<parameter name="workpath">mysql/work/content</parameter>
</contentstore>
<indexer classname="my.lucene.Indexer"/>
<searchengine>
<parameter name="propertySearchClass">my.sql.SearchEngine</parameter>
<parameter name="ContentSearchClass">my.Lucene.SearchEngine</parameter>
</searchengine>
</store>
Does this make sense?
It sure does, but I believe you missed my point.
Here, you are partitioning the tree with stores, and you are associating indexers and searchengines to the store.
What if I want to have two different partitions of the tree space, one for storing and one for indexing/searching? [I believe Oliver was wondering about this as well] and potentially having them layered allowing a single file to be indexed/searched by more than one indexer at the same time?
Just to see if I got your point:
you define a store named foo in domain.xml
you want all documents, that go into foo/images indexed by
a jpeg indexer
you want all documents, that go into foo/pdf indexed by a
pdf indexer
all documents elsewhere in or below foo shall be indexed by
text indexer.
My idea was all those indexers *might* update a *single* index and thus there might be single search without merging.
Yes! So we should have *one* indexer (or an indexer framework) in which
you can plugin a jpg indexer, a pdf indexer, ...
If all that indexed data is written to the same store as the NodeRevisionDescriptors (say in RDBMS), you can write a search engine
that executes a mixed (prop and content search) at once, no merge.
OK, so we were agreeing all the time, right?
A question to the Lucene experts: Where does Lucene writes its index? Is it possible to store in RDBMS?
I was wondering about this as well. Another real problem might be when to index and transactionality. If we index as soon as we write a resource and then decide to rollback at some point it might be a problem if we updated a main index. It might be necessary to create a new index and merge it with the existing one on commit.
Oliver
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
