similar to: Incorrect get_matches_estimated() of Xapian::Mset

I've uploaded Xapian 1.0.20 (including Search::Xapian 1.0.20.0), which as usual you can download from: http://xapian.org/download The most notable changes in this release are: Xapian::MSet: * Fix incorrect values reported by get_matches_estimated(), get_matches_lower_bound(), and get_matches_upper_bound() in certain cases when sorting and collapsing (ticket#464). getopt-related build

Hi all, I found that the figure returned by MSet::get_matches_estimated() varies depending on how results are to be sorted. For instance, in my index, value 4 contains date and time in the format "yyyymmddhhmmss". For the same query, the number of results will be estimated to 20000+ when results are first sorted by date and time with set_sort_by_value_then_relevance(4) and to only 100

Hi, I'm getting quite odd results using get_matches_estimated() that I haven't seen before; we've just added a bunch of new data to the database. Xapian 1.0.7, checkatleast is set to 100. The database will get new stuff added to it automatically around 8.30am BST, so it's possible this might affect the links I provide, I guess. But I'll note what is currently happening as

I don't know whether this is a BUG or for special purpose... According to the definition of "xapian/queryparser.h", FLAG_AUTO_MULTIWORD_SYNONYMS contains bit of FLAG_AUTO_SYNONYMS . Therefore, long as I set the parse flag with FLAG_AUTO_SYNONYMS, the query parser will automatically activate the function of FLAG_AUTO_MULTIWORD_SYNONYMS. See the below source code part from

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

Hi, I have already re-make the patch file, based on the trunk codes in SVN respo. But I can not build the xapian, because there are many errors when building 'languages/' for stemmer. Therefore, I could not test the new patching code. Patching code can be accessed from: http://www.xunsearch.com/download/xapian-scws-1.3.x-trunk.patch Need to install SCWS first as below steps: 1.

Hello, i've some problems with my query. I have a database where the documents have a date stored to value 0. I need to know the trend for a boolean query: example, I want to know how may documents are indexed by "foo" in different value ranges. I proceed building the query: Xapian::Query((foo:(pos=1) AND VALUE_RANGE 0 1286264160 1286264249)) and Xapian::Query((foo:(pos=1) AND

Xapian is a very excellent open source search engine library, but there is no native support for Chinese word segmentation in queryparser and termgenerator. Therefore, I modified small amount of source codes, integrated into the SCWS tokenizer, that is the same open-source and developped by myself. Anyone can obtain the patch from below URL. After patching, Xapian::QueryParser::parse_query and

Hi, is there a way to get the number of all possible matches for a specific query? Some api call like Xapian::doccount Xapian::Enquire::get_number_of_matches(); Best wishes Wilm

Greets, Is it possible to obtain the actual match count if you're using set_collapse_key()? ie, the total count *before* the collapsing occurs (without using get_mset()). Alternatively, will MSet::get_matches_estimated() return the true - pre-collapse - count, or will it also be affected by collapsing? Thanks Henry

We are using the --enable-maintainer-mode and will move to git soon. The diff file is attached. *Siddhant Mutha* Undergraduate Student Department of Computer Science and Engineering IIT Madras Chennai http://www.siddhantmutha.com/ <http:/www.siddhantmutha.com/> On Sun, Apr 13, 2014 at 8:26 PM, James Aylett <james-xapian at tartarus.org>wrote: > On 13 Apr 2014, at 15:48, Pallavi

Hi, I try to use XapianMatchDecider to filtering results, but the code : $Decider = new MatchDecider_Search($XapianDatabase->_cPtr); $mset = $XapEnquire->get_mset(0, 3000, null, $Decider); Always return : PHP Fatal error: No matching function for overloaded 'Enquire_get_mset' in xapian.php on line 1082 I saw that SWIG was not supporting Directors for PHP, but now, it seems to

In the Ruby bindings, set_X and get_X are renamed to remove the get/set, so MSet::get_matches_estimated() becomes a read-only property (if I have my terminology right) of the Ruby MSet class called matches_estimated. This matches how a Ruby programmer would expect a class to be designed. I was looking through the getters and setters list. I wonder if a few entries shouldn't be there, (the

Very few people seem to be using synonym in Xapian, I recently found some problems in the use of synonyms. Normally, I think we should not contain any prefix info in synonym table except that 'Z'. For example, I have the following synonyms and prefix info: db.add_synonym("search", "find"); db.add_synonym("Zsearch", "Zfind");

Have been working recently on a site that classifies posts using tags in taxonomies, so a post about the Oil spill in the Gulf of Mexico might be tagged 'Subscribers only' (access level), 'Barack Obama' (person), 'Tony Hayward' (person), 'BP' (company), 'Transocean' (company), 'Gulf of Mexico' (location). With some advice from Richard Boulton I

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.

I run thunderbird (both 3.x and 5.x) against dovecot 2.x and frequently see delays "loading message". I admit to having a very large mailbox and running multiple imap clients. I've turned on thunderbird debugging, and at least one pattern I see in the log during the delays (maybe a minute long) is the failed protocol message above. These are no the only delays, but are the ones

Hello I defined a weighting scheme to simulate a king of "euclidean" distance. To test it, i used a database with 1000 documents. If I run : enquire.set_weighting_scheme(MyWeight()); Xapian::MSet matches = enquire.get_mset(0, 1000); I have a correct list of results. But if I run Xapian::MSet matches = enquire.get_mset(0, 10); I don't have the top-10 results. If I run Xapian::MSet

Hi folks, I spotted an HTML escaping bug in Xapian::MSet::snippet() while working on the code. This issue has been assigned CVE-2018-0499 (though currently there's no useful information on cve.mitre.org for it). I've added a wiki page for it here: https://trac.xapian.org/wiki/SecurityFixes/2018-07-02 The intended behaviour is that the selected input text is escaped for use in HTML,

I'm already retrying the ->get_mset operations; but now I'm wondering where I'd hit DatabaseModifiedErrors while inside a Xapian::MSetIterator loop. I assume ->get_document is a place where it gets thrown; but once a document is retrieved, can iterating through terms in one document (using TermIterator) also throw DB modified? I'm dumping multiple terms per-document to a