Hi,
We are (still) evaluating Slide for a project where we need fast searches on
property values, in collections containing large numbers of documents (around
10'000). I have two specific questions below.
Context:
We got DASL searches working (using the current CVS version) and found out
that search speed is roughly proportional to the number of documents in a
collection. If I understand the code correctly the current search system does
not take advantage of SQL searches and indexes.
Our ideal scenario is something like
-DASL client wants to find all documents in all collections having a specific
value for a user-defined property ("customer-id = A234" for example)
-Assuming a JDBC attributes store is used, Slide first makes an SQL query
like
select * from property where name='customer-id' and value='A234'
and then uses the results to retrieve the corresponding resources
Questions:
1) Am I right that currently Slide will first retrieve all resources in scope
and then add only those that match to the result set?
2) Am I right that implementing the above scenario in a general way
(basicsearch language) requires quite a lot of work, translating the
basicsearch expressions to SQL and maybe modifying the interactions between
search system and stores?
If the answer is yes to both, we might implement (and contribute) an
additional search language using SQL directly, as done by MS SharePoint for
example (see
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/spssdk/html/_search_request_format.asp),
exe).
Thanks for any advice on the above questions!
--
Bertrand Delacr�taz (codeconsult.ch, jfor.org)
buzzwords: XML, java, XSLT, cocoon, mentoring/teaching/coding.
disclaimer: eternity is very long. mostly towards the end. get ready.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
