similar to: wildcard support (left truncation)

Hi. I am writing a python equivalent of omindex (we are using scriptindex currently - but I wanted to use omindex instead, and extend it to work with our internal file format.. BUT did not want to compile code if possible... so anyway). I have tried to keep the code as close to possible to the omindex native code, but am facing a bit of confusion: what exactly is the reason for omindex to take

I would really like to try out the features in the patch above. But I can't ever seem to get the resulting omindex.cc to "make". I tried updating to rev 10801 from the SVN then run /bootstrap but then I seem to get errors compiling everything when I try and do "make" (I'm using ubuntu 8.10). So I thought I'd try an apply the patch to the latest stable version

Hi, I configured XAPIAN 1.0.1 and OMEGA 1.0.1. on my development machine (first removed the old ones). I recreated my databases (both quartz and flint) and tried to run original queries against the databases created by the new versions. I'm getting empty result sets from OMEGA. If I use the delve tool I actually see that the records are created fine. No log files are written as far as I

Hi All, I've installed Xapian and the php module. I've set up a script for use with scriptindex and dbi2omega for getting data from the db into the index easily, the script file is as follows: =============================== id : field=id title : index title: field=title description : index description : truncate=50 field=content ============================= However, when querying

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.

I installed Xapian and Omega following the instructions for the RHEL 5 RPM package found at xapian.org. I was going to perform the quick start instructions, but there is not "omnidex" for the omindex --db DBPATH --url / WEBPATH command. The quick start also mentions running omega from usr/lib/omega/bin; however that was not created as well using the RHEL 5 RPM. Is there a walkthrough on

Hi, I'm trying to write the PowerPoint2007 filter in the same manner that I did for *.docx and *.xlsx but I'm getting the following error when I tru an index. The document is called: Indexing "/Frisk in Power Point.pptx" as application/vnd.openxmlformats-officedocument.presentationml.presentation ... caution: filename not matched: ppt/notesSlides/notesSlide*.xml caution:

Hello list, I would like to try indexing data in a database table. While I got dbi2omega to work and print the data, I am still not sure how it all works together. What should be done to the output from dbi2omega? If for example I have a table with 5 fields 2 of which I would like to index, like so: (id primary key, title varchar(100), name varchar(100), description

Guys, I was just playing around and added a bit of code to omindex.cc so I could ocr tiff and tif with gocr which seems to work. Here's what it looks like: // Tiff: } else if (startswith(mimetype, "image/tif")) { // Inspired by http://mjr.towers.org.uk/comp/sxw2text string safefile = shell_protect(file); string cmd = "tifftopnm " + safefile + "

Guys, I was just playing around and added a bit of code to omindex.cc so I could ocr tiff and tif with gocr which seems to work. Here's what it looks like: // Tiff: } else if (startswith(mimetype, "image/tif")) { // Inspired by http://mjr.towers.org.uk/comp/sxw2text string safefile = shell_protect(file); string cmd = "tifftopnm " + safefile + "

Hi, I was researching indexing of text in omindex and scriptindex. While indexing text with omindex.cc possition of terms is saved with gap. This is not happening with scriptindex.cc While this is happening ? Another question is why in omindex.cc the term possition starts with 0 while in scriptindex it starts from 1 ? Code snippet from omindex.cc // Add postings for terms to the document

hallo, I'm indexing a filesystem using omindex, and users can query the database via omega: everything works fine now I'd like to add an option like "search files by name" and I'm wondering how to do this can omega search files by name directly? how should I build the query? could I use scriptindex to index, eg., the locate database? how? should I index file names

I'm playing around with a machine that has 2 GB of memory. Indexing about 5GB of data average of 2MB per document. The documents are plain text. I notice the omindex's memory fott print get's biger an bigger then the machine starts to swap and it all slows down to a crawl. In regards to export XAPIAN_FLUSH_THRESHOLD I know the default is 10000 Am I right in saying that for my setup

Proposed changes to omindex Currently Available Items ========================= 1) Have the Q prefix contain the 16 byte MD5 of the full file name used for document lookup during indexing. 2) Add the document?s last modified time to the value table (ID 0). This would allow incremental indexing based on the timestamp and also sorting by date in omega (SORT=0) a. Currently I store the timestamp

Ocassionally when I'm searching using Omega I get: "DatabaseCorruptError: Cannot open tables at consistent revisions" If I click reload it's all ok, is this the database being updated?, is there a way to avoid the message? Frank

I propose making a few changes to the way omega (and omindex) operate. I'm posting these to the list before doing so to check if they'll cause obvious problems for anyone. 1) Configuration handling for omega. Omega has a configuration file, which specifies where databases, templates and logfiles are to be found. It currently looks for this configuration file in its current working

Hi, all -- I want to do Plain Old Omindex'ing *but* the mapping between my documents' filenames and the URLs where I hope search users to find them is, uh..., strange. The simplest thing (to me) would be to run omindex for each document, e.g. omindex --no-delete -U /cool-url-1 /funky/doc/file-blah.pdf omindex --no-delete -U /cool-url-7 /doc/funky/ohmy/blah-file.txt ... and so on...

At wiki page: http://wiki.xapian.org/Omega I added a comment that ht://Dig looks like dead. Does anybody really use it? >From brief glance at docs I had a feeling it is not easy to configure. Maybe better crawler is GNU wget? Mature, stable, maintained? -- Peter Masiar

I am trying to replace my forum's search feature with the Xapian search system (the forum is phpBB), and there's some critical information that isn't in the Xapian documentation. I need information on installing xapian into PHP, since this area is not very detailed in the online documentation. So, how does one go about using the Xapian search system with PHP? OS:FreeBSD 5.4-RELEASE

I am trying to replace my forum's search feature with the Xapian search system (the forum is phpBB), and there's some critical information that isn't in the Xapian documentation. I need information on installing xapian into PHP, since this area is not very detailed in the online documentation. So, how does one go about using the Xapian search system with PHP? OS:FreeBSD 5.4-RELEASE