On 26 Nov 2003, at 11:18, LOMBART Christophe wrote:
Obviously, I'm not talking to you directly. I have just a new user requirement for the next year and I want to receive comments from the committer team.
I sent previous mail on Lucene in this mailing list. I never received a clear response/position on that subject.
So, just some questions on the current search features in Slide : * What about the performances ?
it's dead slow, grows linearly with content, scoping and ordering don't work, custom properties are matched in /history but not in /files... I plan to fix scoping, ordering and property matches (since they just seem bugs).
For the first two (slow and linear growth), well, this is a pretty big design issue.
My suggestion would be to use the JDBC store for properties and translate the DASL query into SQL and let the database take care of everything. So, if you have the TX property store, we use our own (slow) code, if we have a JDBC repository, we use its own query functionality (which should be, if the indexes are setup correctly, O(1) instead of O(n) where n number of documents in the repository)
* Is it possible to search on content ? seems to be optional in webdav search.
currently, it's not possible (AFAIK)
* If I'm using only the helper class - not yet the webdav layer - it is not too complex to use the search helper class ? What about lucene within slide in this case. Lucene api is quite simple.
See my previous email on what I think would be the best way to integrate fulltext search with slide.
-- Stefano.
smime.p7s
Description: S/MIME cryptographic signature
