search for: enquire

i have 300 millions records and my search file like this , i want the newest 10 results that match my query , so i use boolean search and "enquire.set_docid_order(enquire.DESCENDING)" , but this method seems a little slow . when i remove "enquire.set_docid_order(enquire.DESCENDING)" it run much faster . how can i fetch the newest 10 results as fast as possible? search.py #-*- coding: utf-8 -*- import xapian import sys,time...

I got some performance issue for document.get_data() and enquire.get_mset(). It costs 35 seconds for matches = enquire.get_mset(0,200), and 3 seconds for iterating all doc in matches to get_data. Is't normal? My index contains 30millions documents. I use python binding to operate xapian. Bellow it's my index structure # value: 0:date, 1:site # data: json...

Hello list, looks like one can open a Xapian database in read-only mode and do the following: $db = Search::Xapian::Database->new("/foo/bar/"); $enq = $db->enquire("XIDblub"); the same doesn't seem to be possible with a database opened in read-write mode: $db = Search::Xapian::WritableDatabase->new("/foo/bar/", Search::Xapian::DB_CREATE_OR_OPEN); $enq = $db->enquire("XIDblub&q...

...#39; . 'mail'); $xdb->add_document($doc); $doc = Search::Xapian::Document->new; $doc->add_value(0, $num); $doc->set_data("$i $j"); $doc->add_boolean_term('T' . 'ghost'); $xdb->add_document($doc); } $xdb->commit_transaction; } my $enquire = Search::Xapian::Enquire->new($xdb); my $mail_query = Search::Xapian::Query->new('T' . 'mail'); $enquire->set_query($mail_query); $enquire->set_sort_by_value_then_relevance(0, 1); my $offset = 0; my $limit = 200; my $t0 = clock_gettime(CLOCK_MONOTONIC); my $mset = $enqu...

In other words, is it possible to avoid duplicates if new documents are inserted into the DB by another process in-between ->get_mset calls when reusing Xapian::Enquire objects? I do some expensive processing on each mset window, so I always limit the results to limit heap usage even if I'm planning on going through a big chunk of the DB: $mset = $enq->get_mset(0, 1000); do_something_slow_with_mset($mset); $mset = $enq->get_mset(1000, 1000); do_som...

