[Xapian-discuss] omega: omindex behaviour with duplicate files

John Pye john.pye at student.unsw.edu.au
Thu Jul 12 09:48:39 BST 2007

Hi all

I need a little clarification with regard to Omega's behaviour with
'duplicate' files when running 'omindex'.

How is a duplicate recognised? Is it simply by file path? How is an
unmodified file detected, if at all?

I would like to set up subversion post-commit hook to update my index.
If possible I would like to just update the index with the newly
commited files. What is the most efficient way to do this? Is it
something that has already been implemented by others?

Secondly, is there any way that the verbosity of the omindex output can
be reduced? I would like it if there were a '--quiet' option that only
output information about files that were actually being reindexed.

I would like to set up this post-commit hook so that documents deleted
from the repository are correctly removed from the index. At present my
post-commit hook script works by brute force, and looks like this:

cd /data/omegadocs && svn up
omindex -d ignore --db /var/lib/omega/data/default --url /svn/

If there are any tips for improving this, it would be much appreciated.


John Pye
Department of Mechanical and Manufacturing Engineering
University of New South Wales, Sydney, Australia

More information about the Xapian-discuss mailing list