similar to: Debian stuff

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

All, I've run into a couple of things using omega/omindex under cygwin. I don't think I'd attribute them to xapian, omega or omindex, but wanted to get them out to the list so that if anyone else should run into these things down the road, hopefully someone will remember and be able to help. 1) after compiling and building omega, and doing make install, I get a set violation when

Hello, I was looking for a search engine for a small internal documentation site and found xapian and omega. Downloaded and compiled it using msys and ming on a german windows xp system. Finally installed apache on the same box. Following the omega example I copied the book to .../apache/htdocs and startet the omindex which hang up on the first document found. Even on very short doc with

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

Dear senior ML members and developers of Xapian Omega, Mr. Olly has helped me cross the bump of the initial learning curve. (ref: https://lists.xapian.org/pipermail/xapian-discuss/2024-April/010034.html) How can I use Xapian Omega directly (i.e., without using `recoll` and `xapiandb`) to index a directory of text files with all strings greater than 3 characters, to create an index text file

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

OK, I'll try again. Thanks, Jim. -------------- next part -------------- An embedded message was scrubbed... From: Jim Lynch <jwl@sgi.com> Subject: Irix install of omega fails. Date: Mon, 28 Jun 2004 14:16:46 -0400 Size: 2057 Url: http://lists.tartarus.org/pipermail/xapian-discuss/attachments/20040628/212669c1/Irixinstallofomegafails.eml

Hi Parth, I?ve implemented SVMRanker class and also sorted out most of current Letor APIs. Now I?m trying to use INEX dataset to verify my implement. But I stuck in the indexing part. You said in the documentation that we have to add prefix when indexing. Also I notice that you set some metadata in omindex.cc of your version. But the omindex.cc has changed since 2011. I think that?s why my result

Hi, I'm working on the ticket #743 omindex: delay libmagic checks <https://trac.xapian.org/ticket/743>. As the ticket's Description mention, the call to libmagic is expensive than call the stat, so we can check the size by call the stat to get size before call libmagic to get a mime type. But how about the timestamps check? since timestamps check need to iterate the DB to check if

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

I'm starting to prepare the next release. Since 0.8.3 I've made a number of changes to get working builds working on HPUX and OSF, and made some of the Windows specific bits more robust. I'd like to check that these haven't broken CYGWIN or IRIX builds, but I don't have access to these platforms. If you are able to test, it'd be most appreciated if you could. Download a

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.

From the documentation I've read, omega can read from multiple databases, but I'm not sure how to go about this. I have three databases created using omindex, currently located at /var/lib/xapian-omega/data/share, /var/lib/xapian-omega/data/users, and /var/lib/xapiax-omega/data/management The quickstart guide says that in omega.conf database_dir should point to the directory

On Thu, Apr 18, 2024 at 03:46:53PM +0530, Susmita/Rajib wrote: > On Thu, 18 Apr 2024 at 06:24, Olly Betts <olly at survex.com> wrote: > > You may need to configure apache to tell it to use this for a URL on > > your site. > > How Mr. Betts? Suppose I have a ready open document text file, a > LibreOffice text file. say BettsBio.odt, for which I want to create an >

Given a directory tree like ... /foo | +-- A | +-- B | +-- C ... what is the best way to index A and C into a single Xapian database? AFAIK the alternatives are: omindex --db /my_db --no-delete /foo /foo/A omindex --db /my_db --no-delete /foo /foo/B or omindex --db /my_A_db /foo /foo/A omindex --db /my_B_db /foo /foo/B xapian-compact /my_A_db /my_B_db /my_db The first alternative does not

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

Hi, I?m trying to use Omega to index INEX dataset for Letor. But omindex told me these xml files are unknown. Olly told me I could tell omindex to handle them as HTML. (Thanks Olly :) ) Is it appropriate? Parth, could you give me some suggestions? Thank you! Jiarong Wei

Hi, everyone. I'm a third-year student in Computer Science. I have a few projects (school-related) on Bitbucket <https://bitbucket.org/philipchung/philipchungtech>. I've been looking at the project-ideas list and I'm interested in making Omega use libraries instead of external programs. Right now I'm trying to get Olly's patch that was linked there to apply to the

HI all, I'm just testing out the capabilities of xapian and omega. Environment - Fedora15. Disk to be indexed - 2GB? - FAT16 filesystem. Named "New Volume" When I add a text file to the disk, by right-clicking in Fedora and choosing Create New - > Text File The system creates the text file as expected. I added some content/words, however, xapian-omega will not index it:

I've uploaded Xapian 1.0.11 (including Search::Xapian 1.0.11.0), which as usual you can download from: http://xapian.org/download Starting from this release, I'm going to include SHA1 checksums of the released files in the release announcement. For 1.0.11 these are: 480fd99617975c1aaf9127cd7c7166bc05d07eb1 Search-Xapian-1.0.11.0.tar.gz 217c7fb1754d0aeaf82c3ab83d5ec0881099bb61