AW: [opencms-dev] Search engine / pure Java

[weHe @ FreeCreatives]

> -----Ursprungliche Nachricht-----
> Von: owner-opencms-dev at www.opencms.org
> [mailto:owner-opencms-dev at www.opencms.org]Im Auftrag von Thomas Maerz
> Gesendet: Dienstag, 14. Janner 2003 13:03
> An: opencms-dev at www.opencms.org
> Betreff: Re: [opencms-dev] Search engine / pure Java
>
>
> Hello,
>
> has somebody already tried to use different search indexes for different
> users resp. groups of users?

not me.

> My thinking was to export the sites temporarily statically and then to
> create for each user a different index to use Lucene. I also have the
> lists of files belonging to each users access permissions.
> But then I wasn't able to export the files statically, because of the
> the different access permissions the files mustn't be exported. At this
> point I then I chose something else to do, because of the database
> access errors.

I think, I'd index 'em all together in one index set and just let the
httpd's
access mechanism handle the rights - if you're worried about accidentially
revealing
confidential info through the description text's of the search hits, then
you can
omit those from your list of search results.

Or you could also include an extra field in your index to store the
access-level
of the document and use this during your seraches in addition to the user's
query string.



> By the way I didn't adapt the Lucene module, but just created a JSP-file
> which executes a Java command to update the index:
>
> ,----[ not very nice, but works for me ]
> | java -classpath /lib/lucene-1.2.jar:/ \
> | org.apache.lucene.demo.IndexHTML -create -index /export/index /export/
> `----

seems a nice idea, but I'd use it in addition to a cron'ed call
and I'd suggest to spawn it into an off-JSP threat; also, using -create
for every run ever looks inefficient.

Regards, Werner