similar to: Omega

On 08/25/2013 05:02 PM, Olly Betts wrote: > So the simple fix is > probably just to install the perl-Search-Xapian RPM instead. Thanks, the Centos 6 repos don't have that rpm and the http://xapian.org/download page seems to only cover the XS bindings, if I am reading this correctly: But I was able to remove the rpm packages and compile and install the core and swig from source.

Hi, I was reading an article recently about how google ranks results (among many other things of course) based on the proximity of the search terms in the source documents. In addition, the position of the search terms in the search query string itself is also taken into consideration when determining how important each term is. Does Xapian do something similar - at least for the first part?

IRIX 6.5.22, compiled omega.0.8.1 with native MIPS compiler. omega.cgi isn't running from apache. From the log: [Wed Sep 1 10:04:36 2004] [error] [client 198.149.32.31] malformed header from script. Bad header=Caught unknown exception: /var/www/cgi- bin/omega.cgi This is with a url of http://<machine>/cgi-bin/omega.cgi?DB=/open/ When I run it from the command line with no

At least it isn't working the way it used to. Code: $db = Search::Xapian::Database->new( $dx ); my $qp = Search::Xapian::QueryParser->new(); my $dbSize=$db->get_doccount(); # $qp->set_stemmer(new Search::Xapian::Stem("english")); # $qp->set_stemming_strategy(STEM_SOME); # $qp->set_default_op($defaultop); my $par =

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

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

James, thanks for the explanations. I misread the notes. As an exercise, I'm trying to convert an existing project that currently uses Scriptindex and Omega to direct Xapian API calls. I did a (I think) complete dump of a document with delve -r 565 -d database and I see things like subject='A typical subject' with a corresponding set of terms like Sa Stypical Ssubject Which

To Olly Betts: Thank you very much for any feedback. I apologise for this belated reply and also for the fact that the text of the previous posting appeared fragmented, due to its fixed chars/line format. With reference to: > Can, or could, one construct a query so that Omega (Xapian) can handle > this ? > > ... perhaps with some type of Regex ? > > It would seem

Hello :-) How can the default omega URL be prettified? http://<host_ID>/cgi-bin/omega is working fine, giving us all omega's default CGI parameters. Now we want multiple databases which could be accessed using http://<host_ID>/cgi-bin/omega?DB=<index_ID> but this is starting to get messy. It will get messier when we start to customise templates with

Hi, I've tested omega (cgi) on several sql databases on my local machine in which runs Ubuntu, using the version 0.9.4 (installed using apt), and I was really satisfied for the results I obtained. I customized a bit the "query" template. But once I installed omega on the server (using apt for Debian, and omega version 0.9.5), I discovered that the relevances didn't work, as

I'm using omega for a sitesearch and currently having a problem trying to filter $field(sample). At the moment it returns text from the page header and navigation within the sample, ideally I'd like it to return only the page content. I've been trying various omegascript commands to trim the output or seperate the fields and also looking at scriptindex to control how the xhtml is

When I submit a filename to the query parser it breaks it up Example: /home/user/file_name.ext becomes Xapian::Query((home:(pos=1) PHRASE 5 user:(pos=2) PHRASE 5 file:(pos=3) PHRASE 5 name:(pos=4) PHRASE 5 ext:(pos=5))) which does not find the document. If I do an single term query not using the query parser then I find the document. The Query Parser also breaks up hyphenated terms

I've now uploaded Xapian 1.0.1, which you can download from the usual place: http://www.xapian.org/download.php This release mainly comprises bug fixes and performance improvements. The "simple" examples (for both C++ and the bindings) have also been overhauled and now use the QueryParser and TermGenerator classes, which makes for simpler examples and should better reflect

I've now uploaded Xapian 1.0.1, which you can download from the usual place: http://www.xapian.org/download.php This release mainly comprises bug fixes and performance improvements. The "simple" examples (for both C++ and the bindings) have also been overhauled and now use the QueryParser and TermGenerator classes, which makes for simpler examples and should better reflect

On 08/24/2013 08:51 PM, Olly Betts wrote: > On Wed, Aug 21, 2013 at 01:58:35PM -0400, Jim Lynch wrote: >> At least it isn't working the way it used to. > What version are you trying this on (i.e. what is x in 1.2.x) and which > older version was it working with? New (Centos 6): xapian-bindings-1.2.15-1.x86_64 xapian-core-libs-1.2.15-1.x86_64 xapian-bindings-perl-1.2.15-1.x86_64

Hi guys I'm trying to figure out how I can use probabilistic searching on a given field within a document; I've written to the list about this before, but haven't quite figured out what's required and, following a little research, I think I understand what I need to do but I'd like a clarification on this. o We have a database of a number of documents, with fields: title,

Hi All I was wondering if anyone had a solution for the following problem. I user QueryParser to stem my documents before adding them to a database. During the stemming process I would like to find a way of keeping proper nouns that span two or more words together as a phrase. For example "New York" or "Gordon Brown" or "Prime Minister" get spilt up. I see

I recently lost a hard drive and after successfully restoring everything, I think, I'm getting "Error opening database `current.1': DatabaseOpeningError: Couldn't detect type of database" The directory current.1 contains the following files: -rw-rw-r-- 1 jwl jwl  30064640 Aug 28 23:44 docdata.glass -rw-rw-r-- 1 jwl jwl       151 Aug 28 23:44 iamglass -rw-rw-r-- 1 jwl jwl

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

I've uploaded Xapian 1.0.19 (including Search::Xapian 1.0.19.0), which as usual you can download from: http://xapian.org/download The most notable changes in this release are: QueryParser: * Fix memory leak if Database throws an exception during parsing. Flint backend: * Updating positional information for a document optimised a little. Search::Xapian: * Wrap