similar to: "Bad serialised query" error

In current Xapian SVN HEAD, there is a bug in the query parser concerned with the handling of wildcard terms with a "+" prefix. Specifically, a query such as "+foo* bar" will be parsed by the query parser into Xapian::Query("bar") if there are no terms in the database which start "foo". Instead, since the "+" term cannot be matched, I believe

I upgraded to latest xapian version and I have started getting xapian.InvalidArgumentError: Term too long (> 245): XTEXT... This issue was not there in 1.0.16 but it is in the latest version. Any solutions. thanks

The following piece of code triggers an 'unimplemented' exception with the message: "Can't use NEAR/PHRASE with a subexpression containing NEAR or PHRASE" Xapian::Query or1(Xapian::Query::OP_OR, Xapian::Query("one"), Xapian::Query("two")); Xapian::Query or2(Xapian::Query::OP_OR, Xapian::Query("three"),

I'm preparing a pull request for the master branch and noticed that `make check` on a clone of the xapian repository fails badly. I haven't merged my changes and built from e24cc6018de0. Is is just me or is there something broken in the master branch? Running test './apitest' under valgrind Running tests with backend "none"... Running test: defaultctor1...

On Mon, Apr 10, 2017 at 11:47:36PM +0530, Vivek Pal wrote: > > No, use Xapian::Registry to find the weighting scheme from the name > > like how Weight::unserialise() does (otherwise every caller would need > > code similar to that above). > > Okay, I looked into Xapian::Registry and it seems you are referring to using > the get_weighting_scheme method? (which expects a

On Sun, Apr 09, 2017 at 11:34:07PM +0530, Vivek Pal wrote: > > Each scheme already has a human-readable name, and Xapian::Registry > > can map that to an "examplar" object of the right type, so we > > could take a string like "bm25 1 0.8", see the first word is "bm25" > > and get a BM25Weight object, then call parse_params("1 0.8") on

Lately I was reading many articles about using boolean queries for search engine but I haven't seen any complete working demo. Therefore I put together very simple working demo of search engine using boolean query. Feel free to suggest any performance improvement or error while keeping it as simple as possible for understanding. Thanks, -Kevin Duraj http://myhealthcare.com

On Mon, Jul 11, 2016 at 02:02:56PM -0700, Kevin Duraj wrote: > You are saying that when I search for "delve Xapian 1.4" on Google, a > company worth of 491 Billion of Dollars and you saying that their top > of the search result has nothing to do with Xapian. > > https://www.google.com/search?q=xapian+delve&ie=utf-8&oe=utf-8#q=delve+xapian+1.4 Well, I'm not

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 =

> Each scheme already has a human-readable name, and Xapian::Registry > can map that to an "examplar" object of the right type, so we > could take a string like "bm25 1 0.8", see the first word is "bm25" > and get a BM25Weight object, then call parse_params("1 0.8") on it to > create the correct Weight object (broadly similar to how

i use the perl interface of Search::Xapian to index documents, now i got metadata i store with the index like title, date, author, .. and i wonder how to retrieve them from the index again without pulling them from the database. i am pretty sure this is a stupid question and that the answer is obvious i dont seem to be able to find it. regards m

xapian.InvalidArgumentError: Term too long (> 245): XTEXT... What is 245 here. 245 characters or 245 bytes or 245 words or 245 unique words or 245 characters in one word? Does it include spaces? Ashish

Hi all, I've come across a very strange bug with Xapian 1.0.9.0 and the Turkish query parser when trying to index a string (as posting) that looks like this: "...bir araya getiren CD'leri son teknolojiyle piyasaya...". The actual offending bit of the string is: 'leri It throws the message I have shown below. The real annoyance is that I can't seem to catch it because it

OK, I'm indexing my data with the scriptindex. I want to be able to restrict the search by the category field. Do I need to do anything to the data itself? Like, literally prefix it with the characters "XC"? Below is my indexor for scriptindex and the my php code... document_id : field=ref unique=Q boolean=Q search_id : field=document_id index=S document_title : field=title

I'm having trouble translating from C++ to perl objects. The TermIterator class looks like to get a set of terms in a document you might have C++ code like: Enquire::TermIterator termIt =enquire->get_matching_terms_begin(id); for(;termIt != enquire->get_matching_terms_end(id);termIt++) { string term = *termIt; } Or something similar. However when I attempt to translate that

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

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);

Please keep replies on the mailing list — more people can help (and benefit) that way :) So OP_NEAR looks for its terms close to each other (hence "near"). The window is how far away they can be. Probably the easiest way to play with this is using the NEAR syntax in the query parser. So if you had a plain text document: I am walking, always walking. And index it in a very simple

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

I gave extlinux a whirl, 1. installed debian onto a usb hard drive from laptop (onto /dev/sda1) did *not* install grub or lilo. 2. set up extlinux on /dev/sda # mount /dev/sda1 /mnt/t1 [root at harpo syslinux-3.00]# cd /mnt/t1/ [root at harpo t1]# ls boot/ config-2.6.8-1-386 initrd.img-2.6.8-1-386 System.map-2.6.8-1-386 vmlinuz-2.6.8-1-386 [root at harpo t1]# mkdir boot/extlinux [root