search for: and_maybe

...but word characters at the beginning and end ("3--3" will do). The other 2 terms can be anything. "test NEAR x-y NEAR test" will not cause a crash, but "test NEAR test NEAR x-y" will. Stemming language was "english", strategy STEM_SOME. Default op was OP_AND_MAYBE. This is the offending Perl code: [...] my $qp = Search::Xapian::QueryParser->new(); my $stemmer = Search::Xapian::Stem->new("english"); $qp->set_stemmer($stemmer); $qp->set_database($database); $qp->set_stemming_strategy(STEM_SOME); $qp->...

...ood afternoon I would like to ask if is possible somehow give more relevance to the recent documents in search results. I dont want to sort results according to the date, I still prefer relevance, but I would like to see recent documents with better scoring. I was trying to add search query using AND_MAYBE, which should use relevance from both subqueries, but it didnt add any benefit to the resalts which are match by this subquery $query = new XapianQuery(XapianQuery::OP_AND_MAYBE, $query, new XapianQuery(XapianQuery::OP_VALUE_GE, self::DATE, date('Ymd000000', strtotime("- 1 year&quot...

Hey all, I've been using ->add_database for a few years to tie sharded DBs together and it works great. Now, I want to be able to search across several DBs which aren't sharded, say: linux-DB, glibc-DB, freebsd-DB. I want to search for something across all of them, but prioritize results to favor one or some of those DBs over others. Is there a way to do that without reindexing? Or

...t() method which gets passed the shard it is being called for, so you can set an extra weight contribution based on that. This is a replacement for PostingSource::init() in 1.4, which doesn't know which shard it is being called for. You can then combine this PostingSource with your query with AND_MAYBE (so it matches exactly what the query does, but takes an extra weight contribution from the PostingSource for matching documents). > Or would I fiddle with wdf_inc for all ->index_text and ->add_term > calls on a per-DB basis? That would probably work if you don't want to be able...

...he > shard it is being called for, so you can set an extra weight > contribution based on that. This is a replacement for > PostingSource::init() in 1.4, which doesn't know which shard it is being > called for. > > You can then combine this PostingSource with your query with AND_MAYBE > (so it matches exactly what the query does, but takes an extra weight > contribution from the PostingSource for matching documents). Cool. I'll keep that in mind down the line. That could be a while since some users are still on 1.2 and tend to stick to what's provided by enterpr...

I attempted to use the sortable_serialize function from perl, however doesn't seem to exist. The only occurrence of the string "sortable" in the /usr/local/perl/5.10.1/Search/ tree is in the pod in Xapian.pm. What am I doing wrong? use Search::Xapian; ... $doc->add_value(4,sortable_serialize($recdate)); Undefined subroutine &main::sortable_serialize called

...forum threads, DB only indexed the thread title, author name, category name, and 1 optional serialize value(0) which is the unix dateline DB_full indexed all the DB terms + thread contents After couple tests, I decided to remove ALL anchor terms such as SHOW_PUBLIC, MORE_IMPORTANT Before i used AND_MAYBE (MORE_IMPORTANT) in query to add weights to more important docs Before i used AND (SHOW_PUBLIC) to search for public thread I removed these switches coz sometimes the CPU useage pops to 20% for one query (espically when the result set is big) And i also decided to seperate the DB into 2 sets, 1 w...

Are there any options to forming queries with Omega? For instance can you specify a proximity search like "file near 5 manager"? If so, where might I find this documented? I don't see it in the docs directory. Thanks Jim.

...: check that wildcards work with +terms. + unsigned flags = Xapian::QueryParser::FLAG_WILDCARD | + Xapian::QueryParser::FLAG_LOVEHATE; + qobj = queryparser.parse_query("+mai* main", flags); + TEST_EQUAL(qobj.get_description(), "Xapian::Query((main:(pos=1) AND_MAYBE main:(pos=2)))"); + // Regression test (if we had a +term which was a wildcard and wasn't + // present, the query could still match documents). + qobj = queryparser.parse_query("foo* main", flags); + TEST_EQUAL(qobj.get_description(), "Xapian::Query(main:(pos=2))...