...;< "Log file: " << logname << "Query " << query << endl; + std::ofstream logfile(logname.c_str(), ios::out | ios::app); + logfile << query << endl; + logfile.close(); +} + void Database::reopen() { diff -ur xapian-core-1.2.17-o/api/omenquire.cc xapian-core-1.2.17/api/omenquire.cc --- xapian-core-1.2.17-o/api/omenquire.cc 2014-01-29 08:28:01.000000000 +0530 +++ xapian-core-1.2.17/api/omenquire.cc 2014-04-13 17:50:07.000000000 +0530 @@ -22,6 +22,10 @@ * USA */ +// TODO remove it afterwards +#include <iostream> +#include <f...

Hello, this is a question that could be answered by collaborators of the Ruby bindings. Today I've played around with the Xapian::MultiValueSorter class. I've set everything up and then I tried following on an instance of Xapian::Enquire: : enquire = Xapian::Enquire.new(database) enquire.query = options[:query] : sorter = Xapian::MultiValueSorter.new sorter.add(0, true) sorter.add(1, true) : enquire.sort_by_key_then_relevance(sorter) : And it seems that there is no 'sort_by_key_then_relevane' method implented in Xapian::E...

Hello, This is a somewhat idle question about Enquire::get_mset(), possibly based on wrong assumptions on how Xapian works, but I would be grateful if someone satisfied my curiosity. Xapian::MSet Xapian::Enquire::get_mset(Xapian::doccount first, Xapian::doccount maxitems, const Xapian::RSet * omr...

Hello, I am a post-doc of the Federal University of Santa Catarina State (UFSC). Last year, used EnQuireR for hirarchical cluster analisis and end up very well. I formated my computer couple months ago and installed R again as version x64 3.0.2. have new data which ENMCA function of EnQuireR package is not running. R seems to be fine as it runs funcions of other packages. Even MCA fuction of...

My code is not on Github. I am using the tarball as of now. The following it the error that occurred: http://pastebin.com/cVJrjUZX On Sun, Apr 13, 2014 at 8:16 PM, James Aylett <james-xapian at tartarus.org>wrote: > On 13 Apr 2014, at 15:37, Pallavi Gudipati <pallavigudipati at gmail.com> > wrote: > > > A linker error is encountered even after following the above

Dear editor: I'm writing this letter to enquire where can I download the package of "lmtest". Can you send me this package? THanks a lot. Best regards, Shu-Fei Wu

There's a bit of an API glitch with Query objects at present. This code shows it off: Xapian::Database("/path/to/db"); Xapian::Enquire enquire(db); // make a simple query Xapian::Query myquery(Xapian::Query::OP_NEAR, phrase, phrase + 2); enquire.set_query(myquery); // Now change the query - this shouldn't affect the query enquire // will run, but it does. myquery.set_window(10); The essential issue here is that querie...

On Thu, Aug 17, 2023 at 09:28:26PM +0000, Eric Wong wrote: > In other words, is it possible to avoid duplicates if new > documents are inserted into the DB by another process in-between > ->get_mset calls when reusing Xapian::Enquire objects? The Database object itself effectively does (it works in a snapshot of the state of the database when you open it, or last called reopen() which updates that snapshot to what's currently committed). However we don't currently have any locking of the snapshots that readers are usi...

...that I'm building a search engine for a mailing list and I would like to return matches sorted by date; ordering by docid (since the messages are indexed in chronological order) seems to be the simplest way to do so, but because I'm running a probabilistic query I don't think I can use Enquire::set_docid_order, since that will first sort by relevance and then by docid. I thought about adding the date as a value and then use set_sort_by_value, but I wonder about performance (the database contains about one million records). Any thoughts? Thanks, Marco

Hi everyone, I've searched the mail archives and I haven't been able to find a solution to this. I want to subclass a MatchSpy in the Python bindings and have Enquire use it. However, when I try to do so, I get a TypeError raised. The following example illustrates this: >>> import xapian >>> database = xapian.Database(dbpath) >>> class MyMatchSpy(xapian.MatchSpy): ... def __init__(self): ... pass ... def __call__(s...

Olly Betts <olly at survex.com> wrote: > On Fri, Mar 30, 2018 at 05:21:43PM +0000, Eric Wong wrote: > > Hello, is there a way to optimize sorting by certain values > > for queries which return a huge amount of results? > [...] > > $enquire->set_sort_by_value_then_relevance(0, 1); > > If you're just wanting the 200 newest, it'll be faster not to calculate > weights, so: > > $enquire->set_sort_by_value(0, 1); > $enquire->set_weighting_scheme(new Xapian::BoolWeight()); > > For me, this drops t...

Hi, Nice to receive your suggestions. Follwing the suggestions, the xapi service does work on a non XCP host and most of the xe interface of get information (such as "xe vm-list ")can work well. However, when I used the "xe sr-create" interface to create a SR, I got a error "The SR could not be connected because the driver was not recognised ". I noted that

Hi, Nice to receive your suggestions. Follwing the suggestions, the xapi service does work on a non XCP host and most of the xe interface of get information (such as "xe vm-list ")can work well. However, when I used the "xe sr-create" interface to create a SR, I got a error "The SR could not be connected because the driver was not recognised ". I noted that

...;panjunyong at gmail.com> To: Tim Brody <tdb2 at ecs.soton.ac.uk> On Wed, Aug 10, 2011 at 6:39 PM, Tim Brody <tdb2 at ecs.soton.ac.uk> wrote: > Hi, > > In terms of the enquiry, do you mean this?: > set_weighting_scheme(Xapian::BoolWeight()); > set_docid_order(Xapian::Enquire::DESCENDING); > > In my test, it is more than 10 times slower than : set_weighting_scheme(Xapian::BoolWeight()); set_docid_order(Xapian::Enquire::ASCENDING); Why? What's the most efficient process to build multiple Xapian indexes? Can > the "relevance" index provide any hi...

...here, (the comment says it was auto-generated, so I'm guessing it currently simply includes every method matching set_* or get_*). The ones I'm thinking of are those set_ methods which don't take exactly one parameter, and perhaps those get_ methods which take parameters. For example, Enquire::set_sort_by_relevance doesn't take any parameters, while Enquire::set_sort_by_value takes two (the second is optional, but it allows you to reverse the sort order which is a common thing to want to do). Neither of these methods is really a setter method in the usual sense. They're just m...