Hi Pankaj,
Jackrabbit guarantees that queries executed on a workspace are always
correct against the current persisted state of items. Please note that
unsaved changes are not searchable, as specified in jsr-170.
The query implementation uses lucene to maintain an index. we
implemented several extensions to lucene that allow jackrabbit to
efficiently index on an incremental basis.
See also: http://incubator.apache.org/jackrabbit/doc/arch/operate/query.html
which explains some of the implementation details.
To answer your question: you do not have to manually re-index the
repository after a change.
regards
marcel
Pankaj Gupta wrote:
Hi,
I am new to Jackrabbit and from what I have read so far, it looks like a
great product. However I am a little concerned about the use of Lucene
as the search engine. In my application I would be creating a dynamic
data repository and need the search results to be correct and
up-to-date. For example, if I add/delete nodes or change the properties
of some nodes, these changes should be reflected in the next query by
any user of the repository.
Is this behavior guaranteed by Jackrabbit or do I need to manually
reindex after any changes to the repository. If so, what are the
performance implications of reindexing?
I would appreciate any help on this.
Thanks,
Pankaj
--
-----------------------------------------< [EMAIL PROTECTED] >---
Marcel Reutegger, Day Software AG, Barfuesserplatz 6, CH - 4001 Basel
T +41 61 226 98 98, F +41 61 226 98 97
-----------------------------------------------< http://www.day.com >---
