search for: matchal

I've just had a quick look at the XS, but I can't see quite how to make these (or just MatchAll, really) available through the Perl binding ... where should I start please?

Hi, We have a search service based on xapian, when receving a request, we create several threads to create xapian-query and search in the corresponding databases, and then merge all results together. In some case, we use Xapian::Query::MatchAll to create the query, but it always has Segmentation fault (core dumped). It looks like some pointers are double freed. This is the function that we use to create xapian-query. std::shared_ptr<Xapian::Query> constructQuery() { Xapian::Query black_list("BLt1"); return st...

Why there still been rank when using Query::MatchAll() ?

Hi, I have read the concurrency webpage from the Xapian documentation: http://getting-started-with-xapian.readthedocs.io/en/latest/concepts/concurrency.html But it is still not clear to me how to ensure thread-safety when using libxapian (C++ API). Usually when doing multi-threading many threads can read the same variable concurrently without locking provided none of the threads modifies the

Hi, I want to print all the records from the passed database when the search string is not present. I quickly skimmed through the API but I couldn't find a way to do it. Can someone show some pointers. Thanks, Shri

...hirdcontext include => fourthcontext [fourthcontext] _03X.,1,Goto(${EXTEN:2},1) _X.,1,DoSomething() _X.,2,Hangup() the Goto() for exten _03X. seems to start the search for the jump within firstcontext, thus possibly matching an exten in secondcontext or thirdcontext first before hitting the matchall in fourthcontext. obviously, a simple fix would be to change it to Goto(fourthcontext,${EXTEN:2},1). however, i dont remember Goto working this way. shouldn't a Goto search within the current context first when the context parameter is ommitted ? it's asterisk 1.2.14 in FreeBSD 6.1 tho...

...zing don't work, but waste > time oppositely. How do you think about this? If I follow, you're saying your query is just this an ExternalWeightPostingSource object? If so, what is the query in the KeyMaker case? I'd expect a KeyMaker to also be fairly slow if the query is Query::MatchAll or similar as the sort key will need building for every matching document, like how the PostingSource will need to calculate the weight for every matching document. > Also, We found the BM25 algorithm is fast in xapian, so we think if we > can modify our get_weight() function to adjust the...

...r = 0; int count = 0; try { /* set up a cursor to read from all the source databases */ Xapian::Database *srcdb = new Xapian::Database(); while (*sources) { srcdb->add_database(Xapian::Database(*sources++)); } Xapian::Enquire enquire(*srcdb); enquire.set_query(Xapian::Query::MatchAll); Xapian::MSet matches = enquire.get_mset(0, srcdb->get_doccount()); /* create a destination database */ Xapian::WritableDatabase *destdb = new Xapian::WritableDatabase(dest, Xapian::DB_CREATE_OR_OPEN); destdb->begin_transaction(); /* copy all matching documents to the new DB */ for...

...erms: > > std::set<std::string> terms; > > // notmuch populates terms via terms.insert(*i)... > > Query(OP_OR, terms.begin(), terms.end()); The slicker way to do this (unless you need the std::set for other reasons) would be: Xapian::Query filter = Xapian::Query::MatchAll; while (more_terms()) { filter |= Xapian::Query(get_next_term()); } Assuming you're using Xapian >= 1.4.10 then |= on an OP_OR Query with refcount 1 (as here) is specially optimised and just appends a new subquery so you get a single OP_OR node and this is particularly effi...

I probably should've used boolean terms in addition to numeric values when indexing, but currently I have a set of numeric values[1] and trying to avoid having to reindex ~250GB DBs (and asking numerous users to do the same). Say I have a bunch of values which I want to filter a query against. If I had boolean terms, it could just OP_OR against the whole set. IOW, this is what notmuch does

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

>A possible workaround (and perhaps a better approach) would be to >set BoolWeight as the weighting scheme, then feed in your score as >a weight using a PostingSource. Then it's available via get_weight() >on the MSetIterator object: > >https://getting-started-with-xapian.readthedocs.io/en/latest/advanced/postingsource.html > >You may find that's faster because